darkness
Version 0.5.1
Last revised: September 13, 2006
Generated: September 13, 2006
This document is intended to provide standards for the use of ID3 tags in MPEG 1 Layer III audio. This document is not a reference for ID3 or the MPEG format. This document heavily references ``Standards for Music Information'' [SMI] for purposes of data acquisition and formatting. Fields from [SMI] are referred to as ``SMI fields''. Both ID3 version 1 and version 2 are covered in detail, and mappings between the fields defined in [SMI] and each ID3 standard are provided.
ID3v1 tags must be present in all MPEG 1 Layer III audio files. Specifically, ID3v1.1 must be used; later versions of the ID3v1 standard may be used as long as compatibility is retained.
Table 1 is a list of ID3v1.1 fields and their source fields from [SMI]. In some cases, multiple SMI fields may be listed for a single ID3v1.1 field to indicate that the combined content of those SMI fields must be placed into the ID3v1.1 field; further explanation of such fields follows this section. Note that since there is no published standard for ID3v1.1 field names, the fields' canonical names are used.
| ||||||||||||||
When adding the SMI extra artists field onto the end of the ID3v1.1 artist field, the content of the extra artists field must be placed in parentheses within the ID3v1.1 artist field, and a single space must precede the opening parenthesis. For example, if the SMI artist name field contained ``Some Artist'' and the SMI extra artists field contained ``Another Artist'', the ID3v1.1 artist field would be ``Some Artist (Another Artist)''.
Both the set subtitle and collection subtitle, if any, must each be surrounded by parentheses. If this new parenthetical clause follows a set (non-empty) SMI field, it must be separated from it by a single space. If the collection title and/or subtitle are present and follow the set title and/or subtitle, the collection title/subtitle must be separated from the set title/subtitle by a single hyphen surrounded by exactly one space on each side (`` - '').
The track subtitle and modification subtitle, if one or both exist, must be placed in parentheses and placed after the track title. The opening parenthesis must be separated from the track title by exactly one space. If both the track subtitle and the modification subtitle exist, they must be placed in the same set of parentheses and should be separated from each other by a single hyphen surrounded by exactly one space on eaach side (`` - '').
ID3v1.1 fields are very small relative to the length of most fields for an average track. Because of this, when copying information into ID3v1.1 fields from SMI fields, many fields will have to be truncated. The following rules must be used to truncate ID3v1.1 fields unless specifically excepted elsewhere:
The ID3v1.1 comment field is treated as part of the ID3v1.1 song title field. To use the comment field, the song title field must be ended on a word boundary and remaining content put into the comment field. The normal rules for truncation apply to the combination of these two fields, not to either individually. The exception to this is the case where there is no word boundary in the ID3v1.1 song title field, in which case the song title must be truncated using normal rules and the ID3v1.1 comment field cannot be used.
For example, if the SMI track title were ``Some Title Long Enough To Warrant a Comment That Is Truncated'', the ID3v1.1 song title field would be ``Some Title Long Enough To'' and the comment field would be ``Warrant a Comment That Is''.
The ID3v1.1 field year can only hold four characters. Thus only the YYYY (year) field from the SMI release date field is stored in the ID3v1.1 year field.
When an SMI field is set but contains only tags, this field is considered to be a tag-only SMI field. When filling an ID3v1.1 field and one or more tag-only SMI fields immediately follow a set (non-empty) SMI field, the tags from the tag-only SMI fields must be added as new tags to the first preceeding non-tag-only SMI field. (See [SMI] for what it means to ``add a tag.'') After this merging, the tag-only SMI fields must be considered unset. This process is called coalescing tags.
For example, take a track where the SMI set title is ``Exploding Sheep'', the SMI set subtitle is ``[GB]'', and the SMI collection subtitle is ``[CD 1]''. Without coalescing tags, the ID3v1.1 album field would be ``Exploding Sheep ([GB]) - ([CD 1])''. After coalescing tags, the title becomes ``Exploding Sheep [GB; CD1]''. Note that, since the tag-only fields are considered unset, the various punctuation that was previously added to accomodate them (such as the parentheses and the hyphen) is removed.
ID3v2 tags must be present in all MPEG 1 Layer III audio files. Specifically, ID3v2.4.0 must be used; later versions of the ID3v2 standard may be used as long as compatibility is retained.
Table 2 is a list of ID3v2.4.0 fields and their source fields from [SMI]. In some cases, multiple SMI fields may be listed for a single ID3v2.4.0 field to indicate that the combined content of those SMI fields must be placed into the ID3v2.4.0 field; further explanation of such fields follows this section. The ID3v2.4.0 field names are taken from [ID3v2NF].
The ID3v2.4.0 ``involved people'' list is a mapping of names to roles. The name for the role used must be ``Compilation producer'', with the name being the value of the SMI field compilation producer.
The set or collection subtitle, if any, must be surrounded by parentheses. If the parenthetical clause follows any other text, the clause should be preceded by exactly one space.
The collection position or track position must be separated from the collection total or track total, if any, by a single forward slash (``/'').
The track subtitle, if any, must be separated from the modification subtitle, if any, by a single hyphen surrounded by exactly one space on each side (`` - '').
Due to the extremely large sizes afforded to fields by ID3v2.4.0, there should be no situation in which fields would need to be truncated. In the extreme possibility, the same rules for field truncation as in ID3v1 must be used (section 2.2).
When filling in ID3v2.4.0 fields from SMI fields, tags must be coalesced as in section 2.3.
Version 0.1: - Initial release. Version 0.2: - Fixed a grammar/spelling error or two. Version 0.3: - Corrected the ID3v2 field mappings for the SMI field genre: was TIT1, corrected to TCON. - Added mapping for compilation producer to TIPL. Version 0.4: - Described how the two SMI subtitle fields in the ID3v1.1 song title field should be delimited. - Rewrote some of the general rules for truncating fields. Hopefully the meaning is unchanged. - Removed the last general rule for field truncation, which said that parentheses-delimited content could end without the closing parenthesis. This should be impossible, given thte first rule that no content after the first field can be added unless it fits entirely, and that no first fields are enclosed in parentheses. - Rewrote truncation of song title section somewhat. Version 0.5: - Reworded some sections to make formatting requirements more clear (for example, when talking about adding space before a parenthesis that follows a non-empty field). - Added section on coalescing tags. - Fixed bibliography URLs to point to new site. Version 0.5.1: - Andy corrected my grammar: parenthesis->parentheses in many places. $Revision: 1.5 $
This document was generated using the LaTeX2HTML translator Version 2002-2-1 (1.70)
Copyright © 1993, 1994, 1995, 1996,
Nikos Drakos,
Computer Based Learning Unit, University of Leeds.
Copyright © 1997, 1998, 1999,
Ross Moore,
Mathematics Department, Macquarie University, Sydney.
The command line arguments were:
latex2html -split 0 sid3.tex
The translation was initiated by darkness on 2006-09-13