From: Zhao Zhili <quinkblack@foxmail.com> To: ffmpeg-devel@ffmpeg.org Cc: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/h264_mp4toannexb: fix missing SPS/PPS to IDR frames Date: Tue, 10 Jan 2023 23:31:14 +0800 Message-ID: <tencent_4153E3F36895DAA9002EA52545330A684805@qq.com> (raw) In-Reply-To: <DU0P250MB0747A782352F0E81DEAB30808FFF9@DU0P250MB0747.EURP250.PROD.OUTLOOK.COM> On Tue, 2023-01-10 at 07:41 +0100, Andreas Rheinhardt wrote: > Zhao Zhili: > > From: Zhao Zhili <zhilizhao@tencent.com> > > > > If there is a single group of SPS/PPS before an IDR frame, but no > > SPS/PPS after that, we will miss the chance to reset > > idr_sps_seen/idr_pps_seen. The result is missing SPS/PPS for all > > IDR frames except the first one. > > > > Signed-off-by: Zhao Zhili <zhilizhao@tencent.com> > > --- > > libavcodec/h264_mp4toannexb_bsf.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/libavcodec/h264_mp4toannexb_bsf.c > > b/libavcodec/h264_mp4toannexb_bsf.c > > index d11be455c2..bbdeca9c44 100644 > > --- a/libavcodec/h264_mp4toannexb_bsf.c > > +++ b/libavcodec/h264_mp4toannexb_bsf.c > > @@ -259,7 +259,7 @@ static int h264_mp4toannexb_filter(AVBSFContext > > *ctx, AVPacket *opkt) > > > > count_or_copy(&out, &out_size, buf, nal_size, > > unit_type == H264_NAL_SPS || unit_type > > == H264_NAL_PPS, j); > > - if (!new_idr && unit_type == H264_NAL_SLICE) { > > + if (unit_type == H264_NAL_SLICE) { > > new_idr = 1; > > sps_seen = 0; > > pps_seen = 0; > > If I understand you correctly, you want that to include the parameter > sets from the extradata to every IDR frame without extradata if said > IDR > frame follows a non-IDR frame after in-band parameter sets. There is > just one problem with this: Said in-band parameter sets might > overwrite > parameter sets from extradata and inserting the outdated parameter > sets > from extradata lateron might make the stream undecodable. It's a good question. Current code works when an IDR has in-band parameter set, which is different than the out-of-band parameter set, and the decoder doesn't miss the in-band parameter set. But there is a high chance the decoder will miss the in-band parameter set for annexb bitstream, e.g., playback at the middle of a live mpegts streams. It's a serious issue of missing periodic in-band parameter set for annexb for a lot of usecases. Handle new parameter set isn't as common as the need of periodic in-band parameter set (I guess). It's not a new issue that this bitstream failed to update the parameter set, for example, it doesn't handle AV_PKT_DATA_NEW_EXTRADATA. I can add support for 1. handling AV_PKT_DATA_NEW_EXTRADATA 2. handling in-band sps/pps But it won't be soon. > > - Andreas > > _______________________________________________ > 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". _______________________________________________ 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:[~2023-01-10 7:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-28 17:20 Zhao Zhili 2023-01-09 16:46 ` Zhao Zhili 2023-01-10 6:41 ` Andreas Rheinhardt 2023-01-10 15:31 ` Zhao Zhili [this message] 2023-01-16 3:23 ` "zhilizhao(赵志立)"
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=tencent_4153E3F36895DAA9002EA52545330A684805@qq.com \ --to=quinkblack@foxmail.com \ --cc=andreas.rheinhardt@outlook.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