commit | 4847ae6b51ea55b9db9bf16c7b97c3cb8d000f23 | [log] [tgz] |
---|---|---|
author | sprang <sprang@webrtc.org> | Tue Jun 27 14:06:52 2017 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Jun 27 14:06:52 2017 |
tree | c3834a0dc026351c3daef368adb4d0680cae26d1 | |
parent | f0a6fb19c6e8a7fc7c3da6be7b268bb376d33701 [diff] |
Reland of Periodically update codec bit/frame rate settings. Patch set 1 is a reland + trivial rebase. Patch set >= 2 contains bug fixes. > Original issue's description: > > Fix bug in vie_encoder.cc which caused channel parameters not to be updated at regular intervals, as it was intended. > > > > That however exposes a bunch of failed test, so this CL also fixed a few other things: > > * FakeEncoder should trust the configured FPS value rather than guesstimating itself based on the realtime clock, so as not to completely undershoot targets in offline mode. Also, compensate for key-frame overshoots when outputting delta frames. > > * FrameDropper should not assuming incoming frame rate is 0 if no frames have been seen. > > * Fix a bunch of test cases that started failing because they were relying on the fake encoder undershooting. > > * Fix test > > > > BUG=7664 > > > > Review-Url: https://codereview.webrtc.org/2883963002 > > Cr-Commit-Position: refs/heads/master@{#18473} > > Committed: https://chromium.googlesource.com/external/webrtc/+/6431e21da672a5f3bbf166d3d4d98b171d015706 BUG=webrtc:7664 Review-Url: https://codereview.webrtc.org/2953053002 Cr-Commit-Position: refs/heads/master@{#18782}
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.