Reason for revert: Frame rate and freeze detection not working properly after switchCamera(). This is because the previous cameraObserver is not removed before posting a new one. Original issue's description: > VideoCapturerAndroid: Use one thread per startCapture()/stopCapture() session > > Currently, VideoCapturerAndroid sets the thread and handler in the ctor > and clears them in dispose(). This CL sets the handler in startCapture() > instead and clears it in stopCapture(). The purpose is to prepare for > sending in the SurfaceTextureHelper in startCapture() instead of letting > VideoCapturerAndroid create it in the ctor. > > All access to the handler is now synchronized by a lock, and all > Runnables are posted with a token so that they can be removed all at > once in stopCapture() to guarantee that no pending operation will be > executed after stopCapture(). > > BUG=webrtc:5519 > > Committed: https://crrev.com/9cbebee523dbd280a4f67ad414a432ed730f241f > Cr-Commit-Position: refs/heads/master@{#11939} TBR=perkj@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=webrtc:5519 Review URL: https://codereview.webrtc.org/1777253002 Cr-Commit-Position: refs/heads/master@{#11941}
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 VideoCapturerAndroid: Use one thread per startCapture()/stopCapture() session (patchset #2 id:60001 of https://codereview.webrtc.org/1763673002/ )
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%