From: Scott Theisen <scott.the.elm-at-gmail.com@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mpegts: Add AVFMT_FLAG_ALLOW_CODEC_CHANGES (v2)
Date: Tue, 1 Jul 2025 10:24:31 -0400
Message-ID: <e030dd07-ce15-4785-9c14-697c5e08d12e@gmail.com> (raw)
In-Reply-To: <CAJgjuoxZ2Fj=iT73qiWry2NWRbq88T4Vh_nNr9iu5jH8G8anAA@mail.gmail.com>
On 2025/07/01 01:39, 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
MPEG-TS and MPEG-PS can have a new PMT (TS) or PSM (PS) at any time to
do any of the following: modifying current streams, adding new streams,
or removing streams. Therefore, to fully support those containers, you
need to check if the version numbers have changed anyways (or be
notified by a callback).
libavformat/mpeg.c does not use the program_stream_map_version.
Regards,
Scott Theisen
_______________________________________________
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".
next prev parent reply other threads:[~2025-07-01 14:24 UTC|newest]
Thread overview: 7+ 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 [this message]
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=e030dd07-ce15-4785-9c14-697c5e08d12e@gmail.com \
--to=scott.the.elm-at-gmail.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