Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Romain Beauxis <romain.beauxis@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: Re: [FFmpeg-devel] [PATCH v2] ogg/vorbis: implement header packet skip in chained ogg bitstreams.
Date: Wed, 23 Jul 2025 14:06:07 -0500
Message-ID: <CABWZ6OS9ZGYRQjv4nB3fsJKfGmDBn=g4AJqTh2QKH2j0xSRL9Q@mail.gmail.com> (raw)
In-Reply-To: <20250621215947.GY29660@pb2>

Le sam. 21 juin 2025 à 16:59, Michael Niedermayer <michael@niedermayer.cc>
a écrit :
>
> On Sat, Jun 21, 2025 at 10:45:32AM +0200, Romain Beauxis wrote:
> > Le dim. 15 juin 2025 à 00:57, Michael Niedermayer
> > <michael@niedermayer.cc> a écrit :
> > >
> > > On Wed, Jun 04, 2025 at 11:58:52AM -0500, Romain Beauxis wrote:
> > > > This is a redo of 574f634e49847e2225ee50013afebf0de03ef013 using a
flat
> > > > memory storage for the extradata.
> > > >
> > > > PR review comments addressed:
> > > > * Use flat memory bytestream
> > > > * Re-use existing xiph extradata layout
> > > >
> > > > ---
> > >
> > > >  libavcodec/vorbisdec.c                     | 42 ++++++++---
> > > >  libavformat/oggparsevorbis.c               | 83
+++++++++++++++++++++-
> > >
> > > patches that change both libraries at the same time are suspect
> > >
> > > if one depends on changes in the other it needs
> > > minor API version bump and seperate patches so extension of
> > > API and use of it are properly tracked and testable
> >
> > If I remember well, according to Andreas Rheinhardt there's no need
> > for an API bump here since the patch is re-using existing extradata
> > bitstream structures.
>
> If there is really no API extension then the micro versions should be
bumped
> so a user knows if the specific version he uses has teh fix.
> Also it may be usefull in bugreports about ogg to know if its prior or
> after this change

Hi Michael,

I have created a PR on code.ffmpeg.org here:
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20026

Would you have a minute to have a look?

This patch is a redo of a patch that was reverted:
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/848ceb1329cb6102df49379430b277dbb3f07569

It would be great to see if it could be included in the next release,
otherwise the round of work on ogg parsing would be incomplete for it.

I'm hoping that the PR can help gather and keep review feedback in one
place.

Thanks,
-- Romain

> thx
>
> [...]
> --
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> Awnsering whenever a program halts or runs forever is
> On a turing machine, in general impossible (turings halting problem).
> On any real computer, always possible as a real computer has a finite
number
> of states N, and will either halt in less than N cycles or never halt.
> _______________________________________________
> 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-07-23 19:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04 16:58 Romain Beauxis
2025-06-10 18:04 ` Romain Beauxis
2025-06-12 11:35   ` Michael Niedermayer
2025-06-14 10:39     ` Romain Beauxis
2025-06-14 22:57 ` Michael Niedermayer
2025-06-21  8:45   ` Romain Beauxis
2025-06-21 21:59     ` Michael Niedermayer
2025-07-23 19:06       ` Romain Beauxis [this message]

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='CABWZ6OS9ZGYRQjv4nB3fsJKfGmDBn=g4AJqTh2QKH2j0xSRL9Q@mail.gmail.com' \
    --to=romain.beauxis@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    /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