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>
Subject: Re: [FFmpeg-devel] [PATCH v6 3/9] libavformat/oggparsevorbis.c: Don't append new metadata.
Date: Mon, 24 Feb 2025 09:34:28 -0600
Message-ID: <CABWZ6OT3J8pNgoCYaYiGtq0MkmG85HHEuuzpK86BxvtM5tf-QA@mail.gmail.com> (raw)
In-Reply-To: <CABWZ6OTD3ReQiTCZLRY65Nd1=2k6muB41a08Dge0CQM=MaiNMQ@mail.gmail.com>

Le lun. 24 févr. 2025 à 00:19, Romain Beauxis
<romain.beauxis@gmail.com> a écrit :
>
> Le dim. 23 févr. 2025 à 20:43, Michael Niedermayer
> <michael@niedermayer.cc> a écrit :
> >
> > On Tue, Feb 18, 2025 at 11:24:39PM -0600, Romain Beauxis wrote:
> > > See before/after vorbis tests in following patch.
> > >
> > > ---
> > >  libavformat/oggparsevorbis.c | 4 +---
> > >  1 file changed, 1 insertion(+), 3 deletions(-)
> >
> > This breaks:
> >
> > ./ffprobe -hide_banner multi-performer.ogg 2>&1 | grep 'performer '
> >
> >
> >       performer       : prophetik (saxophone);Usa (percussion)
> > vs.
> >       performer       : Usa (percussion)
>
> Do you have a sample/file you can share to reproduce this?

Ok I see, it's in the specs:

Field names are not required to be unique (occur once) within a
comment header. As an example, assume a track was recorded by three
well know artists; the following is permissible, and encouraged:

              ARTIST=Dizzy Gillespie
              ARTIST=Sonny Rollins
              ARTIST=Sonny Stitt

https://xiph.org/vorbis/doc/v-comment.html

Thanks for pointing out, I'll address and will send an updated patch set.

Any other feedback meanwhile?

-- Romain
_______________________________________________
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-02-24 15:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19  5:24 [FFmpeg-devel] [PATCH v6 0/9] Properly decode ogg metadata in ogg/{vorbis, flac, opus} chained bitstreams Romain Beauxis
2025-02-19  5:24 ` [FFmpeg-devel] [PATCH v6 1/9] libavcodec/decode.c: Add generic metadata injection using AV_PKT_DATA_METADATA_UPDATE Romain Beauxis
2025-02-19  5:24 ` [FFmpeg-devel] [PATCH v6 2/9] tests: Add stream dump test API util Romain Beauxis
2025-02-19  5:24 ` [FFmpeg-devel] [PATCH v6 3/9] libavformat/oggparsevorbis.c: Don't append new metadata Romain Beauxis
2025-02-24  2:43   ` Michael Niedermayer
2025-02-24  6:19     ` Romain Beauxis
2025-02-24 15:34       ` Romain Beauxis [this message]
2025-02-24 17:17         ` Romain Beauxis
2025-02-19  5:24 ` [FFmpeg-devel] [PATCH v6 4/9] tests: Add chained ogg/vorbis stream dump test Romain Beauxis
2025-02-19 17:53   ` Romain Beauxis
2025-02-19  5:24 ` [FFmpeg-devel] [PATCH v6 5/9] libavformat/oggdec.h, libavformat/oggparsevorbis.c: Factor out vorbis metadata update mechanism Romain Beauxis
2025-02-19  5:24 ` [FFmpeg-devel] [PATCH v6 6/9] libavformat/oggparseflac.c: Parse ogg/flac comments in new ogg packets, add them to ogg stream new_metadata Romain Beauxis
2025-02-19  5:24 ` [FFmpeg-devel] [PATCH v6 7/9] tests: Add chained ogg/flac stream dump test Romain Beauxis
2025-02-21 11:01   ` Michael Niedermayer
2025-02-21 15:40     ` Romain Beauxis
2025-02-19  5:24 ` [FFmpeg-devel] [PATCH v6 8/9] libavformat/oggparseopus.c: Parse comments from secondary chained streams header packet Romain Beauxis
2025-02-19  5:24 ` [FFmpeg-devel] [PATCH v6 9/9] tests: Add chained ogg/opus stream dump test Romain Beauxis
2025-02-19 18:17 ` [FFmpeg-devel] [PATCH v6 0/9] Properly decode ogg metadata in ogg/{vorbis, flac, opus} chained bitstreams Lynne
2025-02-19 18:57   ` Romain Beauxis
2025-02-21 15:41     ` 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=CABWZ6OT3J8pNgoCYaYiGtq0MkmG85HHEuuzpK86BxvtM5tf-QA@mail.gmail.com \
    --to=romain.beauxis@gmail.com \
    --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