e32ae4f8fb
Without invalidation the codec configuration may not get updated. This is prone to happen when the bandwidth is below the min or above the max in which case the last_encoder_rate_settings_ may have not changed. This led to a regression in b6a45dd, where last_encoder_rate_settings_ would not change the allocation or frame rate, but the frame rate would have been set by the video adapter. Thus the frame rates were set incorrectly, leading to lower values in the regression tests. I have re-run this scenario against some of the metric drops and the regression appears to be fixed. Bug: webrtc:10126 Change-Id: I0fa6c9b71e7aff5dd80e53119db109d97eed98b6 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/154343 Commit-Queue: Evan Shrubsole <eshr@google.com> Reviewed-by: Erik Språng <sprang@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29301}
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.
Development
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.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct