| commit | 40217c3718b9c6c53f399420d679b3d581886b89 | [log] [tgz] |
|---|---|---|
| author | sprang <sprang@webrtc.org> | Mon Nov 21 13:41:52 2016 |
| committer | Commit bot <commit-bot@chromium.org> | Mon Nov 21 13:42:04 2016 |
| tree | 85600c1f290ffdf2a27dd1602d1fe518613bc6c4 | |
| parent | 57c1ad3b16b222d5e63bf94d96a32c652e2e59d8 [diff] |
Initial rate allocation should not use fps = 0 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.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.