c8fbd899bd
This CL fixes a few issues where the reported fraction of frames allocated to various temporal layers could be incorrect: * In LibvpxVp8Encoder, calling GetEncoderInfo() while not initialized, or when first configuring with temporal layers and then without, could trigger incorrect fps allocations. * In VP9 when different spatial layers have different max framerates, the layer fps should be compared to the layer with the highest configured fps, not codec_.maxFramerate which is updated to the current input fps on SetRates(). * In EncoderBitrateAdjuster, just warn and ignore if a layer has non-zero bps but zero fps, rather than passing down the chain and risk weird behavior or divide by zero. Bug: b/152040235 Change-Id: I548fb3e099b1ec9f536a7b93313fb40c4d32e596 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/171516 Commit-Queue: Erik Språng <sprang@webrtc.org> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30880}
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