- From: docfaraday via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Aug 2024 16:25:15 +0000
- To: public-webrtc-logs@w3.org
I should note that semantic matching of sdpFmtpLine is not sufficient to fix this problem; max-fr=60 and max-fr=30 are not semantically equivalent, but we probably still want the .codec setting to work here. If we want to be able to match these, we'd basically have to specify that the browser consider it a match if the same codec/channels/clockRate/fmtp in a remote description would be considered a successful negotiation of that codec. Alternately, we could punt and say that .codec is only ever matched against RTCRtpParameters.codecs (ie; negotiated codecs with parameters from a remote description), and that setting .codec based on getCapabilities, or before negotiation, is simply not allowed. -- GitHub Notification of comment by docfaraday Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2987#issuecomment-2296966299 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 19 August 2024 16:25:16 UTC