Jump to: navigation, search


1,589 bytes added, 18:23, 12 October 2012
Proposed field names: Removed Chapter Extension as it has its own section further down
* [ Ogg Vorbis Comment Field Recommendations]
* [ Proposals for extending Ogg Vorbis comments]
* [[Field names]]
Comments are intended to be free-form, but for the purposes of interoperability, it is helpful to define tag sets for particular applications, and provide some guidelines for machine parsing. Note that some field names have to be non-free-form to achieve machine parsing.
The [ binary FLAC picture structure] is base64 encoded and placed within a vorbis comment VorbisComment with the tag name "METADATA_BLOCK_PICTURE". This is the preferred and recommended way of embedding cover art within vorbis commentsVorbisComments. It has the following benefits:
* Easy to use for developers since the identical (or similar) structure is also used by FLAC and MP3.
* Multiple image blocks MAY be included as separate METADATA_BLOCK_PICTURE comments.
* There may only be one each of picture type (APIC type) 1 and 2 in a Vorbis stream.
* Block order is significant for some types and applications should preserve the comment order when reading or writing Vorbis comment VorbisComment headers. The block order may be used to determine the order pictures are presented to the user.
===== Playback tests =====
* XMPlay 3.4.2: no problem
* Nero ShowTime: no problem
* Songbird 1.8.0: no problem, able to show and edit embedded pictures
'''Tested hardware players'''
* Logitech Squeezebox: doesn't play this file Supported as of January 2009 (and all other oggs with embedded pictureserver version 7.3.3)** Workaround: The needed Server Software (called SqueezeCenter) can convert ogg to mp3 on the fly, and has also no problem to convert oggs with embedded pictures
* Sandisk Sansa Fuze (Firmware 01.01.22): Hangs up when trying to playback the demo file - had to reset the player
** Note: The "Fuze" can play ogg vorbis files which have embedded pictures from "Easytag"
* Cowon D2: no problem (latest Firmware: 2.59, 8GB Version)
* iRiver E100: no problem (latest Firmware: 1.16 G_U, 8GB Version)
* iRiver T20: doesn't play (firmware: 1.71, 1GB)
* Samsung YP-R1: no problem (latest Firmware: 3.07, 16GB Version)
'''Tested tag editors'''
* Easytag 2.1.6: can open the file to edit the normal tag fields
* MP3Tag 2.42e: can open the file to edit the normal tag fields
* MP3Tag 2.47b: is able to show and edit embedded pictures
'''Tested other software'''
* Total Recorder: can open capable to work with artwork according to the file without a problemspecification.
==== Unofficial COVERART field (deprecated) ====
* the cover art can't be linked
* the base64 string is displayed within many tag editors as plain text because of their missing support for this "COVERART" field
* it may breaks the playback on hardware players because of a large vorbis comment VorbisComment headerThe unofficial "COVERART" field is supported for example by such software as AudioShell ( - read/write, and Total Recorder ( only read.
===== Conversion to METADATA_BLOCK_PICTURE =====
* Encode the new picture block, remove the COVERART tag from the comments and add the METADATA_BLOCK_PICTURE entry.
* If multiple tags are being converted the order of the METADATA_BLOCK_PICTURE tags should be the same as that of the COVERART tags they are replacing.
=== Chapter Extension ===
These are used to include navigation points, for example:
CHAPTER001NAME=Chapter 1
See the [[Chapter Extension]] page for more details.
=== Date and time ===
==== ISO proposal ====
The date format for any field describing a date must follow the ISO scheme8601 standard: YYYY-MM-DD, shortened to just YYYY-MM or simply YYYY.
We have been recommending this usage with the DATE tag for some time. It is proposed that the spec be amended to include this information for machinability.
==== Proposal: Inclusion of URL in ENCODER value ====
The encoder field name must be a unique URL providing both encoder software name and version. If no unique URL address is available were both name and version is available; then the version number can be specified by separating with a space character. For example:
The ''Dublin Core Metadata Initiative'' recommends the use of ‘rights’ to describe license and copyright matters. The web feed format Atom 1.0 has implemented a rights element in their specification.
:'''Comment''': The triplet RIGHTS, RIGHTS-DATE, RIGHTS-URI is an example of structured metadata. VorbisComments are inherently unstructured, and this should be respected. Structured metadata belongs in a different stream, such as XML (using [[Metadata#XMLEmbedding|XMLEmbedding]]).
==== Improving existing fields proposal ====
Similar to the DATE tag above, we have generally recommended that a URL uniquely identifying the license be included in the LICENSE field to allow machine identification of the license. This is in agreement with the proposal in the Creative Commons wiki. Since the COPYRIGHT field is a human-readable statement of the copyright, like the proposed RIGHTS tag above, some people include a license url there. Therefore if a url can't be found in a LICENSE tag if any, applications should use one from the COPYRIGHT tag, if any. Contact information for verification, attribution, relicensing, etc. can be obtained from the COPYRIGHT field, but Creative Commons also recommend a separate CONTACT tag for this information. This is reasonable, so we propose it be included.
=== Attributing involved parties ===
The goal is to attribute more persons and organisations involved in audio and music productions to make room for more advanced search and sorting.
'''NO PROPOSAL:''' VorbisComments need a lot of extension beyond just the ARTIST field name. See work at [[M3F]], the proposed XML replacement for VorbisComments for structured metadata.
=== Geo Location fields ===
The existing LOCATION field is meant to carry a human readable location for the recording/creation of the media file.
Having geographical coordinates according to [ WGS84] can be useful as well, especially in a form that can be machine parsed. The agreed format is similar to this [ geo microformat]:
See for detailed information about Replay Gain and how the different values are calculated.
=== Tantalos resource ID ===
Tantalos is a protocol to auto locate and access content in a network scope (normally 'LAN' but can also be bigger like 'company network'). It uses UUIDs to identify resources. There are two groups of those UUIDs: IDs generated using the meta data of the track and IDs generated in some other way (for example random IDs, see UUID specs). The later group may need to be passed with the track. The VCLT Playlist format (see below) uses 'HASH={UUID}id...' with hex-dash format for this (HASH={UUID}e278173d-4d6d-4c66-95ec-4ec85eedc7d1).
--[[User:Ph3-der-loewe|Ph3-der-loewe]] 02:05, 13 December 2011 (PST)
== Other (non-proposed field names) ==
=== VCLT playlist format ===
The VCLT playlist format uses some ''keys'' which look like VorbisComments but they aren't nor they are proposed to become (expect for HASH). This includes the keys STREAMURL, FILENAME, FILEURL, LENGTH, HASH (see above for this one), SIGNALINFO, AUDIOINFO and OFFSET. You can find more infos about those at [].
== Implementations ==
* [ OggImporter] &ndash; imports Ogg Vorbis and Ogg FLAC files to Spotlight importer].* vorbiscomment&ndash; a commandline tool, part of [[VorbisTools]].* [ oggz-comment]&ndash; a commandline tool, part of [[Oggz]] tool. It can add comments to multitrack and video files.

Navigation menu