Genre and Grouping


It’s enabled. Poor me!


It’s like it’s not seeing the genre tag, which seems to be confirmed looking at your variables list screen shot above. On my system, I have the Use folksonomy tags as genre option enabled (see below). I wonder if that’s what’s making the difference?


Just tried and it didn’t work! I think I’m stuck! I will do it manually! Thx for you help


If I recall correctly (I cannot check currently), there is an option to use other’s people tags for the folksonomy. By default, it might only use your own tags. Have you tagged things on Musicbrainz? You might want to look for the option to use other people’s tags.


There ‘Use only my tag’ but I don’t have it checked.


Hello rd, While not “on topic” I have related question concerning file naming and scripting in the Options columns. I have 5 tagger scripts saved. To use one of these scripts do I just check the appropriate box and do nothing to the file naming box? To date, I have been deleting the script in the file naming box, then going back to scripting to copy the script I need and then pasting it into the file naming box.

Is this the way it is supposed to be used? Or am I just supposed to check the script box I wish to use without doing anything with the File Naming area? In the past, if I don’t replace the script in the File Naming tab, funky things happen.

I appreciate your help.


One of the things that I do here to provide different naming scripts for different situations (e.g.: Pop / Rock versus Classical) is to combine the various scripts in the naming script, and wrap each of them in an $if() function such as:

$if($eq(%_nametype%,pop),pop naming script goes here,)


$if($eq(%_nametype%,classical),classical naming script goes here,)

Then I just use a separate script to set the _nametype variable as




In most cases, I can set the naming type automatically based on some logic (e.g.:


But I haven’t yet found the appropriate combination of logical tests to automatically determine when to use the classical naming script, thus the separate setting script.

An alternative, which is closer to the way you suggested is to keep your naming script very simple as:

$if(%_outputpath%,,$set(_outputpath,%albumartist% - %album%)

and then have each of your five scripts set the values of _outputpath and _outputname accordingly. That way you could simply select the script you want to do the processing and avoid any copy ‘n’ pasting or editing of the scripts. Note that I included setting some very basic default values for _outputpath and _outputname just in case none of the processing scripts are selected and the values are blank.

In fact, I really like your suggestion and think I may modify my setup here to keep the different naming style scripts separate. It will make it a bit cleaner when editing one of the styles, and will avoid having a huge master script. Thanks for that.

The beauty is that there are a few different ways of achieving what you want, so I suggest that you pick one that you’re comfortable using and go with it.

That’s caught me on occasion too, but it’s usually because I haven’t taken into account the way the processing occurs within Picard. @dns_server explains the order in:

Things generally seem to work as expected if I do a refresh on the metadata from MusicBrainz (in the right-hand pane) after making any changes to scripts (including selecting / deselecting) and before performing the renaming.


I appreciate your info! Now I have a few things to chew on.

Llama lover