W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2022

[mediacapture-transform] Compare callback-based and ReadableStream-based exposure of video MediaStreamTrack media flow (#69)

From: youennf via GitHub <sysbot+gh@w3.org>
Date: Tue, 04 Jan 2022 08:29:33 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-1093120746-1620403452-sysbot+gh@w3.org>
youennf has just created a new issue for https://github.com/w3c/mediacapture-transform:

== Compare callback-based and ReadableStream-based exposure of video MediaStreamTrack media flow ==
MediaStreamTrack is encapsulating a flow of video frames and some applications might want to be notified when a new video frame happens:
- Existing applications would like to paint into a canvas for every track frame.
- Future applications might want to manipulate raw video frames (MediaStreamTrackProcessor use cases).

It would be interesting to evaluate the pros and cons of a callback-based approach vs. a ReadableStream-based approach.

Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/69 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 4 January 2022 08:29:35 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 4 January 2022 08:29:36 UTC