40217c3718
A recent cl (https://codereview.webrtc.org/2510583002) introduced an issue where the initial rate allocation (call to VideoBitrateAllocator and any associated temporal layers) uses framerate = 0 fps. This may cause issues, including having the rate control in ScreenshareLayers ramp up too slowly. This CL make the initial call use VideoCodec.maxFramerate as framerate. Also expanded unit tests. BUG=webrtc:6301 Review-Url: https://codereview.webrtc.org/2513383002 Cr-Commit-Position: refs/heads/master@{#15166}
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. This page is maintained by the Google Chrome team.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://chromium.googlesource.com/external/webrtc
- 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