From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] hevcdec: skip slices with missing PPS instead of skipping the entire packet Date: Tue, 28 Dec 2021 11:26:32 -0300 Message-ID: <d5c61f57-e088-ffaa-88c8-0110986814ac@gmail.com> (raw) In-Reply-To: <20211228134929.1164-1-h.leppkes@gmail.com> On 12/28/2021 10:49 AM, Hendrik Leppkes wrote: > Aborting decoding of the entire packet on a missing PPS can result in > missing the actual PPS on streams with badly ordered NALs, where the > SPS/PPS/VPS are stitched to the back of the previous frame, instead of > the beginning of the next frame. > > Instead, skip the undecodable slice, and let the decoder process further > NALs in the same packet. > --- > libavcodec/hevcdec.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/libavcodec/hevcdec.c b/libavcodec/hevcdec.c > index 3aa70e2245..c2451d682e 100644 > --- a/libavcodec/hevcdec.c > +++ b/libavcodec/hevcdec.c > @@ -575,7 +575,7 @@ static int hls_slice_header(HEVCContext *s) > sh->pps_id = get_ue_golomb_long(gb); > if (sh->pps_id >= HEVC_MAX_PPS_COUNT || !s->ps.pps_list[sh->pps_id]) { > av_log(s->avctx, AV_LOG_ERROR, "PPS id out of range: %d\n", sh->pps_id); > - return AVERROR_INVALIDDATA; > + return 1; // skip slice with missing PPS The decoder should IMO also set the output frame's decode_error_flags to FF_DECODE_ERROR_DECODE_SLICES in this scenario. > } > if (!sh->first_slice_in_pic_flag && > s->ps.pps != (HEVCPPS*)s->ps.pps_list[sh->pps_id]->data) { _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2021-12-28 14:26 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-28 13:49 Hendrik Leppkes 2021-12-28 14:26 ` James Almer [this message] 2021-12-28 22:01 ` Hendrik Leppkes 2021-12-28 23:08 ` James Almer 2021-12-30 15:08 ` [FFmpeg-devel] [PATCH v2] " Hendrik Leppkes 2021-12-30 15:13 ` James Almer 2021-12-30 15:26 ` Hendrik Leppkes 2021-12-30 15:31 ` James Almer 2021-12-31 9:22 ` Andreas Rheinhardt
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=d5c61f57-e088-ffaa-88c8-0110986814ac@gmail.com \ --to=jamrial@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git