commit | 72eeaa3fe4755197f5137d2326a3f62b56d32949 | [log] [tgz] |
---|---|---|
author | Zhi Huang <zhihuang@webrtc.org> | Mon Feb 26 21:03:38 2018 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Feb 26 21:03:44 2018 +0000 |
tree | cc1adc7704295a7cd534dd3d7057fd47acb54599 | |
parent | 9f79a92e2642015c3f6bfde8d3c22920d7e00d98 [diff] |
Revert "Choose between APM-AGC-Limiter and Apm-AGC2-fixed-gain_controller." This reverts commit bd7b461f16b53363e2c510893d8d3aade5737f3a. Reason for revert: Broke the internal project. The issue maybe related to the apm_debug_dump configuration. Original change's description: > Choose between APM-AGC-Limiter and Apm-AGC2-fixed-gain_controller. > > The webrtc::AudioMixer uses a limiter component. This CL changes the > APM-AGC limiter to the APM-AGC2 limiter though a Chrome field trial. > > The new limiter has a float interface. Since we're moving to it, we > now mix in floats as well. After this CL the mixer will support two > limiters. The limiters have different interfaces and need different > processing steps. Because of that, we make (rather big) changes to the > control flow in FrameCombiner. For a short while, we will mix in > deinterleaved floats when using any limiter. > > NOTRY=true > > Bug: webrtc:8925 > Change-Id: Ie296c2b0d94f3f0078811a2a58f6fbf0f3e6e4a8 > Reviewed-on: https://webrtc-review.googlesource.com/56141 > Commit-Queue: Alex Loiko <aleloi@webrtc.org> > Reviewed-by: Gustaf Ullberg <gustaf@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#22185} TBR=gustaf@webrtc.org,aleloi@webrtc.org Change-Id: I3dd1a2b1fca32c4dd046e6fc325744079e3ac5ca No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:8925 Reviewed-on: https://webrtc-review.googlesource.com/57940 Reviewed-by: Zhi Huang <zhihuang@webrtc.org> Commit-Queue: Zhi Huang <zhihuang@webrtc.org> Cr-Commit-Position: refs/heads/master@{#22189}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.