From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v8 0/8] Properly decode ogg metadata in ogg/{vorbis, flac, opus} chained bitstreams
Date: Mon, 17 Mar 2025 01:20:42 +0100
Message-ID: <20250317002042.GY4991@pb2> (raw)
In-Reply-To: <CABWZ6OTK4+F_kuPUcSGtokK+Uv=pPiFsti3R98N+kA0NPEwrTA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1519 bytes --]
On Sat, Mar 15, 2025 at 07:08:05PM -0500, Romain Beauxis wrote:
> Hi all!
>
>
> Le jeu. 13 mars 2025 à 08:43, Michael Niedermayer
> <michael@niedermayer.cc> a écrit :
> >
> > Hi Romain
> >
> > On Tue, Mar 11, 2025 at 11:56:37AM -0500, Romain Beauxis wrote:
> > > Le mar. 11 mars 2025 à 11:55, Romain Beauxis
> > > <romain.beauxis@gmail.com> a écrit :
> > > >
> > > > This is a series of patches to allow proper decoding of ogg metadata in chained
> > > > `ogg/vorbis, `ogg/flac` and `ogg/opus` streams.
> > > >
> > > > ## Changes since last version:
> > > > * Moved textual reference output for tests to test/ref/fate
> > > > * Updated test binary to only output stream metadata when
> > > > AVSTREAM_EVENT_FLAG_METADATA_UPDATED flag is set.
> > >
> > > Again, forgot to add that test samples are available here:
> > > https://www.dropbox.com/scl/fo/xrtrna2rxr1j354hrtymq/AGwemlxHYecBLNmQ8Fsy--4?rlkey=lzilr4m9w4gfdqygoe172vvy8&dl=0
>
> Any update on this? Or concerns re: the samples?
>
> I've got more work ready to send, I'd love to finish this patch set to
> get the next one rolling.
the files contain "metadata: encoder=Lavc61.19.100"
So they are version dependant which is a problem for reference files
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Into a blind darkness they enter who follow after the Ignorance,
they as if into a greater darkness enter who devote themselves
to the Knowledge alone. -- Isha Upanishad
[-- 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-03-17 0:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 16:55 Romain Beauxis
2025-03-11 16:55 ` [FFmpeg-devel] [PATCH v8 1/8] libavcodec/decode.c: intercept `AV_PKT_DATA_METADATA_UPDATE` packet extra data, attach them to the next decoded frame Romain Beauxis
2025-03-11 16:55 ` [FFmpeg-devel] [PATCH v8 2/8] tests: Add stream dump test API util Romain Beauxis
2025-03-11 16:55 ` [FFmpeg-devel] [PATCH v8 3/8] tests: Add chained ogg/vorbis stream dump test Romain Beauxis
2025-03-11 16:55 ` [FFmpeg-devel] [PATCH v8 4/8] libavformat/oggdec.h, libavformat/oggparsevorbis.c: Factor out vorbis metadata update mechanism Romain Beauxis
2025-03-11 16:55 ` [FFmpeg-devel] [PATCH v8 5/8] libavformat/oggparseflac.c: Parse ogg/flac comments in new ogg packets, add them to ogg stream new_metadata Romain Beauxis
2025-03-11 16:55 ` [FFmpeg-devel] [PATCH v8 6/8] tests: Add chained ogg/flac stream dump test Romain Beauxis
2025-03-11 16:55 ` [FFmpeg-devel] [PATCH v8 7/8] libavformat/oggparseopus.c: Parse comments from secondary chained streams header packet Romain Beauxis
2025-03-11 16:55 ` [FFmpeg-devel] [PATCH v8 8/8] tests: Add chained ogg/opus stream dump test Romain Beauxis
2025-03-11 16:56 ` [FFmpeg-devel] [PATCH v8 0/8] Properly decode ogg metadata in ogg/{vorbis, flac, opus} chained bitstreams Romain Beauxis
2025-03-13 13:42 ` Michael Niedermayer
2025-03-13 15:33 ` Romain Beauxis
2025-03-16 0:08 ` Romain Beauxis
2025-03-17 0:20 ` Michael Niedermayer [this message]
2025-03-17 0:59 ` Romain Beauxis
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=20250317002042.GY4991@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