From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2] avcodec/h264_metadata_bsf: remove AUDs at any position
Date: Wed, 8 Feb 2023 12:03:22 +0530
Message-ID: <00d390d4-4885-5854-dad3-a8bf9e250ad0@gyani.pro> (raw)
In-Reply-To: <20230204100657.6882-1-ffmpeg@gyani.pro>
On 2023-02-04 03:36 pm, Gyan Doshi wrote:
> Some files, likely due to faulty packetization or muxing, can have AUDs
> at other positions besides the head unit of a packet. Remove these too.
Plan to push in 24h if no more comments.
> ---
> libavcodec/h264_metadata_bsf.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/libavcodec/h264_metadata_bsf.c b/libavcodec/h264_metadata_bsf.c
> index d318bf0cee..b9cfeaba94 100644
> --- a/libavcodec/h264_metadata_bsf.c
> +++ b/libavcodec/h264_metadata_bsf.c
> @@ -469,12 +469,13 @@ static int h264_metadata_update_fragment(AVBSFContext *bsf, AVPacket *pkt,
> H264MetadataContext *ctx = bsf->priv_data;
> int err, i, has_sps, seek_point;
>
> - // If an AUD is present, it must be the first NAL unit.
> - if (au->nb_units && au->units[0].type == H264_NAL_AUD) {
> - if (ctx->aud == BSF_ELEMENT_REMOVE)
> - ff_cbs_delete_unit(au, 0);
> - } else {
> - if (pkt && ctx->aud == BSF_ELEMENT_INSERT) {
> + if (ctx->aud == BSF_ELEMENT_REMOVE) {
> + for (i = au->nb_units - 1; i >= 0; i--) {
> + if (au->units[i].type == H264_NAL_AUD)
> + ff_cbs_delete_unit(au, i);
> + }
> + } else if (ctx->aud == BSF_ELEMENT_INSERT) {
> + if (pkt) {
> err = h264_metadata_insert_aud(bsf, au);
> if (err < 0)
> return err;
_______________________________________________
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-02-08 6:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 17:51 [FFmpeg-devel] [PATCH] " Gyan Doshi
2023-02-03 15:23 ` Andreas Rheinhardt
2023-02-04 10:06 ` [FFmpeg-devel] [PATCH v2] " Gyan Doshi
2023-02-08 6:33 ` Gyan Doshi [this message]
2023-02-09 9:12 ` Gyan Doshi
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=00d390d4-4885-5854-dad3-a8bf9e250ad0@gyani.pro \
--to=ffmpeg@gyani.pro \
--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