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] Revert "avcodec/decode: Fix avcodec parameters when bsfs, are enable by decoder"
Date: Sun, 15 Jun 2025 23:22:55 +0800
Message-ID: <tencent_94AE563A39C1C1B4E46ACE03316BDA7C120A@qq.com> (raw)
In-Reply-To: <AS8P250MB0744B0D0C14542DFC8EA1F6A8F71A@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>



> On Jun 15, 2025, at 23:17, Andreas Rheinhardt <andreas.rheinhardt@outlook.com> wrote:
> 
> Zhao Zhili:
>>> Otherwise the extradata used would be ISOBMFF if the input is
>>> even though we use the *_mp4toannexb BSFs to convert it to
>>> annex B to feed it to the actual decoder.
>>> 
>>> (The mediacodec decoders also use said BSFs, yet they process
>>> the extradata in a way that works even when using the ISOBMFF
>>> extradata; in fact, using the converted extradata would break
>>> their check for whether to warn for missing extradata for
>>> the ISOBMFF without-in-band-header profiles.
>>> 
>>> Furthermore, there are several users of the *_mp4toannexb BSFs
>>> that don't ever touch extradata. They have not been touched.)
>> 
>> The solution is fragile and easy to be broken. It doesn’t look like a better
>> solution than avcodec_parameters_to_context.
>> 
> 
> Do you still think this way in light of my reply
> (https://ffmpeg.org/pipermail/ffmpeg-devel/2025-June/344986.html)?
> 

Please apply.

> - 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-15 15:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 15:25 Andreas Rheinhardt
2025-06-11 16:00 ` Zhao Zhili
2025-06-11 16:40   ` Andreas Rheinhardt
2025-06-15 15:17   ` Andreas Rheinhardt
2025-06-15 15:22     ` Zhao Zhili [this message]
2025-06-11 16:51 ` [FFmpeg-devel] [PATCH 3/3] fate/video: Add media100 test Andreas Rheinhardt
2025-06-12  0:28   ` compn

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_94AE563A39C1C1B4E46ACE03316BDA7C120A@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