commit | 96f2c971617fd0e45e3e76eee56d67f21577e343 | [log] [tgz] |
---|---|---|
author | Sergey Silkin <ssilkin@webrtc.org> | Wed Sep 05 21:07:17 2018 +0200 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Sep 11 07:08:36 2018 +0000 |
tree | 5c8a0c9a8aaeeaa81e3cfbb134c299f406b6cfaa | |
parent | 8b0aed1dd62c09fa4567e7325b982c1ced682746 [diff] |
Reland "Frame rate controller per spatial layer." This is a reland of ae9e188e67a489db597224e3cfcfdee04edf0cba Original change's description: > Frame rate controller per spatial layer. > > This allows VP9 encoder wrapper to control frame rate of each spatial > layer. The wrapper configures encoder to skip encoding spatial layer > when actual frame rate exceeds the target frame rate of that layer. > Target frame rate of high spatial layer is expected to be equal or > higher then that of low spatial layer. For now frame rate controller > is only enabled in screen sharing mode. > > Added unit test which configures encoder to produce 3 spatial layers > with frame rates 10, 20 and 30fps and verifies that absolute delta of > final and target rate doesn't exceed 10%. > > Bug: webrtc:9682 > Change-Id: I7a7833f63927dd475e7b42d43e4d29061613e64e > Reviewed-on: https://webrtc-review.googlesource.com/96640 > Commit-Queue: Sergey Silkin <ssilkin@webrtc.org> > Reviewed-by: Erik Språng <sprang@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#24593} TBR=sprang@webrtc.org Bug: webrtc:9682 Change-Id: Idcce315890c79301da532f9ba4997e9606f73fb0 Reviewed-on: https://webrtc-review.googlesource.com/99340 Reviewed-by: Sergey Silkin <ssilkin@webrtc.org> Commit-Queue: Sergey Silkin <ssilkin@webrtc.org> Cr-Commit-Position: refs/heads/master@{#24669}
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.