- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Feb 2024 10:45:51 +0000
- To: public-webrtc-logs@w3.org
It is a missing feature in the implementation, in particular the > Any currently available media formats that are not present in the current remote description MUST be added after all existing formats. from https://www.rfc-editor.org/rfc/rfc8829.html#name-initial-answers I did tinker with a recv-only codec and setting the transceiver direction to sendonly: https://jsfiddle.net/fippo/r63bp8d2/1/ Works fine with and without this change. This is *fine* but the logic is weird... you can only determine the send codec once you have the other side's answer. But the other side will not know what codecs you support... -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2932#issuecomment-1933807433 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 10:45:54 UTC