- From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
- Date: Fri, 22 Jun 2018 11:46:56 +0200
- To: public-webrtc@w3.org
On 22/06/2018 11:19, Harald Alvestrand wrote: > A critical part of this is also that the Web application has to attach > enough information to the encrypted packets that the SFU can do its job > of choosing which packets / frames to forward; in SVC or simulcast, this > includes labelling packets containing video with enough information to > reconstruct the dependency graph, for instance; if "loudest audio" > switching is in effect, the outside of the packet has to contain audio > level information. I don't quite agree, the only information that the SFU requires is already provided by the audio-to-mixer audio level and video frame marking header extensions. That should be implemented by the browser and the app would just need to enable them. Best regards Sergio
Received on Friday, 22 June 2018 09:46:19 UTC