- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Oct 2024 09:25:39 +0000
- To: public-webrtc-logs@w3.org
henbos has just created a new issue for https://github.com/w3c/webrtc-pc: == Align codec preference and direction == How to deal with codecs and directionality was discussed at TPAC 2024: - [Minutes](https://www.w3.org/2024/09/24-webrtc-minutes.html#4c6d) - [Slides](https://docs.google.com/presentation/d/1dFntwgSd9MrLnd1Sf58eBHstkodUd30WSKGIaK5K2CM/edit#slide=id.g302dfc81162_4_26) - [Recording](https://www.youtube.com/watch?v=aDKpOfGhbXk&t=44m39s) There was a strong preference for Proposal A, i.e. to "keep it simple": sendonly transceivers can do all send codecs, recvonly transcievers can do all receive codecs, and sendrecv transceivers can only do codecs and profiles that you can BOTH send AND receive with. So if you want to do fancy unidirectional codecs or profiles you use multiple m= sections. Let this issue track making sure the spec aligns with Proposal A and allow us to merge other codec related issues as fixed by this issue Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3006 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 October 2024 09:25:40 UTC