fdemmer
commented
8 years ago the comments are chosen for compatibility with the lastfmplus plugin: https://picard.musicbrainz.org/docs/tags/ (however, at some point i made a mistake and switched 3 and 4, you can fix that in your config: https://github.com/fdemmer/Picard-Last.fm.ng-Plugin/issues/5)
the plugin does not write meta tags directly. it gathers data and puts them into variables, that you can use in scripts or naming rules. picard uses some of those variables to write actual metatags to files. this is the mapping picard uses to put variables into tags on various formats: http://picard.musicbrainz.org/docs/mappings/
in the plugin config.ini, you can set the variable name per category to whatever you want with metatag_track = .... then it depends on picard to what id3 or vorbis or ape metatag that value will be actually written.
afaik, there is no way to force picard to write a "TXXX", since that is id3 specific. also, i think flac uses vorbis tags.
Hi. I love this program. Thank You! I'm curious why you use the 'comment:' tag vs 'TXXX:' for instance: "comment:Songs-DB_Custom2" vs "Songs-DB_Custom2". I'd like to change to the TXXX because MusicBee reads the MP3 tags for: comment:Songs-DB_Occasion comment:Songs-DB_Custom1 comment:Songs-DB_Custom2 comment:Songs-DB_Custom3 comment:Songs-DB_Custom4 correctly, but is unable to read the same tags from FLAC songs. When i view in the tag editor, it shows: Unknown (Songs-DB_Custom3) British (Songs-DB_Custom4) 2010s (Songs-DB_Custom1) Instrumental (Songs-DB_Custom2) Chillout (Songs-DB_Occasion) as the actual tag value(s) for the tag code "comment"
Is this a bug, Whose? Can i change the lasfmng tag codes for those by adding my updated tag codes to the config.ini, will i encounter in problems other than my old lasfm plugin tagged music files now being under a new tag?
Thanks