Re: active speaker information in mixed streams from Iñaki Baz Castillo on 2014-02-13 (public-webrtc@w3.org from February 2014)

From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Thu, 13 Feb 2014 15:43:34 +0100
To: Emil Ivov <emcho@jitsi.org>
Cc: "Johnston, Alan B (Alan)" <abjohnston@avaya.com>, Bernard Aboba <Bernard.Aboba@microsoft.com>, Tim Panton new <thp@westhawk.co.uk>, Harald Alvestrand <hta@google.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <CALiegfnPgp4SLzLCqzJ-R3EjkP++mC+PDcN=7thqhi7AsPSOoQ@mail.gmail.com>

2014-02-13 15:38 GMT+01:00 Emil Ivov <emcho@jitsi.org>:
>> May I understand how the WebAudio API could be aware of RTP fields?
>
> I don't believe anyone is suggesting that CSRCs be surfaced through
> the WebAudio API. My understanding is that the current discussion is
> about whether or not such details could be bubbled through the WebRTC
> API (1.0).

Right, the subject of this thread is "active speaker information in
mixed streams" so clearly we need the CSRC values inspection in client
side. That can only be achieved by the WebRTC API (and the WebAudio
API is totally useless for this subject).



-- 
Iñaki Baz Castillo
<ibc@aliax.net>

Received on Thursday, 13 February 2014 14:44:23 UTC