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

Re: active speaker information in mixed streams

From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Tue, 11 Feb 2014 23:55:30 +0100
Message-ID: <CALiegfmV6DuO3QTT5rSLR-iQGnEa37dGhJyfLrQB7anh0f3aXw@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
2014-02-07 14:54 GMT+01:00 Harald Alvestrand <harald@alvestrand.no>:
> 1) It is only needed when talking to devices that use CSRC mapping. This
> is a property set that belongs to the peerconnection abstraction
> (probably on the receiving doohickey), not to the more generic
> MediaStram connection.

If that "event" (or whatever) belongs to PeerConnection then the
reference to the MediaStream and/or MediaStreamTrack should also be
provided by the callback, so we end in the same case. The problem here
(IMHO) is having all the stuff on a single object (PeerConnection). Of
course I don't want to expose WebRTC related stuff into
MediaStream(Track), but adding everything on top of PC is not the
proper way to go (IMHO).



> 2) If this is going to be useful for active speaker switch indication,
> the notification has to happen on a sub-second basis - too fast for a
> reasonable periodic event.

It could be relaxed/limited by the spec (i.e. just fire every 0.5
seconds). I don't get how a JS periodic timer can be better, but maybe
I am wrong.


Best regards.



-- 
Iñaki Baz Castillo
<ibc@aliax.net>
Received on Tuesday, 11 February 2014 22:56:18 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:38 UTC