commit | f8e7ccb9679b542a183790ca0040ab616ca8718d | [log] [tgz] |
---|---|---|
author | Elad Alon <eladalon@webrtc.org> | Thu Jan 24 12:38:36 2019 +0100 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Jan 24 12:21:00 2019 +0000 |
tree | b058c1e294f284d23c79440d15732520c591dec9 | |
parent | 2d0505017a9044e0529712b3cc5460ca32f71cc4 [diff] |
Create new RTCP feedback message - LossIndication Create a new RTCP feedback message for reporting the loss and/or non-decodability of video frames, to be used by the upcoming injectable VideoFrameBufferController. The new feedback message should report: 1. The sequence number of the last decoded non-discardable video frame. (TBD: If a multi-packet frame, should it be the sequence number of the first, last, or any of the packets?) 2. The sequence number of the last received RTP packet in the stream. 3. A decodability flag, whose specific meaning depends on the last-received RTP sequence number. The decodability flag is true if and only if all of the frame's dependencies are known to be decodable, and the frame itself is not yet known to be unassemblable. * Clarification #1: In a multi-packet frame, the first packet's dependencies are known, but it is not yet known whether all parts of the current frame will be received. * Clarification #2: In a multi-packet frame, the dependencies would be unknown if the first packet was not received. Then, the packet will be known-unassemblable. Bug: webrtc:10226 Change-Id: I1563c944477e3ed40235e82ab99a439414632aff Reviewed-on: https://webrtc-review.googlesource.com/c/118931 Commit-Queue: Elad Alon <eladalon@webrtc.org> Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> Reviewed-by: Björn Terelius <terelius@webrtc.org> Cr-Commit-Position: refs/heads/master@{#26387}
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.