commit | e01857cca48f8838c3e7d11a67ca377a3e355c60 | [log] [tgz] |
---|---|---|
author | Ilya Nikolaevskiy <ilnik@webrtc.org> | Fri Mar 08 14:25:42 2019 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Mar 08 14:25:47 2019 +0000 |
tree | 3e90deee29a5602d8aefcd2924798a09e2b1bf21 | |
parent | 12abf671fd2028ca249e95bdf0456b15a48136f8 [diff] |
Revert "Reland "Tune vp9 screenshare bitrate and framerate of spatial layers"" This reverts commit 12abf671fd2028ca249e95bdf0456b15a48136f8. Reason for revert: Breaks downstream project. Original change's description: > Reland "Tune vp9 screenshare bitrate and framerate of spatial layers" > > This is a reland without any changes as it seems problems with webrtc-in-chrome importer were flakes or > caused by some issues within chrome codebase. > > Tune vp9 screenshare bitrate and framerate of spatial layers > > VP9 screenshare is not used currently, and with these values according > to local testing with screenshare_loopback, we get performance not worse than current vp8 settings for similar uplink and downlink values. > > Original Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/126226 > > Bug: webrtc:10257 > Change-Id: Ie819d8bbab4f14877daac733d162e5ae7ebf2a8e > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/126460 > Reviewed-by: Johannes Kron <kron@webrtc.org> > Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> > Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#27036} TBR=ilnik@webrtc.org,jeroendb@webrtc.org,kron@webrtc.org Change-Id: I9ad9017b054213f931b3b39c641060d35565f17d No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:10257 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/126523 Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#27037}
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.