commit | 9a99905301ffa8a08a717ddaea3e4879440c97f9 | [log] [tgz] |
---|---|---|
author | Evan Shrubsole <eshr@webrtc.org> | Sun Dec 12 14:27:00 2021 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 31 11:40:27 2022 |
tree | 1d6ab3d9fda7c5c0dd4612ad742e3f52c2d182f9 | |
parent | 538b76a2f11fcf316aae20082d463ba03e437cec [diff] |
Implement FrameBuffer3Proxy This emulates behaviour from frame buffer 2, but does not handle stats. In contrast to frame buffer 2, all work happens on the same task queue. FrameBuffer3Proxy encapsulates FrameBuffer3 and scheduler behind a field trial WebRTC-FrameBuffer3. This separates frame scheduling behaviour into a few components, VideoReceiveStreamTimeoutTracker * Handles the stream timeouts. FrameDecodeScheduler * Manages the scheduling and cancelling of frames being sent to the decoder. FrameDecodeTiming * Handles the timing and ordering of frames to be decoded. Other changes * Adds CurrentSize() method to FrameBuffer3 * Move timing to a separate library * Does a thread check for Receive statistics as this is now on the worker thread. * Adds `FlushImmediate` method to RunLoop so that video_receive_stream2_unittest can pass when scheduling is happening on the worker thread. Change-Id: Ia8d2e5650d1708cdc1be3631a5214134583a0721 Bug: webrtc:13343 Tested: Ran webrtc_perf_tests, video_engine_tests, rtc_unittests forcing frame buffer3 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/241603 Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Reviewed-by: Markus Handell <handellm@webrtc.org> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Reviewed-by: Philip Eliasson <philipel@webrtc.org> Reviewed-by: Tomas Gunnarsson <tommi@webrtc.org> Commit-Queue: Evan Shrubsole <eshr@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35847}
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.