- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 Jul 2019 18:21:28 +0000
- To: public-webrtc-logs@w3.org
I'd suggest the same applies to `getSynchronizationSources()`. See audio bars next to speakers in a WebRTC call seems useful regardless of whether that audio is being outputted. Maybe even more so when it is not. Browsers that want to optimize this, could look at whether the JS is using the `getSynchronizationSources()` API at all (I suspect very few do)—The API is synchronous, but is meant to be called in realtime, so I don't think anyone would fault the browser if the very first call didn't have the right info? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2240#issuecomment-516535198 using your GitHub account
Received on Tuesday, 30 July 2019 18:21:29 UTC