commit | 0dcb470cfe8576bfd55ab4ef1345a063a43ef0d0 | [log] [tgz] |
---|---|---|
author | Evan Shrubsole <eshr@google.com> | Thu May 07 13:45:14 2020 +0200 |
committer | Commit Bot <commit-bot@chromium.org> | Thu May 07 12:22:10 2020 +0000 |
tree | d095c97df00bcef3a10d412eb71f401d9159e069 | |
parent | ab866a2ccbf595af7c8a8646a890548463ea936f [diff] |
[Adaptation] Adapt up requires previous underuse The problem is that a resource that signals Underuse would be able to trigger an adapt up when it was never limited in the past. This means that an underused resource would be able to negate the adaptations made for an overused one. For example, consider a fast CPU on a bad link. The QP for the image is high but the CPU is underused. Without requiring previous underuse, everytime the QP would signal overuse and trigger an adpatation down, the CPU would signal underuse and trigger an adaptation up. This works today as we want by using the active counts in the VideoStreamEncoderResourceManager. This change makes it a normal behaviour independant of active counts. The problem with active counts is that is only works with 2 resources. When resources are injectable it no longer works as expected. Bug: webrtc:11522, webrtc:11523 Change-Id: I140636ce206d74e00a6b6f8558162bb8afffda1c Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/174482 Commit-Queue: Evan Shrubsole <eshr@google.com> Reviewed-by: Henrik Boström <hbos@webrtc.org> Cr-Commit-Position: refs/heads/master@{#31181}
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.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.