891419f8e8
The video send pipeline uses the magic value 0 for an unset ntp time. However, the receive pipeline uses the magic value -1 for unset (unclear where, it seems it behaved differently a few months ago). This makes cl https://codereview.webrtc.org/2469993003/ fail the P2PTestConductor.ForwardVideoOnlyStream, because that cl removes code which always clears the ntp time, and enables propagation of ntp time from the receive pipeline to the send pipeline. Treating ntp time <= 0 as unset is a small improvement. Ultimately, a VideoFrame shouldn't carry an ntp time at all. BUG=webrtc:5740,webrtc:6977 Review-Url: https://codereview.webrtc.org/2620383005 Cr-Commit-Position: refs/heads/master@{#16035}
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. This page is maintained by the Google Chrome team.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://chromium.googlesource.com/external/webrtc
- 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