We are already asserting in tryDeliverTextureFrame() that we are on the SurfaceTextureHelper handler thread, but this behavior isn't guaranteed by Android. Also updated docs for OnTextureFrameAvailableListener, since other classes (e.g. capturers) were also asserting that they were called on the SurfaceTextureHelper thread. Bug: webrtc:8087, b/64609528 Change-Id: I47148c452f66f24477e438b06ef124a96965853d Reviewed-on: https://chromium-review.googlesource.com/610495 Reviewed-by: Sami Kalliomäki <sakal@webrtc.org> Commit-Queue: Jonathan Yu <yujo@chromium.org> Cr-Commit-Position: refs/heads/master@{#19398}
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%