|
MusicBrainzTag
This page has not been reviewed by our documentation team (more info).
MusicBrainz Metadata Tags (ID3 and Vorbis/FLAC Comment)Status: The information on this page is complete as of tunepimp Subversion snapshot 2006-01-13. Applications that read or write metadata tags from music files should follow one consistent specification for what MusicBrainz information is stored where and in what tag. That way all the work of the various tagger applications will contribute to a well connected and clean body of metadata. Any application that deals with music should be able to read the MusicBrainzIdentifier ID3v2 Tag specificationsSee ID3v2Tags for a list of proposed frames tagger applications could write. The following descriptions are summerized in a table below, for more information on how to use ID3v2 tags in your own applications read the specifications on http://www.id3.org/. Note: for each text frame (TXXX) the encoding of the value strings can be defined in the frame header. ID3v2.3 supports UTF-16 and ISO-8859-1 encoded strings; ID3v2.4 has addional support for UTF-8 and UTF-16BE. MusicBrainz Identifiers must be encoded as ISO-8859-1 strings. ID3v2 frames can be stored in any order in the MP3 file. General FramesThe following frames are used for the regular information from the database: TPE1 for the main artist name, TALB for the album name, TIT2 for the track title, TRCK for the track number on the album (without total number of tracks in the old MusicBrainzTagger and PicardTagger < 0.5.1 and with totals since PicardTagger 0.5.1). TCMP is a nonstandard tag that defines a track as being part of a compilation (VA album) if set to 1 or part of a single artist album if set to 0. It is used by the iTunes music player software. Artist SortnameThe artist sortname is stored in the TSOP frame for ID3v2.4 and in the experimental XSOP frame for ID3v2.3. Release DateID3v2.3 is missing a standard frame for a detailed date. Therefore the experimental XDOR frame is used and the additional TORY that stores the year of release as a 4 digit number only is used. In ID3v2.4 only the TDRL frame is used to store the complete release date in Music Brainz IdentifierTo store the MusicBrainzIdentifier MusicBrainz Track IdentifierThe MusicBrainz Track Id is the internal unique ID MusicBrainz defines for every object in its database. It is stored in the special UFID frame, that contains two parts: The Owner Identifier selects the namespace where the identifies is unique. For MusicBrainz it is be guaranteed that this ID is unique on the server; therefore the default owner identifier is MusicBrainz Artist IdentifierThe MusicBrainz Artist Id is stored in a user defined TXXX text information frame, encoded as a MusicBrainz Album IdentifierThe MusicBrainz Album Id is stored in a user defined TXXX text information frame, encoded as a MusicBrainz Album Artist IdentifierThe MusicBrainz Album Artist Id is used to store an artist identifier for the album the track is on. This is only for VariousArtistsRelease It is stored in a user defined TXXX text information frame, encoded as a MusicBrainz Album StatusThis stores the status of the album the track is from, encoded as a MusicBrainz Album TypeThis type the status of the album the track is from, encoded as a MusicIP PUID IdentifierThe MusicIP PUID is stored in a user defined TXXX text information frame, encoded as a Vorbis/FLAC comment specificationsIn contrast to the various possibilities of ID3 tagging, Vorbis and FLAC tags are stored in a unified way. All strings are encoded as UTF-8, tagged data is stored in the so called comment header, each key value pair is specified as a tripplet of the form: Note, that The different comment names and their equivalent ID3v3 frames can be found in the table below. Overview
Proposed additions
MusicBrainz DiscID IdentifierThe MusicBrainz DiscID is stored in a user define TXXX text information frame, encoded as a
|
| Original Design|vacubomb.com |
Contact details |
Server version: RELEASE-20090524 |