- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Feb 2022 22:44:13 +0000
- To: public-webrtc-logs@w3.org
@fippo That is a very impressive list of bugs!
@orphis @alvestrand Are we looking to modify the negotiation process (e.g. filter codecs emitted by `createOffer()`)? Or we talking about a parameter setting?
In a scenario where the preferred codec is only supported in hardware, `setParameters("prefer-software")` would imply attempting to modify the envelope of what is negotiated in Offer/Answer, which is not permitted in WebRTC 1.0. So the parameters approach seems problematic to me.
Instead, could we have an extension to `setCodecPreferences()` which affects how `createOffer()` and `createAnswer()` behave. If that's the case, then the change will only take effect when negotiation completes.
--
GitHub Notification of comment by aboba
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/98#issuecomment-1054745385 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 February 2022 22:44:14 UTC