commit | 1158bff15f33c467543928dd6a49cb6ad04da1ba | [log] [tgz] |
---|---|---|
author | Tommi <tommi@webrtc.org> | Fri Feb 11 15:08:33 2022 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 11 16:03:14 2022 |
tree | 169e453f259714442635a91e34d7366244f84c59 | |
parent | 9a6097046eddc984e649bfe9831a2da7668cb20e [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. Another change in this re-land is that instead of the `state` property of the VideoTrack be marshalled to the signaling thread, it's readable from the calling thread. Previously this was marshalled to the worker and the original changed that to the signaling thread (same as for AudioTrack) - but in case that's causing downstream problems this reland uses BYPASS_PROXY_CONSTMETHOD0 for the `state()` accessor of the VideoTrack proxy. 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: Icb3e165f07240ae10730a316d3a8a3b2b9167d82 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/251387 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Tomas Gunnarsson <tommi@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35979}
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.