1e4d4fdf88
Currently, key frames are scheduled even when the encoder is not reset during reconfigeration. This means whenever new parameters like max bitrate or min bitrate are updated through SetRtpParameters(), the triggered encoder reconfigeration will always schedule key frames even they are not necessary. Since parameters' changes like bitrate doesn't require encoder instance reset. This causes flood of key frames in our app since we do regularly max bitrate update according to server control message. Bug: None Change-Id: I15d953b24c30e6026c0e97b30f44495d845f293f Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/185380 Commit-Queue: Rasmus Brandt <brandtr@webrtc.org> Reviewed-by: Rasmus Brandt <brandtr@webrtc.org> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#32245}
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 here 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