- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Thu, 08 Dec 2011 13:48:07 +0100
- To: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
- Cc: public-webrtc@w3.org
Le jeudi 08 décembre 2011 à 12:02 +0100, Stefan Hakansson LK a écrit : > > Reading through the use cases, none of them seems to suggest a case > > where the Web app needs to have specific control on echo cancellation. > > Can anyone think of a reason why it should? Shouldn't this be something > > that "just" happens whenever audio streams are exchanged? or should it > > only happen for some audio streams? > > My default view is the same (i.e. just happens). But this has not really > been discussed, and there can be reasons for giving control: > * The echo canceller introduces a lot of clipping (or other artefacts), > and there is no need since the user uses a head set > * The echo canceller consumes a lot of CPU (and is not needed) > It can be noted that if you go into "settings" of many commercial > clients today you get the option to disable the EC I think these reasons could all be handled (and probably be better handled) by the browser offering a user interface, rather than by each Web app having to deal with it. > > I'm not clear if there is anything that we need from the Audio WG on > > this bit, if it is all to be handled on the browser side. We may need to > > have a flag on audio tracks to enable/disable echo cancellation (if > > there are indeed use cases for that), but I don't think we should expect > > each Web app to manually use the audio API to do echo cancellation. > > Agree! OK; probably worth including in our feedback to the audio WG if consensus emerges on this. Dom
Received on Thursday, 8 December 2011 12:48:34 UTC