- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Jan 2023 12:33:45 +0000
- To: public-webrtc-logs@w3.org
This was heavily discussed when we had the "shape of the API" discussion. The consensus was that we would go with MediaStreamTrackProcessor because it was able to process any kind of MediaStreamTrack, and VideoTrackGenerator / AudioTrackGenerator because the type of input data was different. We have implementations, we have code that uses this. I don't see a reason to reopen this issue. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/73#issuecomment-1377194295 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 January 2023 12:33:47 UTC