- From: Florent Castelli via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Jan 2024 21:06:10 +0000
- To: public-webrtc-logs@w3.org
> One slightly confusing thing for me is that webrtc-extensions adds the possibility to define a codec with setParameters on the _RTCRTPsender_. Can't this be a problem if used before negotiation? In that case any of the implemented (send) codecs can be used, so the promise probably resolves, but the receiver may not support it, which only becomes apparent after SDP o/a. [Section 7.2.3](https://w3c.github.io/webrtc-extensions/#set-the-session-description) handles that, and if the codec is not in the `SendCodecs` list, the forced codec setting will be removed and it'll default to the browser's choice. It should still be valid with the proposed fixes. -- GitHub Notification of comment by Orphis Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2888#issuecomment-1885733099 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 January 2024 21:06:13 UTC