From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/h264_mp4toannexb: Prepend SPS/PPS to buffering period SEI
Date: Tue, 23 Jul 2024 02:16:46 +0200
Message-ID: <beccdcc8-c1cd-48d1-bf95-857c6043c7e6@rothenpieler.org> (raw)
In-Reply-To: <CAPEbzdtFKQi+gRQRV1Qtd57kw9Pu90OaEi_KQrS8t-e4ERy6BA@mail.gmail.com>
On 23/07/2024 01:01, Josh Allmann wrote:
> On Tue, 9 Jul 2024 at 12:06, Josh Allmann <joshua.allmann@gmail.com> wrote:
>>
>> 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(-)
>>
>
> Ping again for review. Looking at the FATE output, this patch fixes a number
> of things - see [1] for details
patch generally looks good to me, but I'm not closely familiar with the
code there.
_______________________________________________
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:[~2024-07-23 0:17 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 [this message]
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
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=beccdcc8-c1cd-48d1-bf95-857c6043c7e6@rothenpieler.org \
--to=timo@rothenpieler.org \
--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