Re: [FFmpeg-devel] [PATCH] avformat/mpegts: update stream info when PMT ES stream_type changes

From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mpegts: update stream info when PMT ES stream_type changes
Date: Sat, 26 Apr 2025 13:19:52 +0200
Message-ID: <20250426111952.GD4991@pb2> (raw)
In-Reply-To: <CAJgjuowYz2mbZjb2oFjSKcHiRhP=W9CiEUGq0C0VCWZG1O8oaQ@mail.gmail.com>

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

On Fri, Apr 25, 2025 at 11:45:08AM -0600, Pavel Koshevoy wrote:
> On Fri, Apr 25, 2025 at 7:40 AM Michael Niedermayer <michael@niedermayer.cc>
> wrote:
> 
> > On Tue, Apr 22, 2025 at 06:51:55PM -0600, Pavel Koshevoy wrote:
> > > I have a couple of .ts captures where video and audio codec changes
> > > even though the PMT version does not change and the PIDs stay the same.
> > >
> > > I've updated fate ts-demux expected results.
> > > ---
> > >  libavformat/mpegts.c    | 2 +-
> > >  tests/ref/fate/ts-demux | 4 ++--
> > >  2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > please send a link to a git repo or base64 encoded attachment the long line
> > in the patch causes problems:
> >
> > Applying: avformat/mpegts: update stream info when PMT ES stream_type
> > changes
> > error: corrupt patch at line 38
> > error: could not build fake ancestor
> >
> >
> interesting, I used git format-patch master and git send-email to submit
> the patch.

Iam also not 100% sure but overly long lines cause problems somewhere

> I can send it manually as an attachment if that's what you are asking for,
> but I haven't had these problems with other patches I've submitted with git
> send-email in the past.

yes, i can apply the new one fine

> I can also just push the changes to git master if you approve, since I have
> commit access.

There are several people who know TS better than me

thx

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

Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.

[-- 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".