Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Dale Curtis <dalecurtis@chromium.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Check codec_whitelist before reinitializing AVCtx.priv_data.
Date: Tue, 30 Jul 2024 16:14:13 -0700
Message-ID: <CAPUDrwd8n+si-ZeDyNLdF1E+ht4mG7rw2PuFRWASBr9nvo6hgQ@mail.gmail.com> (raw)
In-Reply-To: <CAPUDrwcotq2i9SV20VNiNGZgM6LEBKxhj4tqUy4ZW_vqTo7USQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 548 bytes --]

I realized there are a couple more allocations that can be skipped here
when a codec is not on the allow list. Here's the updated patch.

- dale

On Mon, Jul 29, 2024 at 10:19 AM Dale Curtis <dalecurtis@chromium.org>
wrote:

> This ensures that if a codec isn't on codec_whitelist, its VUI
> information can still be populated during find_stream_info()
> via parsers.
>
> Signed-off-by: Dale Curtis <dalecurtis@chromium.org>
> ---
>  libavcodec/avcodec.c | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
>
>

[-- Attachment #2: no_reinit_v2.patch --]
[-- Type: application/octet-stream, Size: 2105 bytes --]

[-- Attachment #3: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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:[~2024-07-30 23:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 17:19 Dale Curtis
2024-07-30 23:14 ` Dale Curtis [this message]
2024-07-31 11:32   ` Anton Khirnov
2024-07-31 21:10     ` Dale Curtis
2024-07-31 21:29       ` Dale Curtis
2024-07-31 23:18         ` Dale Curtis
2024-08-14 16:44           ` Dale Curtis

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=CAPUDrwd8n+si-ZeDyNLdF1E+ht4mG7rw2PuFRWASBr9nvo6hgQ@mail.gmail.com \
    --to=dalecurtis@chromium.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