Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/1] avcodec/dolby_e: Add error recovery when parse_mantissas run out of bits
Date: Mon, 13 Mar 2023 14:05:12 +0100
Message-ID: <976e459d93e0c73cfd27cfaf9ab79ebd917077c1.camel@haerdin.se> (raw)
In-Reply-To: <20230310091753.10230-2-nicolas.gaullier@cji.paris>

fre 2023-03-10 klockan 10:17 +0100 skrev Nicolas Gaullier:
> +                if (i == c->nb_groups - 1
> +                    && count * size1 > get_bits_left(&s->gb)
> +                    && get_bits_left(&s->gb) >= 0
> +                    && (int)(mnt - c->mantissas) >= MIN_MANTISSAS) {
> +                    av_log(s->avctx, AV_LOG_WARNING, "Truncated
> mantissas @%d, "
> +                        "highest frequencies not recoverable\n",
> (int)(mnt - c->mantissas));
> +                    break;
> +                }

Surely there's a proper way to fix this rather than having an arbitrary
threshold. At the very least the get_bits_left() check could be moved
to before parse_mantissas(). If get_bits_left() is < 0 after
parse_mantissas() then a warning could be issued instead of erroring
out, which should have an effect similar to this.

Is there a spec saying what to do with truncated packets? Since this is
Dolby-E I suspect the answer is "no".

/Tomas

_______________________________________________
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:[~2023-03-13 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10  9:17 [FFmpeg-devel] [PATCH 0/1] " Nicolas Gaullier
2023-03-10  9:17 ` [FFmpeg-devel] [PATCH 1/1] " Nicolas Gaullier
2023-03-13 13:05   ` Tomas Härdin [this message]
2023-03-13 15:07     ` Nicolas Gaullier
2024-03-11 14:01 [FFmpeg-devel] [PATCH 0/1] " Nicolas Gaullier
2024-03-11 14:01 ` [FFmpeg-devel] [PATCH 1/1] " Nicolas Gaullier
2024-03-26 16:16   ` Nicolas Gaullier

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=976e459d93e0c73cfd27cfaf9ab79ebd917077c1.camel@haerdin.se \
    --to=git@haerdin.se \
    --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