Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mpegts: Add AVFMT_FLAG_ALLOW_CODEC_CHANGES (v2)
Date: Fri, 4 Jul 2025 00:01:48 +0200
Message-ID: <20250703220148.GO29660@pb2> (raw)
In-Reply-To: <CAJgjuoxZ2Fj=iT73qiWry2NWRbq88T4Vh_nNr9iu5jH8G8anAA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1938 bytes --]

Hi Pavel

On Mon, Jun 30, 2025 at 11:39:32PM -0600, Pavel Koshevoy wrote:
> On Mon, Jun 30, 2025, 21:46 Michael Niedermayer <michael@niedermayer.cc>
> wrote:
> 
> > On Mon, Jun 30, 2025 at 07:32:36PM -0600, Pavel Koshevoy wrote:
> > > On Mon, Jun 30, 2025 at 3:46 PM Scott Theisen <
> > > scott.the.elm-at-gmail.com@ffmpeg.org> wrote:
> > >
> > > > On 2025/06/29 23:55, Pavel Koshevoy wrote:
> > > > > Make midstream AVStream.codecpar updates optional and disabled
> > > > > by default, so that avformat API clients can enable this feature
> > > > > explicitly when they add support for midstream codec changes.
> > > >
> > > > Is this signaled in any way or is the client expected to check if
> > > > codecpar has changed?
> > > >
> > >
> > > The client is expected to check codecpar for changes ...
> >
> > What performance impact does this have ?
> >
> 
> In my player?  None that I cared to measure

Your player is not the only user of the libavformat API
and with low latency audio codecs tiny packets could require
thousands of "has anything in this AVStream changed" checks per second


> 
> 
> 
> > also how does this align with AV_PKT_DATA_NEW_EXTRADATA
> > and AV_PKT_DATA_PARAM_CHANGE ?
> >
> 
> I don't know anything about them.

you do suggest to make streams change arbitrarily.
Thats a API change, so you should first understand the existing
related APIs

Also teh design of the new API is for all user applications

there needs to be a plan how to support this in ffmpeg and the muxer side

The API is a puzzle piece in this plan. It must fit in, even if
other people work on ffmpeg and the muxers.

Dont you agree with that too ?

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

If a bugfix only changes things apparently unrelated to the bug with no
further explanation, that is a good sign that the bugfix is wrong.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: 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".

  parent reply	other threads:[~2025-07-03 22:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30  3:55 Pavel Koshevoy
2025-06-30 21:45 ` Scott Theisen
2025-07-01  1:32   ` Pavel Koshevoy
2025-07-01  3:46     ` Michael Niedermayer
2025-07-01  5:39       ` Pavel Koshevoy
2025-07-01 14:24         ` Scott Theisen
2025-07-03 22:01         ` Michael Niedermayer [this message]
2025-07-04  5:30           ` Pavel Koshevoy
2025-07-01 14:08     ` Scott Theisen

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=20250703220148.GO29660@pb2 \
    --to=michael@niedermayer.cc \
    --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