My plugins

MusicBrainz Picard
1

I created few plugins I use daily for a long time so I thought to publish them on GitHub:

Plugin File What it does
Release Relations Tagger relationships.py Maps MB release-level relationships (artist, label, place, area, URL) to configurable tag fields — each type can be enabled, renamed and prefixed; multiple values join with a configurable separator. Place/area rels are fetched via a supplementary API call (Picard’s default lookup omits them). Configured in Options → Plugins.
Bandcamp Info bandcamp_info.py Fetches the release’s Bandcamp tags and about-description from the linked Bandcamp page into configurable tag names (album-level, cached).
Discogs Info discogs_info.py Fetches and merges Discogs genres + styles into a discogs_genre tag (album-level, cached) and stores the Discogs release/master IDs.
Preserve Tags preserve_tags.py Protects tags listed in a per-file preserve_tags tag from being overwritten by MB tagging: values present on disk are restored, absent ones are kept absent. Presence is checked by reading the file via mutagen, so Picard-internal fields are never mistaken for real tags.
Compiler compiler.py Extracts the release’s compiler relationship from MB and writes it to a compiler tag (multiple compilers joined with ;).
timestamp timestamp.py Adds a $timestamp() tagger-script function returning the current date-time (YYYY-MM-DD HH:MM).
1 Like
2

Ok - so…

  1. Picard v2 and Picard v3 need different plugins - so you need to be clear about which version these support.

  2. Picard v2 only gives a UI for plugins in the single centrally maintained github repo. So if your plugins are v2 then if they are in a separate repo they won’t appear in the GUI and the user will have to manually download & install them. You may want to think about submitting them as a PR, though I suspect that the v2 plugin list is stabilised and PRs for new ones won’t be accepted.

  3. I believe that Picard v3 has a more federated approach but I haven’t used it so cannot speak from experience. But I believe that the intent is to allow users to add plugins from separate repos to the index. I don’t know how this will work, but you might want to look into it.

  4. The Picard plugins web site shows that v2 has 74 existing plugins, but v3 has only 28 of these ported. I am not sure what the plans are for the other 46.

1 Like
3

Those are v2 scripts, intentionally kept in single repo as I created them for my own use cases and not sure how valuable those are for other people. I can always properly handle them in the future if there is interest.