commit | 6a871d34878a0e301925e243ec994c7c2e88d136 | [log] [tgz] |
---|---|---|
author | Tommi <tommi@webrtc.org> | Sat May 09 20:16:08 2020 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Sat May 09 21:30:40 2020 +0000 |
tree | 731572a24856b6d39f3a6e1ed9fdb2b78bf391a1 | |
parent | 358070668499fba841f8cb1e9475720a60de9f04 [diff] |
Revert "Remove playout delay lock." This reverts commit c623495fd1ff90aada0eb625af91ec17843fefd0. Reason for revert: Need to look into failure in remoting_unittests in Chrome (Webrtc/ConnectionTest.SecondCaptureFailed/0). It looks like the order FrameBuffer2 calls into VCMTiming while receiving frames and updating playout delay values, needs to be synchronized better. Original change's description: > Remove playout delay lock. > Now update the playout delay and related stats on the worker thread. > > This was previously reviewed here: > https://webrtc-review.googlesource.com/c/src/+/172929/ > > With the exception of reducing unnecessarily broad > lock scope in one function in rtp_rtcp_impl.cc > and added comments in rtp_streams_synchronizer.h > > Bug: webrtc:11489 > Change-Id: I77807b5da2accfe774255d9409542d358f288993 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/174200 > Commit-Queue: Tommi <tommi@webrtc.org> > Reviewed-by: Erik Språng <sprang@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#31193} TBR=tommi@webrtc.org,sprang@webrtc.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: webrtc:11489 Change-Id: I9149025d2fc10686314e6d4e89d1b92125650c36 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/174757 Reviewed-by: Tommi <tommi@webrtc.org> Commit-Queue: Tommi <tommi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#31197}
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.
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.