Added an "enable-audio-processor" flag and WebRtcAudioProcessor class

content/public/common/content_switches.cc

Index: content/public/common/content_switches.cc
diff --git a/content/public/common/content_switches.cc b/content/public/common/content_switches.cc
index 66403b20a9eed81804ff6ea4e784dd0afc84f048..6fe2e050a30513d1c8da95d61ca824d29d3f2b86 100644
--- a/content/public/common/content_switches.cc
+++ b/content/public/common/content_switches.cc
@@ -913,6 +913,9 @@ const char kZygoteCmdPrefix[]               = "zygote-cmd-prefix";
 const char kZygoteProcess[]                 = "zygote";
 
 #if defined(ENABLE_WEBRTC)
+// Enable WebRtc audio processor in Chrome.

[Henrik Grunell, 2013/11/01 07:22:36]

I think it would be nice to have a name (of both the variable and the flag) that
shows that this will run audio processing at a different place than without the
flag. The audio processing is always enabled. Though it's hard to find a very
good name, I'd like to hear what the other reviewers think of this? One idea
(from the previous CL) could be something like "use-audio-processing-per-track".

Despite the name, write in the comment what this does (enables audio processing
on a webrtc track in Chrome, disables it in the webrtc stack).

[no longer working on chromium, 2013/11/01 11:44:43]

updated the comment a bit, and I am still opened to the naming, lets wait for
other reviewers' opinions.

+const char kEnableWebRtcAudioProcessor[]    = "enable-audio-processor";
+
 // Disable WebRTC device enumeration.
 const char kDisableDeviceEnumeration[]      = "disable-device-enumeration";