commit | 426b5e7ea12e12b684f283a4a773121faa679e33 | [log] [tgz] |
---|---|---|
author | Sergey Silkin <ssilkin@webrtc.org> | Fri Mar 22 12:52:02 2024 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 22 13:42:44 2024 |
tree | d90f65349d82969e9ca5b13ee5fe5767b13020c6 | |
parent | e0edc2120e72c3174601df6e826fc58b271a7cd0 [diff] |
Revert "Mark frames with inter_layer_predicted=true as delta frames" This reverts commit 7ae48c452abf8694a1b0a7a9a2aef13a9d10298a. Reason for revert: breaks RtpVp9RefFinder Original change's description: > Mark frames with inter_layer_predicted=true as delta frames > > As it is currently implemented, the VP9 depacketizer decides packet's frame type based on p_bit ("Inter-picture predicted layer frame"). p_bit is set to 0 for upper spatial layer frames of keyframe since they do not have temporal refs. This results in marking packets of upper spatial layer frames, and, eventually these frames, of SVC keyframes as "keyframe" while they are in fact delta frames. > > Normally spatial layer frames are merged into a superframe and the superframe is passed to decoder. But passing individual layers to a single decoder instance is a valid scenario too and is used in downstream projects. In this case, an upper layer frame marked as keyframe may cause decoder reset [2] and break decoding. > > This CL changes frame type decision logic in the VP9 depacketizer such that only packets with both P and D (inter-layer predicted) bits unset are considered as keyframe packets. > > When spatial layer frames are merged into a superframe in CombineAndDeleteFrames [1], frame type of the superframe is inferred from the lowest spatial layer frame. > > [1] https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/modules/video_coding/frame_helpers.cc;l=53 > > [2] https://source.corp.google.com/piper///depot/google3/third_party/webrtc/files/stable/webrtc/modules/video_coding/codecs/vp9/libvpx_vp9_decoder.cc;l=209 > > Bug: webrtc:15827 > Change-Id: Idc3445636f0eae0192dac998876fedec48628560 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/343342 > Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> > Commit-Queue: Sergey Silkin <ssilkin@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#41939} Bug: webrtc:15827 Change-Id: I697a057b8b3e88c07499f77c42f014da43cf1dc1 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/343763 Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> Commit-Queue: Sergey Silkin <ssilkin@webrtc.org> Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#41953}
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.