| commit | 26091b1118e37b5cbbfe0de9869127fd5c1b01d0 | [log] [tgz] |
|---|---|---|
| author | perkj <perkj@webrtc.org> | Thu Sep 01 08:17:40 2016 |
| committer | Commit bot <commit-bot@chromium.org> | Thu Sep 01 08:17:43 2016 |
| tree | dc50c0b97bbbc9035467f8842ba4492c47a6bc8b | |
| parent | 9f8e37b6f833cb6c821c6f401421b7c33cbe4b27 [diff] |
This reverts commit 8eb37a39e79fe1098d3503dcb8c8c2d196203fed. Chrome now have its own implementation of TaskQueues that is based on Chrome threads. cl was originally reviewed here: https://codereview.webrtc.org/2060403002/ - Add task queue to Call with the intent of replacing the use of one of the process threads. - Split VideoSendStream in two. VideoSendStreamInternal is created and used on the new task queue. - BitrateAllocator is now created on libjingle's worker thread but always used on the new task queue instead of both encoder threads and the process thread. - VideoEncoderConfig and VideoSendStream::Config support move semantics. - The encoder thread is moved from VideoSendStream to ViEEncoder. Frames are forwarded directly to ViEEncoder which is responsible for timestamping ? and encoding the frames. TBR=mflodman@webrtc.org BUG=webrtc:5687 Review-Url: https://codereview.webrtc.org/2250123002 Cr-Commit-Position: refs/heads/master@{#14014}
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.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.