- From: Gustavo Garcia <ggb@tokbox.com>
- Date: Tue, 28 Jan 2014 09:31:17 -0800
- To: Iņaki Baz Castillo <ibc@aliax.net>
- Cc: Emil Ivov <emcho@jitsi.org>, public-orca <public-orca@w3.org>
1) The audio level is sent by Chrome in the corresponding RTP extension header, but AFAIK that information is not used by the browser receiving it. 2) You have access to the audio level of the tracks received with the getStats API (in Chrome) 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> >
Received on Tuesday, 28 January 2014 17:31:48 UTC