commit | 2e161c4dd6547f5f7accc7241c0c3d224d1d0cb6 | [log] [tgz] |
---|---|---|
author | Mirko Bonadei <mbonadei@webrtc.org> | Thu Feb 20 08:45:01 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Feb 20 11:03:25 2020 |
tree | ba09fee7099723e44c076b4c044ab2bee4268aaf | |
parent | b5ffd4715626241174cbc5eb1ad3f431e73dfc7a [diff] |
Revert "Remove ResourceAdaptationModule::OnMaybeEncodeFrame" This reverts commit 93d9ae8a17f2e7b90641cbac28e740afc67d383a. Reason for revert: Perf regression. Original change's description: > Remove ResourceAdaptationModule::OnMaybeEncodeFrame > > 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} TBR=ilnik@webrtc.org,hbos@webrtc.org,eshr@google.com # Not skipping CQ checks because original CL landed > 1 day ago. No-Try: True Bug: webrtc:11222 Change-Id: Ifb2fc74eb7572568fb0ee1b53a09e4180f87b30c Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/168880 Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30568}
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 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.