- From: Emil Ivov <emcho@jitsi.org>
- Date: Thu, 28 Feb 2013 10:15:25 +0200
- To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
- CC: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On 27.02.13, 20:25, Emil Ivov wrote: > +1 again. It would also if such an API would also the possibility to Awfully sorry! This was supposed to say: "It would also *be great* if such an API would also *provide* the possibility to retrieve audio levels. (Coffee deficiency!) Emil > 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 ) > > Cheers, > Emil >> >> >> On Feb 22, 2013, at 1:19 AM, Magnus Westerlund >> <magnus.westerlund@ericsson.com> wrote: >> >>> WebRTC WG, >>> >>> As editor of the RTP usage specification in RTCWEB WG, we have had >>> a noted issue in our draft specification >>> (https://datatracker.ietf.org/doc/draft-ietf-rtcweb-rtp-usage/). >>> In Section 12.5. of version 05 (Contributing Sources) we had the >>> following: >>> >>> (tbd: does the API need to provide the ability to add a CSRC list >>> to an outgoing packet? this is only useful if the sender is mixing >>> content) >>> >>> This is clearly an API question. We intended to remove it. However, >>> I like to hand it over to you in W3C to consider on the impact on >>> the API this has. >>> >>> From my personal view point this has two aspects: >>> >>> Exposing when a received MediaStreamTrack is actually the mix (or >>> switch) of other MediaStreamTracks, a mix performed by a WebRTC >>> endpoint or RTP middlebox (Mixer). Applications that like to know >>> who are currently seen or audible needs this information mapping. >>> We also have specified an optional to support RTP header extension >>> (RFC6465) that provide energy levels for each contributing source. >>> If that is used, that information would be something an application >>> would like to render somehow. >>> >>> The other aspect is when an WebRTC endpoint mixes media to produce >>> a new MediaStreamTrack, for example with the Web Audio API, then >>> one need to consider if and how the CSRC list is populated. >>> >>> Cheers >>> >>> Magnus Westerlund >>> >>> ---------------------------------------------------------------------- >>> >>> > Multimedia Technologies, Ericsson Research EAB/TVM >>> ---------------------------------------------------------------------- >>> >>> > Ericsson AB | Phone +46 10 7148287 >>> Färögatan 6 | Mobile +46 73 0949079 SE-164 80 >>> Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com >>> ---------------------------------------------------------------------- >>> >>> >>> > _______________________________________________ >>> rtcweb mailing list rtcweb@ietf.org >>> https://www.ietf.org/mailman/listinfo/rtcweb >> >> _______________________________________________ rtcweb mailing list >> rtcweb@ietf.org https://www.ietf.org/mailman/listinfo/rtcweb >> > -- https://jitsi.org
Received on Thursday, 28 February 2013 08:15:54 UTC