Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Mark Thompson <sw@jkqxz.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v3 2/7] lavc/cbs: APV support
Date: Thu, 24 Apr 2025 21:16:45 +0100
Message-ID: <bf8aebb4-f2d6-4540-a0d8-6898475296e8@jkqxz.net> (raw)
In-Reply-To: <7277e091-01d0-4b06-b995-9edc35e975e9@gmail.com>

On 24/04/2025 01:02, James Almer wrote:
> On 4/23/2025 5:45 PM, Mark Thompson wrote:
>> +static int cbs_apv_split_fragment(CodedBitstreamContext *ctx,
>> +                                  CodedBitstreamFragment *frag,
>> +                                  int header)
>> +{
>> +    uint8_t *data = frag->data;
>> +    size_t   size = frag->data_size;
>> +    uint32_t signature;
>> +    int err, trace;
> 
> To prepare CBS for the presence of extradata, make this function a no-op when header != 0.

Yep, done.

I've also added the check that we actually have 4 bytes available for the signature (missed when I added it to the AVPacket).

>> +
>> +    // Don't include parsing here in trace output.
>> +    trace = ctx->trace_enable;
>> +    ctx->trace_enable = 0;
>> +
>> +    signature = AV_RB32(data);
>> +    if (signature != APV_SIGNATURE) {
>> +        av_log(ctx->log_ctx, AV_LOG_ERROR,
>> +               "Invalid APV access unit: bad signature %08x.\n",
>> +               signature);
>> +        err = AVERROR_INVALIDDATA;
>> +        goto fail;
>> +    }
>> +    data += 4;
>> +    size -= 4;
>> +
>> +    while (size > 0) {
>> +        GetBitContext   gbc;
>> +        uint32_t        pbu_size;
>> +        APVRawPBUHeader pbu_header;
>> +
>> +        if (size < 8) {
>> +            av_log(ctx->log_ctx, AV_LOG_ERROR, "Invalid PBU: "
>> +                   "fragment too short (%"SIZE_SPECIFIER" bytes).\n",
>> +                   size);
>> +            err = AVERROR_INVALIDDATA;
>> +            goto fail;
>> +        }

Thanks,

- Mark

_______________________________________________
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".

  reply	other threads:[~2025-04-24 20:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 20:45 [FFmpeg-devel] [PATCH v3 0/7] " Mark Thompson
2025-04-23 20:45 ` [FFmpeg-devel] [PATCH v3 1/7] lavc: APV codec ID and descriptor Mark Thompson
2025-04-23 20:45 ` [FFmpeg-devel] [PATCH v3 2/7] lavc/cbs: APV support Mark Thompson
2025-04-24  0:02   ` James Almer
2025-04-24 20:16     ` Mark Thompson [this message]
2025-04-23 20:45 ` [FFmpeg-devel] [PATCH v3 3/7] lavf: APV demuxer Mark Thompson
2025-04-24  0:10   ` James Almer
2025-04-24 20:15     ` Mark Thompson
2025-04-23 20:45 ` [FFmpeg-devel] [PATCH v3 4/7] lavc: APV decoder Mark Thompson
2025-04-24  3:04   ` James Almer
2025-04-25 17:25   ` Michael Niedermayer
2025-04-23 20:45 ` [FFmpeg-devel] [PATCH v3 5/7] lavc/apv: AVX2 transquant for x86-64 Mark Thompson
2025-04-24  2:55   ` James Almer
2025-04-24 20:37     ` Mark Thompson
2025-04-24 21:41       ` James Almer
2025-04-23 20:45 ` [FFmpeg-devel] [PATCH v3 6/7] lavc: APV metadata bitstream filter Mark Thompson
2025-04-23 20:45 ` [FFmpeg-devel] [PATCH v3 7/7] lavf: APV muxer Mark Thompson

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=bf8aebb4-f2d6-4540-a0d8-6898475296e8@jkqxz.net \
    --to=sw@jkqxz.net \
    --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