| commit | 2c47235b0ef1c7bc1aeadc7d0e3aed18e131b3c7 | [log] [tgz] |
|---|---|---|
| author | Tommi <tommi@webrtc.org> | Sun Feb 06 12:17:33 2022 +0100 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Feb 07 08:15:43 2022 +0000 |
| tree | 0ba2c1055864895277381f4a93fa40f8e27d2aca | |
| parent | ad3b3237a1c6c9f4eb54f26a6a5e7967389ce8f9 [diff] |
Reland "Use non-proxied source object in VideoTrack." This is a reland of 3eb29c12358930a60134f185cd849e0d12aa9166 This reland doesn't contain the AudioTrack changes (see original description) that got triggered in some cases and needs to be addressed separately. Original change's description: > Use non-proxied source object in VideoTrack. > > Use the internal representation of the video source object from the > track. Before there were implicit thread hops due to use of the proxy. > > Also, override AudioTrack's enabled methods to enforce thread > expectations. > > Bug: webrtc:13540 > Change-Id: I4bc7aca96d6fc24f31ade45e47f52599f1cc2f97 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/250180 > Reviewed-by: Harald Alvestrand <hta@webrtc.org> > Commit-Queue: Tomas Gunnarsson <tommi@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#35911} Bug: webrtc:13540 Change-Id: I59997be174cc9278e3e5910d493efd5352e6de68 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/250940 Auto-Submit: Tomas Gunnarsson <tommi@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35924}
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.