commit | afb3fc35581b91dc8b967fd5c5af1222e06532d0 | [log] [tgz] |
---|---|---|
author | Erik Språng <sprang@webrtc.org> | Tue Dec 19 11:21:04 2017 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Dec 19 11:21:11 2017 |
tree | 44db65c660dd8fd5a0d5dbe8acc4cef7f35c6686 | |
parent | 69c67e02e2d991371d27cfd5e7622c05be6e054a [diff] |
Revert "Smoother frame dropping when screenshare_layers limits fps" This reverts commit 28a06b16cc4daa9f380ad45af8acfd11b6057283. Reason for revert: Causes some unexpected perf changes. Original change's description: > Smoother frame dropping when screenshare_layers limits fps > > Currently, when input fps is higher than the configured target fps in > screenshare_layers, we drop frames with the help of a rate tracker using > a one second sliding window. This is not optimal. > For instance, given a 5fps limit and a 30fps capturer, the window will > not be saturated until we have added the first 5 frames. Then we will > drop all frames until the oldest one drops out, at which point we can > immediately fill it's place. This results in quick 5 frame bursts every > second. > > In addition to rate tracker, also set a limit on minimum interval > required between input frames, based on target frame rate. > > Bug: webrtc:4172 > Change-Id: I49f0abf4d549673cc6b3fafe580b529ea3feaf57 > Reviewed-on: https://webrtc-review.googlesource.com/34380 > Commit-Queue: Erik Språng <sprang@webrtc.org> > Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#21325} TBR=ilnik@webrtc.org,sprang@webrtc.org Change-Id: I7ca5b0c847310dbb11dce28773082eac946c0ba4 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:4172 Reviewed-on: https://webrtc-review.googlesource.com/34780 Reviewed-by: Erik Språng <sprang@webrtc.org> Commit-Queue: Erik Språng <sprang@webrtc.org> Cr-Commit-Position: refs/heads/master@{#21354}
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.