- From: perahgren via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Feb 2021 09:28:45 +0000
- To: public-webrtc-logs@w3.org
A concern I have on the PR is that it does not really solve the underlying problem of lack of API and the need for munging. It will indeed make setting up stereo calls more convenient in that stereo=1 is added by default which avoids the issue that there is no API to control it (and therefore avoids the munging needed). However, the problem of lack of API, and the resulting need for munging, is then instead imposed on the clients that actually would want to set stereo=0 (or omit the stereo flag). I may get this wrong, but I think what would be needed is to have an API for setting/clearing the stereo that avoids munging. Having stereo=1 would be handy, but I share the concerns of @juberti and also that there may be other unforeseen effects for clients that implicitly rely on stereo=1 not being set by default. -- GitHub Notification of comment by perahgren Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/63#issuecomment-784938351 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 February 2021 09:28:47 UTC