Some tags provide the MusicBrainz Identifier (MBID) of the entity. The MBID is a 32-character identifier assigned to an entity (e.g.: artist, album, track or work) to uniquely identify the entity. For more information about MBIDs, please see the MusicBrainz Identifier page in the MusicBrainz documentation.
Tags will not be created and will not be available as variables if there was no value retrieved for the tag from the MusicBrainz database.
Some of these tags are only supported for certain file types or tag formats. Please see the Picard Tag Mapping section for details.
Track Relationship Tags
If you enable “Use track relationships” in the Option settings, you get these extra tags:
The names of the arrangers associated with the track. These can include the instrument and orchestra arrangers, and could be associated with the release, recording or work. (since Picard 0.10)
The names of the composers for the associated work.
The sort names of the composers for the associated work.
The names of the conductors associated with the track. These can include the conductor and chorus master, and could be associated with the release or recording.
The director of a track as provided by the Video Director or Audio Director relationship in MusicBrainz. (Since Picard 2.6, updated in Picard 2.9)
The names of the DJ mixers for the track. (since Picard 0.9)
The names of the engineers associated with the track.
Work lyric language as per ISO 639-3 if a related work exists. (since Picard 0.10)
The licenses associated with the track, either through the release or recording relationships. (since Picard 1.0)
The names of the lyricists for the associated work.
The names of the “Mixed By” engineers associated with the track. (since Picard 0.9)
The MBID for the Work if a related work exists.
The names of the performers for the specified type. These types include:
vocals or instruments for the associated release or recording, where <type> can be “vocal”, “guest guitar”, “solo violin”, etc.
the orchestra for the associated release or recording, where <type> is “orchestra”
the concert master for the associated release or recording, where <type> is “concertmaster”
The names of the producers for the associated release or recording.
The names of the remixer engineers associated with the track.
The name of the work associated with the track. (since Picard 1.3)
A multi-value tag containing the names of the writers associated with the related work. (since Picard 1.0). This is not written to most file formats automatically. You can merge this with composers with a script like:$copymerge(composer, writer)
Some tags such as performer are available as both track and release level relationships, and the values may be different depending on which relationship options are enabled.
If you enable “Use genres from MusicBrainz”, you get:
A multi-value tag containing the specified genre information from MusicBrainz (since Picard 2.1, earlier versions used folksonomy tags)