- From: stefan hakansson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Jan 2024 13:15:33 +0000
- To: public-webrtc-logs@w3.org
@fippo thanks for a good summary! For my case (unidirectional medai), things now make sense as the receiving (also being SDP answerer) end can use transceiver.setCodecPreferences to indicate preferred receive codec(s). Exactly what I was looking for. 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. -- GitHub Notification of comment by stefhak Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2888#issuecomment-1884831753 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 13:15:36 UTC