bc771b7585
In balanced adaptation mode, a 1280x720 feed would only ever be reduced in resolution twice, and would never have its framerate reduced (due to an interaction with MinFps()). This change removes the hard limits entirely, instead relying only on kMinFramerateFps and VideoEncoder::ScalingSettings::min_pixels_per_frame. Deleted SinkWantsFromOveruseDetector test because it duplicates other tests. Fixed DoesntAdaptDownPastMinFramerate; it wasn't testing what it claimed to because it wasn't updating the fake clock correctly, meaning FPS was detected as 0, meaning framerate adaptation was never triggered. Bug: webrtc:8068, b/38207842 Change-Id: If99d0e74c1334879c1b0c3117eb079f5f2139851 Reviewed-on: https://webrtc-review.googlesource.com/31644 Reviewed-by: Åsa Persson <asapersson@webrtc.org> Commit-Queue: Jonathan Yu <yujo@chromium.org> Cr-Commit-Position: refs/heads/master@{#21312}
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