| Revision as of 18:56, 21 February 2018 editCreak (talk | contribs)17 edits Add TRACKTOTAL as a de facto comment← Previous edit | Revision as of 18:56, 21 February 2018 edit undo400ml pep (talk | contribs)15 edits Undid revision 826920409 by Creak (talk)Tag: UndoNext edit → | ||
| Line 9: | Line 9: | ||
| Any tag name is allowed, and there is no format that the data values must be in. This is in contrast to the ] format used for ]s, which is highly structured. Field names are also permitted to be used more than once. It is encouraged to use this feature to support multiple values, for example two <code>ARTIST=...</code> fields to list both artists of a single composition. | Any tag name is allowed, and there is no format that the data values must be in. This is in contrast to the ] format used for ]s, which is highly structured. Field names are also permitted to be used more than once. It is encouraged to use this feature to support multiple values, for example two <code>ARTIST=...</code> fields to list both artists of a single composition. | ||
| The specification gives several example tag names such as <code>TITLE</code> and <code>TRACKNUMBER</code>. Most applications also support common ''de facto'' standards, such as |
The specification gives several example tag names such as <code>TITLE</code> and <code>TRACKNUMBER</code>. Most applications also support common ''de facto'' standards, such as <code>DISCNUMBER</code>, <code>RATING</code>, and tags for ] information. Ratings are usually mapped as 1-5 stars with 20,40,60,80,100 as the actual string values. | ||
| There are no provisions for storing binary data in Vorbis comments. This is by design; they are intended to be used as part of a ] such as ], and any additional binary data should be encoded into the container as a stream. The exception to this, by popular request, is a proposal to incorporate cover art into a Vorbis comment.<ref>{{cite web|title=VorbisComment, cover art|url=https://wiki.xiph.org/index.php/VorbisComment#Cover_art|website=wiki.xiph.org|publisher=]|accessdate=1 October 2016}}</ref> | There are no provisions for storing binary data in Vorbis comments. This is by design; they are intended to be used as part of a ] such as ], and any additional binary data should be encoded into the container as a stream. The exception to this, by popular request, is a proposal to incorporate cover art into a Vorbis comment.<ref>{{cite web|title=VorbisComment, cover art|url=https://wiki.xiph.org/index.php/VorbisComment#Cover_art|website=wiki.xiph.org|publisher=]|accessdate=1 October 2016}}</ref> | ||
Revision as of 18:56, 21 February 2018
 | This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Vorbis comment" – news · newspapers · books · scholar · JSTOR (February 2016) (Learn how and when to remove this message) |
A Vorbis comment is a metadata container used in the Vorbis, FLAC, Theora, Speex and Opus file formats. It allows information such as the title, artist, album, track number or other information about the file to be added to the file itself. However, as the official Ogg Vorbis documentation notes, “ is meant for short, text comments, not arbitrary metadata; arbitrary metadata belongs in a separate logical bitstream (usually an XML stream type) that provides greater structure and machine parseability.”
Format
A Vorbis tag is a list of fields in the format FieldName=Data. The field name can be composed of printable ASCII characters, 0x20 (space) through 0x7D (‘}’), with 0x3D (‘=’) and 0x7E (‘~’) excluded. It is case insensitive, so artist and ARTIST are the same field. The number of fields and their length is restricted to 4,294,967,295 (the maximum value of an unsigned 32-bit integer), but most tag editing applications impose stricter limits.
The data are encoded in UTF-8, and so any conforming Unicode string may be used as a value.
Any tag name is allowed, and there is no format that the data values must be in. This is in contrast to the ID3 format used for MP3s, which is highly structured. Field names are also permitted to be used more than once. It is encouraged to use this feature to support multiple values, for example two ARTIST=... fields to list both artists of a single composition.
The specification gives several example tag names such as TITLE and TRACKNUMBER. Most applications also support common de facto standards, such as DISCNUMBER, RATING, and tags for ReplayGain information. Ratings are usually mapped as 1-5 stars with 20,40,60,80,100 as the actual string values.
There are no provisions for storing binary data in Vorbis comments. This is by design; they are intended to be used as part of a container format such as Ogg, and any additional binary data should be encoded into the container as a stream. The exception to this, by popular request, is a proposal to incorporate cover art into a Vorbis comment.
See also
References
- "Ogg Vorbis I format specification: comment field and header specification". xiph.org. Xiph.Org Foundation. 2005. Retrieved 18 February 2016.
- "VorbisComment, cover art". wiki.xiph.org. xiph.org. Retrieved 1 October 2016.
External links
- Vorbis Comments specification at Xiph
- Proposed field names at Xiph Wiki
- Proposal for extensions (e.g.: cover art, chapter extension, date and time) at Xiph Wiki
- Chapter mark extension at Xiph Wiki
- Shea, David (Sep 28, 2004). "Proposals for extending Ogg Vorbis comments". Archived from the original on April 2014.
{{cite web}}: Check date values in:|archive-date=(help)
| Xiph.Org Foundation | |
|---|---|
| Ogg Project codecs | |
| Media tools | |
| Related articles | |