From: Josh Allmann <joshua.allmann@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>, Josh Allmann <joshua.allmann@gmail.com> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/h264_mp4toannexb: Prepend SPS/PPS to buffering period SEI Date: Thu, 1 Aug 2024 14:45:05 -0700 Message-ID: <CAPEbzdvsFNVVaQZ-LnGrgg4dxYCN9=2CAMYzjKDsPHs04ZtX5g@mail.gmail.com> (raw) In-Reply-To: <172249913303.21344.17598597604771690214@lain.khirnov.net> On Thu, 1 Aug 2024 at 00:58, Anton Khirnov <anton@khirnov.net> wrote: > Thanks for the review. > Quoting Josh Allmann (2024-07-09 21:05:47) > > Encoders may emit a buffering period SEI without a corresponding > > SPS/PPS if the SPS/PPS is carried out-of-band, eg with avcc. > > > > During Annex B conversion, this may result in the SPS/PPS being > > inserted *after* the buffering period SEI but before the IDR NAL. > > > > Since the buffering period SEI references the SPS, the SPS/PPS > > needs to come first. > > --- > > > > Notes: > > v2: Updated FATE test refs > > > > libavcodec/bsf/h264_mp4toannexb.c | 13 +++++++++++++ > > tests/ref/fate/h264-bsf-mp4toannexb | 2 +- > > tests/ref/fate/h264_mp4toannexb_ticket2991 | 18 +++++++++--------- > > tests/ref/fate/segment-mp4-to-ts | 12 ++++++------ > > 4 files changed, 29 insertions(+), 16 deletions(-) > > > > diff --git a/libavcodec/bsf/h264_mp4toannexb.c b/libavcodec/bsf/h264_mp4toannexb.c > > index 92af6a6881..6607f1e91a 100644 > > --- a/libavcodec/bsf/h264_mp4toannexb.c > > +++ b/libavcodec/bsf/h264_mp4toannexb.c > > @@ -363,6 +363,19 @@ static int h264_mp4toannexb_filter(AVBSFContext *ctx, AVPacket *opkt) > > if (!new_idr && unit_type == H264_NAL_IDR_SLICE && (buf[1] & 0x80)) > > new_idr = 1; > > > > + /* If this is a buffering period SEI without a corresponding sps/pps > > + * then prepend any existing sps/pps before the SEI */ > > + if (unit_type == H264_NAL_SEI && buf[1] == 0 && !sps_seen && !pps_seen) { > > That 0 should be SEI_TYPE_BUFFERING_PERIOD, right? > Yes - fixed > > + if (s->sps_size) { > > + count_or_copy(&out, &out_size, s->sps, s->sps_size, PS_OUT_OF_BAND, j); > > + sps_seen = 1; > > + } > > + if (s->pps_size) { > > + count_or_copy(&out, &out_size, s->pps, s->pps_size, PS_OUT_OF_BAND, j); > > + pps_seen = 1; > > + } > > Is there a reason to insert the PPS? IIUC only the SPS is needed. > I believe it would be needed if using this bsf with the segment muxer, and segmentation happens on a recovery point (with a buffering period), eg in the test fate-segment-mp4-to-ts . Granted it is kind of incidental that this patch actually fixes that specific case. I have never seen a SPS without a PPS though. Josh _______________________________________________ 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".
prev parent reply other threads:[~2024-08-01 21:45 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-03 21:05 Josh Allmann 2024-07-06 16:37 ` Michael Niedermayer 2024-07-08 22:06 ` Josh Allmann 2024-07-09 19:05 ` Josh Allmann 2024-07-15 17:48 ` Josh Allmann 2024-07-15 17:54 ` Josh Allmann 2024-07-22 23:01 ` Josh Allmann 2024-07-23 0:16 ` Timo Rothenpieler 2024-07-30 20:16 ` Josh Allmann 2024-08-01 7:58 ` Anton Khirnov 2024-08-01 21:36 ` Josh Allmann 2024-08-07 16:13 ` Josh Allmann 2024-08-13 16:57 ` Josh Allmann 2024-08-14 11:45 ` Anton Khirnov 2024-08-01 21:45 ` Josh Allmann [this message]
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='CAPEbzdvsFNVVaQZ-LnGrgg4dxYCN9=2CAMYzjKDsPHs04ZtX5g@mail.gmail.com' \ --to=joshua.allmann@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