W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2012

[Bug 15747] Echo cancellation API

From: <bugzilla@jessica.w3.org>
Date: Sun, 29 Jan 2012 21:40:24 +0000
To: public-webrtc@w3.org
Message-Id: <E1RrcU4-0003vS-1V@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15747

Timothy B. Terriberry <tterribe@vt.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tterribe@vt.edu

--- Comment #2 from Timothy B. Terriberry <tterribe@vt.edu> 2012-01-29 21:40:23 UTC ---
(In reply to comment #1)
> - is it correct to place this option on the PeerConnection?

I don't think it is. Echo cancellation should occur using output audio as close
to the speakers as possible to cancel echo in input streams as close to the
microphone as possible. It would seem to me the appropriate place would be
either a LocalMediaStream or the corresponding audio track.

Even if (especially if!) you just planned to play back the stream locally,
you'd want echo cancellation enabled. Alternatively, if didn't want to play or
transmit the stream, but, e.g., just wanted to record it, or use it for
visualization, or something else, you'd want to be able to shut echo
cancellation off. No PeerConnection is involved in any of these cases.

> - to which audio streams does echo cancellation apply, if there are several?
> Should we ignore it and say "the implementation will do the best it can across
> all streams"?

If you put the option at the LocalMediaStream level, I'd say "all of them"
(assuming we even allow more than one). If you put it at the track level, then
this question goes away.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Sunday, 29 January 2012 21:40:27 UTC

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