- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Mar 2017 02:45:51 +0000
- To: public-webrtc-logs@w3.org
> Another puzzling question is what happens if we have both simulcast and CSRC I've seen a number of applications that have implemented Opus forwarding instead of mixing. Typically this is supported by forwarding up to N streams, each of which goes to its own receiver, with mixing in the browser. In this scenario (which is *not* simulcast), the packets may arrive with CSRCs, representing the sources that contributed to the packet (usually only one), with the SSRC being one of the N allocated by the SFU. Since there is no mixing, there will likely be no mixer-client extension, yet there would be a (single) CSRC and it would be useful to have the audiolevel corresponding to the SSRC, since this would be used to show the level originating from the CSRC. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1091#issuecomment-288282357 using your GitHub account
Received on Wednesday, 22 March 2017 02:45:57 UTC