commit | 1109b59d0c59fa178e9dff3c6154b717af6aea5f | [log] [tgz] |
---|---|---|
author | Jeroen de Borst <jeroendb@webrtc.org> | Thu Mar 07 20:44:55 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Mar 07 20:45:08 2019 |
tree | 9e110d23e816ce371c4917b15a4251fb803ae9f6 | |
parent | 2c7b9825bcd1497953322b67311a50b92b310c52 [diff] |
Revert "Tune vp9 screenshare bitrate and framerate of spatial layers" This reverts commit aaf3cb3adb618a9f9b14931876b9050201396bee. Reason for revert: Chrome importer consitently failing after this change Original change's description: > 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. > > Bug: webrtc:10257 > Change-Id: Icabac04fbd3d616412bbae59291a1fc026d0a504 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/126226 > Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org> > Reviewed-by: Johannes Kron <kron@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#27023} TBR=ilnik@webrtc.org,kron@webrtc.org Change-Id: I1ef1eeec8fe87a7662a354ef6362b7d463b2bb4c No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:10257 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/126340 Reviewed-by: Jeroen de Borst <jeroendb@webrtc.org> Commit-Queue: Jeroen de Borst <jeroendb@webrtc.org> Cr-Commit-Position: refs/heads/master@{#27027}
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.