More information needed.

The following proposal (involving polling) was put forward to support retrieval of both the mixer-to-client audio level as well as the CSRC list. Although some people expressed interest, overall it was not considered a "must have" for WebRTC 1.1, let alone WebRTC 1.0:

partial interface RTCRtpReceiver {
sequence getContributingSources ();
};

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

@alvestrand - would stats be a reasonable place to put this or should it be RTCRtpReceiver ?

The use case for this BTW is that this is the best way to drive the active speaker indication in a conference roster list.

It would 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 getContributingSources ();
};

Methods

getContributingSources
Retrieve the sequence of contributing sources.

No parameters.
Return type: sequence

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.commailto:notifications@github.com> wrote:

@alvestrandhttps://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 GitHubhttps://github.com//issues/4#issuecomment-126725763.

It can be used to determine a list of audio volume generators, but determining the dominant speakers is probably best done using other techniques. See:
https://jitsi.org/publications/nossdav2015lastn.pdf

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

The use case for this BTW is that this is the best way to drive the active speaker indication in a conference roster list.

—
Reply to this email directly or view it on GitHub.