Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Zhao Zhili <quinkblack-at-foxmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/decode: Workaround for media100 decoding failure issue
Date: Wed, 11 Jun 2025 14:44:11 +0800
Message-ID: <tencent_E04D99CFBCD53A270038DF96474D32201F07@qq.com> (raw)
In-Reply-To: <GV1P250MB0737A782E64421C7B1E985678F75A@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>



> On Jun 11, 2025, at 13:55, Andreas Rheinhardt <andreas.rheinhardt@outlook.com> wrote:
> 
> Zhao Zhili:
>> From: Zhao Zhili <zhilizhao@tencent.com>
>> 
>> This is a regression since 1c170613.
>> ---
>> libavcodec/decode.c | 11 ++++++++---
>> 1 file changed, 8 insertions(+), 3 deletions(-)
>> 
>> diff --git a/libavcodec/decode.c b/libavcodec/decode.c
>> index ef09568381..7e47a2971c 100644
>> --- a/libavcodec/decode.c
>> +++ b/libavcodec/decode.c
>> @@ -204,9 +204,14 @@ static int decode_bsfs_init(AVCodecContext *avctx)
>>     ret = av_bsf_init(avci->bsf);
>>     if (ret < 0)
>>         goto fail;
>> -    ret = avcodec_parameters_to_context(avctx, avci->bsf->par_out);
>> -    if (ret < 0)
>> -        goto fail;
>> +    /* Don't copy par_out to avcodec context if bsf changed codec ID,
>> +     * e.g., media100_to_mjpegb
>> +     */
>> +    if (avctx->codec_id == avci->bsf->par_out->codec_id) {
>> +        ret = avcodec_parameters_to_context(avctx, avci->bsf->par_out);
>> +        if (ret < 0)
>> +            goto fail;
>> +    }
>> 
>>     return 0;
>> fail:
> 
> We should rather use a clean revert; after all, the internal BSF is
> supposed to be internal and not change the user-visible extradata etc.

Then how to let decoder see new extradata? Access bsf directly?
I’m OK to revert this after extradata can be synced to decoder properly.

AVCodecContext::extradata is owned by codec. Updating extradata can
be a little surprise, but it’s less surprise than change codec id in bsf.

What are the boundaries/limits of bsf’s functionality? Is it allowed for a bsf
to update media type? I remember there is a trac with samples which
can be handled with a video to audio bsf.

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

_______________________________________________
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-06-11  6:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 15:56 Zhao Zhili
2025-06-11  5:55 ` Andreas Rheinhardt
2025-06-11  6:44   ` Zhao Zhili [this message]

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=tencent_E04D99CFBCD53A270038DF96474D32201F07@qq.com \
    --to=quinkblack-at-foxmail.com@ffmpeg.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