- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Feb 2024 08:45:02 +0000
- To: public-webrtc-logs@w3.org
> That is not what setCodecPreferences does, it only controls receive preferences. [...] and that is what we are doing? What we're seeing is not being allowed to prefer to receive H264 unless the offerer is preferring to receive it too. This is fine for codecs that work in both directions because you can always swap preference order and use the codec you don't want to use as a fallback, but it makes little sense for unidirectional codecs. Whether we want to solve this or not is up to us, there are workarounds like modifying SDP (in a legal way) or preferring to receive something you can't receive knowing the other endpoint will swap orders. Just because you can shoot yourself in the foot doesn't mean you will. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2932#issuecomment-1933604818 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 February 2024 08:45:05 UTC