f7f0b2108f
When MediaStreamVideoSource::RequestRefreshFrame is called, the capturer most often emits a refresh frame. Due to various conditions such as for example timing of prior delivery, these frames can be dropped at various places in the input pipeline into WebRTC. This change ensures the frame cadence adapter repeatedly requests refresh frames at max fps frequency until one is received, in which case the requests cease. Fixed: chromium:1324120 Change-Id: I90f85d31b132b6c441aa1c28c5eff85e3dc365ad Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/263520 Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Commit-Queue: Markus Handell <handellm@webrtc.org> Cr-Commit-Position: refs/heads/main@{#36998}
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: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation