From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Wolfgang Müller" <wolf@oriole.systems>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/id3v2: Add Grouping frame to id3v2.4 metadata table
Date: Mon, 14 Feb 2022 17:18:53 +0100
Message-ID: <164485553344.9519.7488726669466846074@lain.red.khirnov.net> (raw)
In-Reply-To: <20220213134633.52291-1-wolf@oriole.systems>
Quoting Wolfgang Müller (2022-02-13 14:46:33)
> The ID3v2.4.0 standard defines TIT1 as the "Content group description"
> tag [1]. This frame is usually referred to as the "Grouping" tag and in
> de-facto use under that name by Vorbis and APEv2 [2].
>
> This commit introduces a mapping from "TIT1" to "grouping" in the
> id3v2.4 metadata conversion table. This will enable software to access
> it using that name. In particular, MPD will now read this tag correctly
> when using the ffmpeg decoder plugin.
>
> [1] https://id3.org/id3v2.4.0-frames (4.2.1)
> [2] https://picard-docs.musicbrainz.org/en/appendices/tag_mapping.html#grouping-3
>
> Signed-off-by: Wolfgang Müller <wolf@oriole.systems>
> ---
>
> As evident from the commit message, I ran into this using MPD with the
> ffmpeg decoder plugin. MPD relies on these mappings heavily, and I found
> it the easiest place to fix this particular issue, especially if other
> pieces of software can also gain from this.
>
> libavformat/id3v2.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/libavformat/id3v2.c b/libavformat/id3v2.c
> index ff27c062e5..0f9bedea02 100644
> --- a/libavformat/id3v2.c
> +++ b/libavformat/id3v2.c
> @@ -69,6 +69,7 @@ const AVMetadataConv ff_id3v2_4_metadata_conv[] = {
> { "TSOA", "album-sort" },
> { "TSOP", "artist-sort" },
> { "TSOT", "title-sort" },
> + { "TIT1", "grouping" },
> { 0 }
> };
>
> --
> 2.35.1
Looks ok, will push tomorrow
--
Anton Khirnov
_______________________________________________
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".
prev parent reply other threads:[~2022-02-14 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 13:46 Wolfgang Müller
2022-02-14 16:18 ` Anton Khirnov [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=164485553344.9519.7488726669466846074@lain.red.khirnov.net \
--to=anton@khirnov.net \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=wolf@oriole.systems \
/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