90a7e2ceba
Timestamps are currently dead-reckoned for repeated frames in zero-hertz mode. This leads to an ever increasing totalPacketSendDelay metric in chrome://webrtc-internals which is bad. Fix this by tracking the origin timestamp of the first delay and measuring time's progression since then. A unit test was added which fails with the previous version. go/rtc-0hz-present Bug: chromium:1255737 Change-Id: I8627b91424f9bc56305b1dbd6a4c0624b6b3669d Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/242863 Reviewed-by: Erik Språng <sprang@webrtc.org> Commit-Queue: Markus Handell <handellm@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35595}
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