- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Oct 2024 13:40:20 +0000
- To: public-webrtc-logs@w3.org
https://www.rfc-editor.org/rfc/rfc8829.html#section-4.2.6-1 remains clear on what setCodecPreferences is intended for: > It only affects which codecs the implementation indicates that it prefers to receive, via the offer or answer I keep looking for a sendonly codec that is not covered by special codec rules like level-asymmetry-allowed which covered the weird ([and likely buggy](https://issues.chromium.org/issues/368478704)) H264 instance we found. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3006#issuecomment-2391454485 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 October 2024 13:40:21 UTC