Ben Wagner
Ben Wagner
Following up to https://github.com/w3c/mediacapture-transform/issues/28, the sample at https://github.com/webrtc/samples/tree/gh-pages/src/content/insertable-streams/video-processing should be changed to (optionally?) process the video on a worker rather than the main thread.
Following up to w3c/mediacapture-transform#28, the sample at https://github.com/webrtc/samples/tree/gh-pages/src/content/insertable-streams/audio-processing should be changed to (optionally?) process the video on a worker rather than the main thread.
The [WebRTC Next Version Use Cases doc](https://w3c.github.io/webrtc-nv-use-cases/) lists three use-cases under [Funny hats](https://w3c.github.io/webrtc-nv-use-cases/#funnyhats*) related to plain-text associated with media: [Captioning, Transcription, and Language translation](https://github.com/w3c/webrtc-nv-use-cases/blob/f937a4fdf26d4b2dedefce371425a952be8ad05b/index.html#L279). However, there do not seem to...
Many APIs providing a MediaStreamTrack are limited by [SecureContext](https://webidl.spec.whatwg.org/#SecureContext) in WebIDL, such as enumerateDevices, getUserMedia, and getDisplayMedia. Other APIs do not require a SecureContext, e.g. [captureStream](https://w3c.github.io/mediacapture-fromelement/). Which of the following...
Currently the [transfer spec](https://w3c.github.io/mediacapture-extensions/#transferable-mediastreamtrack) changes only the interface definition for `MediaStreamTrack`, making it `Transferable` as well as adding `Worker` to the `Exposed` list. If we keep worker exposure, some other...
Regarding [Transferable MediaStreamTrack](https://w3c.github.io/mediacapture-extensions/#transferable-mediastreamtrack), I think there is only one reasonable approach for handling delivery of media (video frames or audio data) during transfer: media stops flowing before postMessage returns on...