93d9ae8a17
We can react just as well at OnEncodeVideoFrame, which is the same behaviour except after checking if the Encoder is paused and the frame dropper. For the initial frame drop, the frame dropper is irrelevant as the frame can not be dropped until we are accepting frames. If we didn't drop the frame, the encoder can't be paused as the data rate is over 0. For the quality rampup experiment, similar for encoder paused - we can't rampup if we are paused anyways since the data rate needs to be non-zero. If we are dropping frames we likely don't want to do quality rampup anyways. Bug: webrtc:11222 Change-Id: Ie3e09d9d8d509dc17ba7a1443cf4747f61c04f6a Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/168601 Reviewed-by: Henrik Boström <hbos@webrtc.org> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Commit-Queue: Evan Shrubsole <eshr@google.com> Cr-Commit-Position: refs/heads/master@{#30539}
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.
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: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct