commit | ce723234bacfd0eac80a31d2a7540e9e33371175 | [log] [tgz] |
---|---|---|
author | Ilya Nikolaevskiy <ilnik@webrtc.org> | Fri May 24 09:31:46 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Fri May 24 09:31:56 2019 |
tree | d6a69a60e43fa8113337222c4732bbce43e1df70 | |
parent | eb1754c5750dfcad23ac62b47aa3aa2176ae7be2 [diff] |
Revert "VP9 screenshare: Don't base layers frame-rate on input frame-rate" This reverts commit eb1754c5750dfcad23ac62b47aa3aa2176ae7be2. Reason for revert: breaks downstream projects Original change's description: > VP9 screenshare: Don't base layers frame-rate on input frame-rate > > If input framerate is a little unstable, using it to cap layers will > make output framerate even smaller for longer periods of time. > > Also, fix screenshare_loopback test for low-fps vp9 testing. > > Bug: webrtc:10257 > Change-Id: I64aa087e859ab4ab8e484c9ab7f5ac0fb18bd37d > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/138204 > Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org> > Reviewed-by: Sergey Silkin <ssilkin@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#28050} TBR=ilnik@webrtc.org,ssilkin@webrtc.org Change-Id: I82bfbac58249cfe0da5ff565aa97a4745fd078ff No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:10257 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/138213 Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#28051}
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.