W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2011

Re: WebRTC requirements for Audio WG

From: Timothy B. Terriberry <tterriberry@mozilla.com>
Date: Wed, 14 Dec 2011 22:55:37 -0800
Message-ID: <4EE999E9.7070106@mozilla.com>
CC: public-webrtc@w3.org, public-audio@w3.org
> I think echo cancellation is potentially relevant to audio; it needs to
> have access to the correlation between "stream that is played out" and
> "stream that comes in (from microphone)". If audio processing happens
> between the PeerConnection and the audio interfaces, echo cancellation
> can turn out to be very difficult to implement without accessing the
> close-to-speaker audio stream. But I'm no expert...

This is true, but there is a lot more than simply audio processing that 
can affect this. Even just playing a file in an <audio> tag during a 
call can pose a significant problem for echo cancellation, as well as 
audio sources outside the browser. But, that said, this seems like a 
browser architecture issue, rather than anything that requires an API 
that needs to be standardized.
Received on Thursday, 15 December 2011 06:56:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:49:57 UTC