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

Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in the API?

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Thu, 28 Feb 2013 09:53:27 +0100
Message-ID: <512F1B07.1030404@ericsson.com>
To: public-webrtc@w3.org
In the settings proposal (that is discussed in the Media Capture TF), 
audio level ("volume") is a property of an audio source that can be read 
from an API on a AudioStreamTrack [1].

I think this is the right place for this kind of info

[1] 
https://dvcs.w3.org/hg/dap/raw-file/tip/media-stream-capture/proposals/SettingsAPI_proposal_v6.html#source-state-api-extensions-to-audiostreamtrack

Stefan


On 2013-02-28 01:21, Justin Uberti wrote:
> Chrome currently surfaces audio level information via the getStats API,
> albeit not for mixed audio levels.
>
>
> On Wed, Feb 27, 2013 at 10:33 AM, Cullen Jennings <fluffy@iii.ca
> <mailto:fluffy@iii.ca>> wrote:
>
>
>     On Feb 27, 2013, at 10:25 AM, Emil Ivov <emcho@jitsi.org
>     <mailto:emcho@jitsi.org>> wrote:
>
>      > It would also if such an API would also the possibility to
>      > retrieve audio levels from the RTP (Magnus already mentioned RFC6465)
>      > so that applications can render such information.
>      >
>      > (Like this for example: http://goo.gl/QTaqy )
>
>     +1 on that too
>
>     _______________________________________________
>     rtcweb mailing list
>     rtcweb@ietf.org <mailto:rtcweb@ietf.org>
>     https://www.ietf.org/mailman/listinfo/rtcweb
>
>
Received on Thursday, 28 February 2013 08:53:51 UTC

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