The other way around?
Do you have fields where you want to keep (Album), (Digital Album), (EP), (LP), (Single)?
If not:
You could remove it from _ALL instead of ALBUM, _DIRECTORY and _FILENAME
@LyricsLover
The intended use is to keep this within an all-in-one action group.
If I add this action to the beginning it would be possible to make it work as you have suggested.
If I were to do this, I could reduce the number of lines from 15 to 5 (which is a pretty good improvement).
Is there a way to condense further?
@ohrenkino
Whilst the code worked to change square brackets to round, the action could not be adapted for use in other circumstances so, based on @ryerman's recommendation (like in the other thread mentioned) I have started a new thread for this question because the previous question was unclear and did not resolve the query. Now this is related to a different specific example.
Just to add the "Guess value" example:
Action: Guess value Source: $replace(%_directory% == %_filename% === %album%, '('Album')',, '('Digital Album')',, '('EP')',, '('LP')',, '('Single')',)
String: %_directory% == %_filename% === %album%
There is no guarantee that it actually works with this combination of fields as I still suspect that you have to run actions that manipulate the folder name in a different action group.
@ohrenkino
Thanks for providing an alternative solution. I tested it but it didn't pick up (ep) from any fields mentioned unless the case matched exactly as specified in the example given.
There does appear to be a limitation with this method whereby the directory name is not affected.
Interestingly (and frustratingly), when saving changes through mp3tag to the example you have given in the action manager it keeps changing the case of the words included to 'First Letter Of Each Word'.
Yes. You can tell they are allowed because they are hard-coded into the drop-down list of the "Replace with regular expression" action, unlike in the "Format value" action.
After further testing it looks like this is case sensitive too. I input the test in lower case, save the action and then it converts the code to Mixed Case...
Yes. We have discussed this before. And I bet that LP does not work either as I suspect that you run an action before that which sets the first letter to upper case and the others to lower. "Album", "Digital Album" and "Single" follow these rules.
So it should be a piece of cake to add the pairs for "Lp" and "Ep".
I assume that the $replace() in a "Format value" action behaves in the same way.
It appears that you are falling back on old bad habits: copying solutions without knowing the basics.
I'm not sure what your regular expressions match, but matches will be deleted!
You want them changed to UPPER case.
Thank you both for your replies. I am sorry that I have not got back to you sooner. Not had a chance to test your suggestions yet, but will be sure to try them out when I get an opportunity.
In the mean time, I am attaching all my actions (mainly for my benefit in case I lose them, but also in case anyone is interested/they are helpful). The one which most closely relates to what has been discussed before your two most recent suggestions is called All In One Conversion (Record Folder) Filename & Directory.mta.
They may be useful to others, so long as you know that my workflow involved keeping new artists/albums in a folder within A:\Music\Record for processing in Mp3tag (filename changes to # Trackname with correct capitals in all tags). Even if the folder structure is not correct, so long as the artist name is included when processing, it will correct this for you to A|\Music\Record\Artist\Album. Once completed, I run Finished Tagging (Move to Music).mta to move the new Artist\Album to A:\Music\Artist\Album. I then run 'Remove Empty Directories' (http://www.jonasjohn.de/red.htm) to clear the empty folders in A:\Music\Record using the following settings: