Reason for revert: Breaks Android it looks like. See your own try jobs and https://build.chromium.org/p/client.webrtc/builders/Android32%20Tests%20%28L%... Original issue's description: > Drop the 16kHz sample rate restriction on AECM and zero out higher bands > > The restriction has been removed completely and AECM now supports any > number of higher bands. But this has been achieved by always zeroing out the > higher bands, instead of applying a constant gain which is the average over half > of the lower band (like it is done for the AEC), because that would be > non-trivial to implement and we don't want to spend too much time on AECM, since > we want to get rid of it in the long term anyway. > > R=peah@webrtc.org, solenberg@webrtc.org, tina.legrand@webrtc.org > > Committed: https://crrev.com/f687d53aabee0523ce6e9e0636163af8df120e41 > Cr-Commit-Position: refs/heads/master@{#11931} TBR=peah@webrtc.org,turaj@webrtc.org,tina.legrand@webrtc.org,solenberg@webrtc.org,aluebs@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review URL: https://codereview.webrtc.org/1781893002 Cr-Commit-Position: refs/heads/master@{#11932}
Revert of Drop the 16kHz sample rate restriction on AECM and zero out higher bands (patchset #3 id:40001 of https://codereview.webrtc.org/1774553002/ )
Revert of Drop the 16kHz sample rate restriction on AECM and zero out higher bands (patchset #3 id:40001 of https://codereview.webrtc.org/1774553002/ )
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. This page is maintained by the Google Chrome team.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://chromium.googlesource.com/external/webrtc
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
Description
The idea is to make CMake build for WebRTC m130 version - for audio processing module
Languages
C++
90.3%
Java
2.9%
C
2.2%
Objective-C++
2%
Python
1.3%
Other
1%