commit | 8102a1a8ea497a20fe89dfe480f199023063b18c | [log] [tgz] |
---|---|---|
author | Ilya Nikolaevskiy <ilnik@webrtc.org> | Thu Jan 31 11:57:20 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Jan 31 11:57:37 2019 |
tree | d209bea30ebb91861cb560d4f9b9554bb78cbedb | |
parent | 8a21e1c9c95c9b9b570c84bdfeda0315ede9dc29 [diff] |
Revert "Partial frame capture API part 1" This reverts commit 8a21e1c9c95c9b9b570c84bdfeda0315ede9dc29. Reason for revert: breaks buildbots Original change's description: > Partial frame capture API part 1 > > Define new optional struct in VideoFrame to signal that the frame is a > changed part of a whole picture and add a flag to signal that partial > update may be issued by the VideoFrame source. > > Also, fix too strict assumptions in FrameBuffers PasteFrom methods. > Also, add ability to set a new buffer in video frame. > > > Bug: webrtc:10152 > Change-Id: Ie0da418fd60bc7a34334329292e0b860ec388788 > Reviewed-on: https://webrtc-review.googlesource.com/c/120405 > Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org> > Reviewed-by: Erik Språng <sprang@webrtc.org> > Reviewed-by: Niels Moller <nisse@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#26489} TBR=ilnik@webrtc.org,nisse@webrtc.org,sprang@webrtc.org Change-Id: Ibf61f28e529a444882962b984474d4849bb44e4b No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:10152 Reviewed-on: https://webrtc-review.googlesource.com/c/120760 Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#26490}
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 http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.