d4dbe4527d
The integration relies on GainController2 methods Process() and GetRecommendedInputVolume() to internally take into account whether the input volume controller is enabled in the ctor or not. These methods are called for every frame processed if GainController2 is enabled. Analyze() is called if the input volume controller is enabled. The functionality can be enabled from the APM config and is not enabled by default. If multiple input volume controllers are enabled, an error is logged. Tested: Bitexact on a large number of aecdumps if not enabled Bug: webrtc:7494 Change-Id: I9105483be34eb95fab3c46afbbd368802e956fad Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/282720 Reviewed-by: Alessio Bazzica <alessiob@webrtc.org> Reviewed-by: Sam Zackrisson <saza@webrtc.org> Commit-Queue: Hanna Silen <silen@webrtc.org> Reviewed-by: Per Åhgren <peah@webrtc.org> Cr-Commit-Position: refs/heads/main@{#38776}
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.
Development
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation