Re: [EXTERNAL] Re: Call for Consensus (CfC) on Adoption of the Insertable Streams API specification

On Jun 2, 2020, at 2:00 AM, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> wrote:

I’d like to see more work to determine if this model is also suitable for accessing raw media, and I’d also like to see overlap/sync vis a vis WebCodecs investigated.
Regarding N22: would it be worth looking into whether WebGPU (https://gpuweb.github.io/gpuweb/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgpuweb.github.io%2Fgpuweb%2F&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8db5a4fef3a94a7679e408d806d32991%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637266852299530210&sdata=%2BaA%2FeU2LsVhlpAjFBioVPdLOdsoygrQ3yzN8yo0ui6w%3D&reserved=0>) could be useful?

[BA] Excellent points. Raw media is much larger than encoded, so performance is a concern. One thing under discussion in WebCodecs is whether it might be useful to provide handles to GPU buffers which could enable WebGPU operations on raw (or encoded) media.

Prototyping of WHATWG stream support in WebCodecs did not go well, and issues relating to WebRTC parity and DRM support have been raised. So at present Insertable Streams is much closer to a “bird in the hand” although we are not sure what songs this bird may be able to sing.