- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Jan 2021 16:15:53 +0000
- To: public-webrtc-logs@w3.org
This is my understanding: - All opus endpoints must be prepared to receive stereo. Even if we announced "stereo=0" we are gently asking to get mono, but the other endpoint is free to send us stereo anyway. (Similar to how order of codecs is just a preference.) - "stereo=1" only talks about receiving preferences, not sending preferences. - However if "stereo" is missing we default to "stereo=0" so in practise everybody asks for mono at the moment. To me it sounds like no spec change is needed in order to achieve _receiving_ stereo. @perahgren can you verify that WebRTC is able to receive stereo even if "stereo=1" is missing? However it doesn't make sense to be _sending_ stereo at the present moment since everybody is implicitly asking for mono by having "stereo=1" missing. To me it would make sense if "stereo=1" is the default in offers and decide the what to send based on the MediaStreamTrack's number of channels. Questions: - Is the answerer allowed to modify the stereo line or is this an illegal modification by the answerer side to the SDP? - If we change the default, would we start sending stereo in a lot of cases where we don't today? How easy and performant is it to change number of channels of a MediaStreamTrack? In other words is there still a reason to be able to control this? -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/63#issuecomment-761036205 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 January 2021 16:15:55 UTC