- From: Youenn Fablet <youenn@apple.com>
- Date: Mon, 13 Dec 2021 23:10:28 +0100
- To: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Cc: "public-webrtc@W3.org" <public-webrtc@w3.org>
- Message-id: <CBC1812A-CC95-4528-AD9F-5C1D65F56012@apple.com>
• I support adoption of "MediaStreamTrack Insertable Media Processing using Streams". For this effort to be successful, I believe the WG will have to make sure progress is being made in the following areas: - Make sure proper streams supported along the lines of https://github.com/whatwg/streams/pull/1193 <https://github.com/whatwg/streams/pull/1193>. - Improve consistency with WebCodecs, using streams in one but not the other creates a mismatch in API design, which is unfortunate. - Improve consistency with other image manipulation APIs that might being designed in the future. https://wicg.github.io/shape-detection-api/ <https://wicg.github.io/shape-detection-api/> is a good example which uses callbacks, while TransformStream would be the natural way to go with MediaStreamTrack capture transform. > On 2 Dec 2021, at 14:09, Bernard Aboba <Bernard.Aboba@microsoft.com> wrote: > > This is a Call for Adoption (CfA) of "MediaStreamTrack Insertable Media Processing using Streams". The specification is available for inspection here: > MediaStreamTrack Insertable Media Processing using Streams (alvestrand.github.io) <https://alvestrand.github.io/mediacapture-transform/> > > The GitHub repo is here: GitHub - alvestrand/mediacapture-transform <https://github.com/alvestrand/mediacapture-transform> > > In response, please state one of the following: > I support adoption of "MediaStreamTrack Insertable Media Processing using Streams". > I object to adoption of the specification, due to issues filed in open bug <#number>. > The CfA will end on December 13, 2021 at midnight Pacific Time. > > Bernard > > For the Chairs
Received on Monday, 13 December 2021 22:10:49 UTC