985905d42d
If the RTP header extension playout-delay is used and set to min=0, max>=0, frames are scheduled to be decoded as soon as possible. There's a risk that too many frames are sent to the decoder at once, which may cause problems further down in the video pipeline. This CL adds the fieldtrial WebRTC-ZeroPlayoutDelay with the parameter min_pacing that determines the minimum pacing interval between two frames scheduled for decoding. Bug: None Change-Id: I471f7718761cfce9789b3aa8adea3e8a16ecb2fd Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/223742 Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Commit-Queue: Johannes Kron <kron@webrtc.org> Cr-Commit-Position: refs/heads/master@{#34387}
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