12abf671fd
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}
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.
Development
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.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct