diff options
| author | bemasc@chromium.org <bemasc@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-19 13:20:43 +0000 |
|---|---|---|
| committer | bemasc@chromium.org <bemasc@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-19 13:20:43 +0000 |
| commit | 9e7ee9877dfe191ea72b99c6ae794d95f2d66cf5 (patch) | |
| tree | ca3b7b651acbf072f56e152b5ac5ffc8b84aba4e /google_update | |
| parent | 2ca6ed82cc4e9603c7238aa95feabaa5784e812a (diff) | |
| download | chromium_src-9e7ee9877dfe191ea72b99c6ae794d95f2d66cf5.zip chromium_src-9e7ee9877dfe191ea72b99c6ae794d95f2d66cf5.tar.gz chromium_src-9e7ee9877dfe191ea72b99c6ae794d95f2d66cf5.tar.bz2 | |
Enable WebRTC audio processing on WebAudio inputs.
When a microphone input is routed through WebAudio, the
constraints that were supplied when opening the device are
lost. Without these constraints, we cannot determine
whether the user requested to disable AEC, AGC, etc.
Currently, all these audio processing functions are enabled
by default for microphone inputs, but are always disabled
for WebAudio inputs. They were disabled in Revision 182669
(https://codereview.chromium.org/12220121), in order to
serve the needs of a loopback demo
(http://simpl.info/webrtcwebaudio/). However, these settings
break any actual WebRTC use (i.e. peer-to-peer).
This CL changes the settings to favor the actual use case,
by using settings that match the default microphone behavior, at
the expense of the loopback (demo) case.
BUG=none
TEST=Fixes audio quality problem (echo) in p2p tests.
Review URL: https://chromiumcodereview.appspot.com/16879009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207224 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'google_update')
0 files changed, 0 insertions, 0 deletions