- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Mar 2017 02:34:16 +0000
- To: public-webrtc-logs@w3.org
In the case where there are CSRCs (a mixer), there also would presumably be a mixer-client extension which would provide audiolevels for the CSRCs. In this case the browser would not be required to compute the audio-level for the SSRC. In the P2P case, there would only be an SSRC, so the browser is required to include the audiolevel for that SSRC. Given this, the code to compute the audiolevel for the SSRC is going to be there in either case. And one could argue that the SSRC could be included (though not in the list of CSRCs, as Harald pointed out), and if it is, the audiolevel could be computed as well (e.g. it could be used to provide UI for the overall audiolevel of the conference) -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1091#issuecomment-288280634 using your GitHub account
Received on Wednesday, 22 March 2017 02:34:22 UTC