Repository navigation
|
Hii I have tried the zero plugin, but can't figure out which field I should be using. musicbrainz_albumcomment isn't in the list, and none of the prefix mb_ or comments fields point to it as far as I can tell. Is zero the best approach here? Or am I able to prevent specific tags from even being pulled in the first place? |
Replies: 1 comment 1 reply
|
Hi! The field you're looking for is So zero is the right approach, you just need that field name: plugins: zero # plus whatever plugins you already use
zero:
fields: albumdisambigThe zero plugin hooks into every tag write, not only imports, so with For the files you already have, run: beet zeroor limit it with a query, for example One thing to decide is whether you also want As for preventing it from being pulled in the first place, I don't think there's an option for that. The autotagger always fills the field from MusicBrainz, so zero is the way to keep it out of your files. Hope this helps! |
Hi! The field you're looking for is
albumdisambig. In beets it holds the MusicBrainz release disambiguation, and when beets writes it to your files it uses theMusicBrainz Album Commenttag (MUSICBRAINZ_ALBUMCOMMENTin Vorbis/FLAC, aTXXX:MusicBrainz Album Commentframe in MP3). You can see the mapping in mediafile, wherealbumdisambigis defined with those storage styles. That's why you couldn't find it undercommentsor themb_fields.So zero is the right approach, you just need that field name:
The zero plugin hooks into every tag write, not only imports, so with
autoleft at its default (yes) the…