From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Revert "avformat/mpegts: update stream info when PMT ES stream_type changes"
Date: Sat, 14 Jun 2025 22:50:30 +0200
Message-ID: <20250614205030.GL29660@pb2> (raw)
In-Reply-To: <CAJgjuoxN6JdWgU65=tAZNZCsdj7p=rZNwxmcU=4MtM5=AgCLoA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1043 bytes --]
On Sat, Jun 14, 2025 at 01:15:24PM -0600, Pavel Koshevoy wrote:
> On Fri, Jun 13, 2025 at 3:48 PM Pavel Koshevoy <pkoshevoy@gmail.com> wrote:
>
> >
> >
> > On Fri, Jun 13, 2025 at 2:46 PM Michael Niedermayer <
> > michael@niedermayer.cc> wrote:
> >
> >>
> >> <snip>
>
> >
> >> Pavel, are you ok with this being reverted or do you want to submit a
> >> patch that puts this behind some runtime flag ?
> >>
> >
> > I'd prefer a runtime flag, but idk how to do that, some pointers to
> > examples might help.
> >
>
> Should I just add a new option to avformat/mpegts.c `options`?
> There is also `raw_options` for mpegtsraw demuxer -- IDK what that's for.
> Should the new option be added to MPEGTS_OPTIONS or just `options`?
> Is "reprobe_stream_if_pmt_es_stream_type_changes" option name acceptable?
iam fine with that name, its a bit long though
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
It is what and why we do it that matters, not just one of them.
[-- 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".
next prev parent reply other threads:[~2025-06-14 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 12:25 Michael Niedermayer
2025-06-13 20:46 ` Michael Niedermayer
2025-06-13 21:48 ` Pavel Koshevoy
2025-06-14 19:15 ` Pavel Koshevoy
2025-06-14 20:50 ` Michael Niedermayer [this message]
2025-06-13 22:06 ` Pavel Koshevoy
2025-06-14 20:47 ` Michael Niedermayer
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=20250614205030.GL29660@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