commit | 871e14413253f939b65d83131068e40666e65b66 | [log] [tgz] |
---|---|---|
author | Ilya Nikolaevskiy <ilnik@webrtc.org> | Mon Feb 11 12:35:03 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Feb 11 14:20:37 2019 |
tree | 8b4d06f466077455631b1fb34708ae8bc7c370b8 | |
parent | 421c85935126c5c529149236fb5de4caaf5b925f [diff] |
Revert "Reland "Partial frame capture API part 1"" This reverts commit 12e5d392cc8fc0ba7a04587c190daa4232e412bb. Reason for revert: Partial Capture API is not needed, according to new info from the Chrome team. Original change's description: > Reland "Partial frame capture API part 1" > > Reland with fixes to undefined behavior. > > 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. > > Original Reviewed-on: https://webrtc-review.googlesource.com/c/120405 > > Bug: webrtc:10152 > Change-Id: I85790dfc7cec2f23abfe9d6cd18dc76a0c343bc0 > Reviewed-on: https://webrtc-review.googlesource.com/c/120780 > Reviewed-by: Niels Moller <nisse@webrtc.org> > Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> > Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#26493} TBR=ilnik@webrtc.org,nisse@webrtc.org,sprang@webrtc.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: webrtc:10152 Change-Id: I1c1dd51a8b5a09f743f212336beb01447f60f26e Reviewed-on: https://webrtc-review.googlesource.com/c/122092 Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Reviewed-by: Niels Moller <nisse@webrtc.org> Reviewed-by: Erik Språng <sprang@webrtc.org> Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#26638}
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.