Tagger scripts that are [X] Ticked are automatically acted on … but exactly when?
If an Album automatically goes to the Album side because it’s already got an MBID and Ignore MBIDs when loading is disabled:
Does the Tagger Script get run the moment the tracks go to the right or does it get run -AFTER- the [loading album information] happens?
I’m trying to work out a way to intercept existing tags if they’re set to a certain value before Picard would apply any changes it gets from the MBDB or other Plugin Fetched data.
This example will set %genresort% to with the value of %genre% if does not already contain a value.
I want to move whatever is currently in the Genre tag to another tag if it’s not been done already. So I can let Picard have control of the Genre tag contents and I’ll move my custom stuff to another tag.
If I want to make sure it’s applied to everything, do I need to set Picard to ignore existing MBIDs (so that everything loaded stays to the Cluster side and manually apply the script myself or can I let it do it automatically and catch those that already have an MBID, grabbing the value from it before it gets updated?