commit | 90d6efbd4eb4b3a0a6fc26da0bc2f04843865b3e | [log] [tgz] |
---|---|---|
author | Ilya Nikolaevskiy <ilnik@webrtc.org> | Wed Sep 25 09:06:50 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Sep 25 09:06:59 2019 |
tree | 3dafed1a1531636b1505da8dc39c2cfe8f827b6c | |
parent | 7911d3705cd2d9edae147561b7e195197187c264 [diff] |
Revert "VP9 encoder: handle disabled layers correctly" This reverts commit 88fe84b7fbcb8dffe07b98d21d8a11572259c0d0. Reason for revert: Downstream project isn't updated to the latest libvpx roll yet, thus some tests are broken. Original change's description: > VP9 encoder: handle disabled layers correctly > > Now vp9 screenshare would enable new layers as soon as requested and will > force all spatial layers present on the next frame, even if they should be > dropped because of frame-rate limiting. > > This might cause frame-rate liming to be exceeded if layer is toggling on > and off very often, but this situation is bad itself. E.g. in realtime video > it will cause too many key-frames. > > Now SvcRateAllocator and VP9EncoderImpl are aware that there may be some skipped > layers before the first enabled. Key-frames and ss_info triggering logic is also > updated. > > Bug: webrtc:10977 > Change-Id: Ie2555210c0368a1d3c51ddf6670d0052e6d679de > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/153483 > Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org> > Reviewed-by: Sergey Silkin <ssilkin@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#29296} TBR=ilnik@webrtc.org,ssilkin@webrtc.org Change-Id: If33886a5f8a0c3b33168dcadfe45c11a6f4387c1 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:10977 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/154354 Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29299}
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.