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

I support the adoption of "WebRTC Insertable Media Using Streams" as a WEBRTC WG deliverable.

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/) could be useful?

Br,
Stefan

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Thursday, 28 May 2020 at 18:02
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Call for Consensus (CfC) on Adoption of the Insertable Streams API specification
Resent from: "public-webrtc@w3.org" <public-webrtc@w3.org>
Resent date: Thursday, 28 May 2020 at 18:00

This is a Call for Consensus (CfC) to adopt "WebRTC Insertable Media Using Streams" as a WEBRTC WG deliverable.

Note that adoption as a WEBRTC WG deliverable implies only that the specification is suitable as a starting point.

The specification is located here: https://alvestrand.github.io/webrtc-media-streams/<https://protect2.fireeye.com/v1/url?k=5d8131fd-0321d169-5d817166-86d2114eab2f-67d6a2fdb7866c90&q=1&e=729f44a6-6ecf-4608-be75-89ab76994230&u=https%3A%2F%2Falvestrand.github.io%2Fwebrtc-media-streams%2F>
The Github repo is here: https://github.com/alvestrand/webrtc-media-streams<https://protect2.fireeye.com/v1/url?k=586eb0eb-06ce507f-586ef070-86d2114eab2f-7fefb69bd7b1a686&q=1&e=729f44a6-6ecf-4608-be75-89ab76994230&u=https%3A%2F%2Fgithub.com%2Falvestrand%2Fwebrtc-media-streams>

The WebRTC-NV use cases document is available here: https://w3c.github.io/webrtc-nv-use-cases/<https://protect2.fireeye.com/v1/url?k=35ff4d49-6b5faddd-35ff0dd2-86d2114eab2f-7f026e4ba5400fb2&q=1&e=729f44a6-6ecf-4608-be75-89ab76994230&u=https%3A%2F%2Fw3c.github.io%2Fwebrtc-nv-use-cases%2F>

The CfC will last for one week, and will end on Friday, June 5, 2020 at 16:00 UTC.

In response, please state one of the following:
·         I support publishing the Insertable Streams API draft as WEBRTC WG deliverable.
·         I object to adopting the current Insertable Streams API draft as a WEBRTC WG work item, due to issues filed in open bug <#number>.
Note that time has been reserved at the June 4, 2020 virtual interim (see previous message) for discussion of the Insertable Streams API.


Bernard, for the Chairs