- From: Gustavo Garcia <ggb@tokbox.com>
- Date: Tue, 28 Jan 2014 09:49:38 -0800
- To: Emil Ivov <emcho@jitsi.org>
- Cc: Iņaki Baz Castillo <ibc@aliax.net>, public-orca <public-orca@w3.org>
>> 2) You have access to the audio level of the tracks received with the >> getStats API (in Chrome) > > Just to make it clear: my original question was about mixed streams. > That is, streams where all contributors would be rendered within the > same track. I know, just asking Iņaki's question :) Regarding your question I think it makes a lot of sense and adding a way to get those "stats" from the RtpTrack could be very useful. Being able to subscribe to changes of the V bit could also be helpful but I think it is too much for ORTC v1. > Emil > >> On Tue, Jan 28, 2014 at 5:51 AM, Iņaki Baz Castillo <ibc@aliax.net> wrote: >>> 2014-01-28 Emil Ivov <emcho@jitsi.org>: >>>> One requirement that we often bump against is the possibility to >>>> extract active speaker information from an incoming *mixed* audio >>>> stream. Acquiring the CSRC list from RTP would be a good start. Audio >>>> levels as per RFC6465 would be even better. >>> >>> Question (related): >>> >>> In case of a bridge server that does not mix audio channels but just >>> relays them as separate tracks, how can the WebRTC client/browser know >>> about the activity of each received audio track? >>> >>> >>> -- >>> Iņaki Baz Castillo >>> <ibc@aliax.net> >>> > > > > -- > https://jitsi.org
Received on Tuesday, 28 January 2014 17:50:05 UTC