w3ctag / design-reviews

W3C specs and API reviews
Creative Commons Zero v1.0 Universal
330 stars 55 forks source link

WebRTC Codec selection API #836

Closed Orphis closed 1 year ago

Orphis commented 1 year ago

こんにちは TAG-さん!

I'm requesting a TAG review of the WebRTC Codec selection API.

We want to be able to change codec with RTCRtpSender.setParameters() in order to do the following:

Current users of the WebRTC APIs can achieve the similar functionality with multiple calls that are not quite easy to use (renegotiate with a different codec order in the SDP, which is a heavy operation) and are not as efficient (changing the codec and then changing the scalability mode or other parameters may add an extra I-frame that is not needed). This API also allows to have mixed-codec simulcast, which was not possible previously.

Further details:

We'd prefer the TAG provide feedback as:

💬 leave review feedback as a comment in this issue and @-notify [@orphis]

torgo commented 1 year ago

Hi - Can you please put together an explainer for this so we can start a review? See here https://w3ctag.org/explainers/ for our explainer explainer. Thanks! ✨

torgo commented 1 year ago

Hi @Orphis - just a gentle reminder on this one. Can you please send us a (markdown) explainer - see https://w3ctag.org/explainers/ ? I see you've linked to a presentation but it's really not clear from that what the user need is specifically. I just want to make sure we understand that. Can you also please send us some explicit info on multi-stakeholder support (in particular multiple browser engines)?

torgo commented 1 year ago

Hi folks - I'm going to close this one for now. Please feel free to re-open when you're ready for a review.

Orphis commented 1 year ago

@torgo Sorry for the long delay. Here is an explainer for the API changes: https://github.com/Orphis/webrtc-extensions/blob/explainer/explainers/codec-selection.md Could you reopen the issue please?

torgo commented 1 year ago

@Orphis thanks for this updated explainer. It's really good to see that this proposal enjoys support from multiple browsers. Ideally I'd like to see a bit more discussion of user needs – which you may feel boil down to "more seamless video calls" – but it would be nice to have that spelled out.