W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2015

Re: Need API to read the CSRC on received tracks (#4)

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Fri, 31 Jul 2015 17:26:36 +0000
To: public-webrtc <public-webrtc@w3.org>
Message-ID: <4BDF42C7-D821-4A5A-9E50-7FEB4A718195@microsoft.com>
It could extend RTCRtpReceiver, like this:

Contributing Sources

The getContributingSources method extends the RTCRtpReceiver object, providing information on the sources contributing to an incoming media stream.

partial interface RTCRtpReceiver {
    sequence<RTCRtpContributingSource> getContributingSources ();


Retrieve the sequence of contributing sources.

No parameters.
Return type: sequence<RTCRtpContributingSource>

dictionary RTCRtpContributingSource

dictionary RTCRtpContributingSource {
             DOMHiResTimeStamp timestamp;
             unsigned long     csrc;
             byte              audioLevel;

Dictionary RTCRtpContributingSource Members

audioLevel of type byte,
The audio level of the contributing source. Value is between 0 and -127 representing the contributing source dBov value, as described in [RFC6465]

csrc of type unsigned long,
The contributing source.

timestamp of type DOMHiResTimeStamp,

On Jul 31, 2015, at 08:31, Cullen Jennings <notifications@github.com<mailto:notifications@github.com>> wrote:

@alvestrand<https://github.com/alvestrand> - would stats be a reasonable place to put this or should it be RTCRtpReceiver ?

Reply to this email directly or view it on GitHub<https://github.com/w3c/webrtc-pc/issues/4#issuecomment-126725763>.
Received on Friday, 31 July 2015 17:27:11 UTC

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