I’ve updated the execution priorities of the performer_tag_replace, combine_performer_tags and format_performer_tags plugins, so that performer_tag_replace is executed before the other two. I’ve submitted the update to the official Picard plugins site, but until the request has been processed you can download all three revised plugins from my repo on GitHub.
3 Likes
Thank you for everything!!!
2 Likes
Hi Bob!
Sorry to bother you ahain, but I have a couple of questions,
do I need to install the plugins in a specific order?
will it work with only Combine Performer Tag and Performer Tag Replace, or do I need to have the three installed?
Do I need to change something in the Scripting section?
I have the three plugins installed, “apply replacements to performers as well as instruments & vocals” selected in Performer Tag Replacement , and this in a script (for Combine Performer Tag):
$noop( Set as a multi-value tag. )
$setmulti(personnel,%_performers%)
$unset(performer:*)
And I’m still getting “drums (drum set)” instead of “drums” when processing a release,
Thanks!
I can reproduce the problem here. I’ll take a look in the next few days when I have a chance, and let you know what I find.
1 Like
I’m pretty sure that I have resolved the issues now. You will need to download and install the latest version (v0.03) of the Performer Tag Replace plugin from my GitHub repository.
For the curious, the problem was that I was updating the tags themselves, but not the underlying metadata retrieved from MusicBrainz (and it was this metadata that was being used by the Combine Performer Tag plugin).
3 Likes
