Talk:Field names: Difference between revisions
Jump to navigation
Jump to search
(comment on proposal:Picard Tag mapping) |
Martin.leese (talk | contribs) m (Added attribution + section heading) |
||
Line 1: | Line 1: | ||
== Picard == | |||
http://wiki.musicbrainz.org/PicardQt/TagMapping | Hi, you should also consider the tag mapping used by Picard (the Musicbrainz tagger), although Picard isnt as popular as some taggers files tagged with this tagger are tagged comprehensively due to the data-richness of the Musicbrainz database.[http://wiki.musicbrainz.org/PicardQt/TagMapping] | ||
In particular note Picard already uses: | |||
<pre> | |||
COMPOSER | COMPOSER | ||
TRACKTOTAL | TRACKTOTAL | ||
DISCNUMBER | DISCNUMBER | ||
DISCTOTAL | DISCTOTAL | ||
</pre> | |||
but uses | but uses: | ||
<pre> | |||
ENCODEDBY not ENCODED-BY | ENCODEDBY not ENCODED-BY | ||
BARCODE not PRODUCTNUMBER | BARCODE not PRODUCTNUMBER | ||
</pre> | |||
[[User:Ijabz|Ijabz]] 9 November 2009 |
Revision as of 07:19, 9 November 2009
Picard
Hi, you should also consider the tag mapping used by Picard (the Musicbrainz tagger), although Picard isnt as popular as some taggers files tagged with this tagger are tagged comprehensively due to the data-richness of the Musicbrainz database.[1]
In particular note Picard already uses:
COMPOSER TRACKTOTAL DISCNUMBER DISCTOTAL
but uses:
ENCODEDBY not ENCODED-BY BARCODE not PRODUCTNUMBER
Ijabz 9 November 2009