- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Feb 2024 11:07:08 +0000
- To: public-webrtc-logs@w3.org
Assuming we finalise https://github.com/w3c/media-capabilities/pull/186, we would use `RTCRtpCodecCapability` as the output of Media Capabilities. On WebRTC side, API wise, there could be different approaches: 1. Context wide approach. Add `RTCRtpSender.addCodec` and `RTCRtpReceiver.addCodec`, applies to all peer connections of the given context 2. RTCPeerConnection wide approach. Add senderCodecs and receiverCodecs fields to `RTCConfiguration` 3. Transceiver approach. Use `RTCRtpSender.setCodecPreferences` and `RTCRtpReceiver.setCodecPreferences` 3 has no API overhead which is nice. I might have a slight preference for 1 though: from a web developer point of view, this is the least invasive approach and would make it easy to handle UAs with different default codec sets in one single place. @alvestrand, thoughts? -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2929#issuecomment-1959212929 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 22 February 2024 11:07:09 UTC