| commit | 647bf43dcb2fd16fccf276bd94dc4400728bb405 | [log] [tgz] |
|---|---|---|
| author | sprang <sprang@webrtc.org> | Thu Nov 10 06:46:20 2016 -0800 |
| committer | Commit bot <commit-bot@chromium.org> | Thu Nov 10 14:46:28 2016 +0000 |
| tree | ca54a7f89ce8a4caba08efbc8bc43498685f73c7 | |
| parent | 9d1315a961bdf13ae6765093872fcb82bf9e5787 [diff] |
Reland of Issue 2434073003: Extract bitrate allocation ... This is a reland of https://codereview.webrtc.org/2434073003/ including some fixes for failing test cases. Original description: Extract bitrate allocation of spatial/temporal layers out of codec impl. This CL makes a number of intervowen changes: * Add BitrateAllocation struct, that contains a codec independent view of how the target bitrate is distributed over spatial and temporal layers. * Adds the BitrateAllocator interface, which takes a bitrate and frame rate and produces a BitrateAllocation. * A default (non layered) implementation is added, and SimulcastRateAllocator is extended to fully handle VP8 allocation. This includes capturing TemporalLayer instances created by the encoder. * ViEEncoder now owns both the bitrate allocator and the temporal layer factories for VP8. This allows allocation to happen fully outside of the encoder implementation. This refactoring will make it possible for ViEEncoder to signal the full picture of target bitrates to the RTCP module. BUG=webrtc:6301 Review-Url: https://codereview.webrtc.org/2488833004 Cr-Commit-Position: refs/heads/master@{#15023}
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.