- From: perahgren via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Jan 2021 22:23:48 +0000
- To: public-webrtc-logs@w3.org
From what I know, stereo is fully supported in the pipeline. However, I'm not convinced that setting stereo=1 by default really solves this. As I see it, there are two problems 1. To be able to produce stereo, the SDP needs to be munged (by adding stereo=1) before setLocalDescription. 2. If the receiver does not want to receive stereo (sets stereo=0 or omits a value for stereo), the sender should heed that by re-doing the createOffer. If I've understood this correctly, setting stereo=1 by default won't really solve any of the above, apart from not requiring any action when stereo should be sent. If mono should be sent, however, the problems still persist. Also, if we set stereo=1 by default, won't then suddenly all stereo-capable client that are not explicitly setting stereo=0 start sending stereo audio instead of mono? -- GitHub Notification of comment by perahgren Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/63#issuecomment-762495567 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 18 January 2021 22:23:50 UTC