This brings QualityScaler much more in line with OveruseFrameDetector. The two classes are conceptually similar, and should be used in the same way. The biggest changes in this CL are: - Quality scaling is now only done in ViEEncoder and not in each encoder implementation separately. - QualityScaler now checks the average QP asynchronously, instead of having to be polled on each frame. - QualityScaler is no longer responsible for actually scaling the frames, but has a callback to ViEEncoder that it uses to express it's desire for lower resolution. BUG=webrtc:6495 Review-Url: https://codereview.webrtc.org/2398963003 Cr-Commit-Position: refs/heads/master@{#15286}
This directory holds a Java implementation of the webrtc::PeerConnection API, as
well as the JNI glue C++ code that lets the Java implementation reuse the C++
implementation of the same API.
To build the Java API and related tests, generate GN projects with:
--args='target_os="android"'
To use the Java API, start by looking at the public interface of
org.webrtc.PeerConnection{,Factory} and the org.webrtc.PeerConnectionTest.
To understand the implementation of the API, see the native code in jni/.