PlayoutFrequency(), at least, is called ~200 times a second. The others appear to not be in practice, but it's unclear what value they serve. They were traces before https://chromium-review.googlesource.com/c/518133/, which was more reasonable, as you could enable them for just audio coding traces. But now that they are just logs, they make all VERBOSE logging unusable. Bug: webrtc:7959 Change-Id: I190a61c8ff4c0f047798087e80adbb41d791fc29 Reviewed-on: https://chromium-review.googlesource.com/563881 Reviewed-by: Minyue Li <minyue@webrtc.org> Commit-Queue: Noah Richards <noahric@chromium.org> Cr-Commit-Position: refs/heads/master@{#18956}
Revert of Test and fix for huge bwe drop after alr state. (patchset #13 id:320001 of https://codereview.webrtc.org/2931873002/ )
Reland of PyLint fixes for tools-webrtc and webrtc/tools (patchset #1 id:1 of https://codereview.webrtc.org/2737233003/ )
…
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 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%