W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2014

RE: active speaker information in mixed streams

From: Johnston, Alan B (Alan) <abjohnston@avaya.com>
Date: Wed, 12 Feb 2014 22:45:54 +0000
To: Emil Ivov <emcho@jitsi.org>, Bernard Aboba <Bernard.Aboba@microsoft.com>
CC: Tim Panton new <thp@westhawk.co.uk>, Harald Alvestrand <hta@google.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <7DE47B1B6D020A4789561F4C0D3E96C75F307203@AZ-US1EXMB03.global.avaya.com>
There are existing audio mixers that support CSRC indications, and SIP VoIP clients that can use them to display active speakers.

Why wouldn't we encourage support of this in WebRTC for now and use web audio in the future.

- Alan -
From: Emil Ivov [emcho@jitsi.org]
Sent: Wednesday, February 12, 2014 5:34 PM
To: Bernard Aboba
Cc: Tim Panton new; Harald Alvestrand; public-webrtc@w3.org
Subject: Re: active speaker information in mixed streams

On Wed, Feb 12, 2014 at 6:31 PM, Emil Ivov <emcho@jitsi.org> wrote:
> On Wed, Feb 12, 2014 at 6:24 PM, Bernard Aboba
> <Bernard.Aboba@microsoft.com> wrote:
>> [BA] That is my take, at least for "dominant speaker" identification.   To my mind, CSRCs and averaged levels are only useful for indicating which sources are providing sound (or noise, as the case may be).
>> If the goal is to enable switching video to the dominant speaker, then you actually need to figure out who is speaking (as opposed to typing on their keyboard, having their dog bark, etc.).  The web audio API is much better suited for that.
> The web audio API would be great if you actually have access to the
> individual audio streams. This is not the case when the browser is
> only getting a single, mixed audio stream. CSRC levels is the only
> option one has there.

Another thought about this. If consensus is that 1.0 is too far ahead
for CSRC audio levels then maybe we could at least add support for

Adding access to those would at least allow mixers to detect dominant
speakers and indicate them to participants.

Besides, CSRCs are, after all, native to RFC3550.


Received on Thursday, 13 February 2014 08:34:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:54 UTC