The screenshot shows the tag-field GENRE holding a list of unique GENRE or STYLE names, formatted into a multi-value tag-field.
I don't know all the options, which the script developer 'pone' has already built into the user adaptable configuration part of his websource script.
Assuming there maybe is no configuration option to split GENRE and STYLE names into two separate tag-fields ...
(I can not believe it actually),
... you may try out the following method to apply as a final cleanup procedure.
-
Given is a 'bad' list of genre and style names mixed together.
For example: 'TEST\\Techno\\IDM\\Ambient\\Electronic\\Blues\\TEST' -
Create a 'good' checklist of genre names.
For example: 'ElectronicRockBlues' -
Create a 'good' checklist of style names.
For example: 'TechnoIDMAmbient' -
Check each name from the bad list, whether it matches with a name in the good lists.
If there is a match, then put this name into the new list for genre names, ...
respectively put this name into the new list for style names. -
At end of the comparing procedure remove the helper lists.
-
The result is a set of two new lists, one list with genre names, and one list with the style names.
The lists /will be/can be/must not/ converted into multi-value tag-fields GENRE_NEW and STYLE_NEW.
Then decide what to do next.
I have attached a Mp3tag action script for testing ... adapt it to your needs ...
Test_2014_20140515.Clean.Genre.Style.mta (2.76 KB)
See also ...
Feld Genre mit zu vielen Wörtern...
DD.20140515.2205.CEST
Test_2014_20140515.Clean.Genre.Style.mta (2.76 KB)