W3C home > Mailing lists > Public > public-webrtc@w3.org > December 2011

Re: Echo cancellation

From: Justin Uberti <juberti@google.com>
Date: Fri, 9 Dec 2011 14:10:41 -0500
Message-ID: <CAOJ7v-3vLJnUR=hANgo2Zt5NodrTDo52LPyQ-wB2zNW5BWHKog@mail.gmail.com>
To: "Robert Wolff (GoCast)" <rwolff@gocast.it>
Cc: Randell Jesup <randell-ietf@jesup.org>, public-webrtc@w3.org
On Fri, Dec 9, 2011 at 2:05 PM, Robert Wolff (GoCast) <rwolff@gocast.it>wrote:

> On Fri, Dec 9, 2011 at 10:52 AM, Justin Uberti <juberti@google.com> wrote:
>
>>
>>
>> We might end up with additional parameters down the road that the app may
>> want to control, so I'd prefer to wrap this property in a MediaOptions
>> object, which could later have other properties (e.g. AGC), and have a
>> callback to indicate changes to that object, i.e.
>>
>> attribute MediaOptions mediaOptions;
>> attribute Function? onmediaoptionschange;
>>
>> I agree Justin. We've been playing with various options within the audio
> options lately and believe exposing these is important. Trying to keep an
> interface simple is great, but the functionality buried in webrtc is great
> and very useful. I'd love to see some optionally usable knobs and levers
> here.


Bob, what options do you have in mind?

To be clear, I'm not advocating for more knobs and levers, but simply
recognizing that we will end up with more, and therefore we should plan
accordingly.


>
> Bob Wolff
> ~~~~~~~~~~~~~~~
> GoCast - Video broadcasting on the go!
> www.GoCast.it <http://www.GoCast.it%20>
>
>
Received on Friday, 9 December 2011 19:11:40 UTC

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