I am observing I weird behaviour on action group which I cannot explain in any ways, so maybe someone from this forum has an explanation.
So, Action Group has 2 Actions, format tag field:
_FILENAME -> %DISCNUMBER%$num(%TRACK%,2) %TITLE%
_DIRECTORY -> %ALBUMARTIST%/%ALBUM%
Order in which they are in action group does not change behaviour, but this is what happens.
First path becomes (desired behaviour):
/Users/%username%/Testing/Compilations/Various Artists/24_7 Dub Pack (Special Edition)/01 Radio Hardcore Porn.mp3
All other file paths change to (weird behaviour): /Users/%username%/Testing/Compilations/Various Artists/Various Artists/24_7 Dub Pack (Special Edition)/02 Badgertism.mp3
Which is super weird, basically %ALBUMARTIST% is inserted twice?
Same happens, when I reverse order of those actions, at the same time both actions work correctly, if they are in separate action groups.
So it only works as desired, for some reason, for first file in specific folder.
What I am missing here?
I assume that you have "Various Artists" as ALBUMARTIST?
If you rename the _DIRECTORY
to
then you get Various Artists\24_7 Dub Pack (Special Edition)
The other "Various Artists" is not part of the current directory but of the parent directory.
I forgot to add, starting path for those files in example is:
/Users/%username%/Testing/Compilations/Various Artists - 24-7 Dub Pack (Special Edition)/01 - Alaguan - Radio Hardcore Porn.mp3
/Users/%username%/Testing/Compilations/Various Artists - 24-7 Dub Pack (Special Edition)/02 - Rob IYF & Al Storm - Badgertism.mp3
The other "Various Artists" is not part of the current directory but of the parent directory
There is no such parent directory, before action group runs.
And it does not explain, why it works, when I remove _FILENAME action from that group.
Then _DIRECTORY action works fine, for every file and does not spawn %ALBUMARTIST% twice.
Actually it is 70 files, 2 directories (albums) I am playing around with.
But same happens for both, first folder has 13 files, first one gets treated as you would expect, all 12 other 12 have behaviour as second file in my posted example.
Same happens to second directory (album), first file gets treated as expected all other 56 have behaviour as second file in my posted example. For second folder it is not Various Artists, but specific Artist which is same as Album Artist.
Increasing decreasing amount of sample albums or files does not change this behaviour.
Only thing that does, is removing _FILENAME action, but I definitely don't have %ALBUMARTIST% tagged into %DISCNUMBER%, %TRACK% or somewhere else, except correct field.
If you had 3 files in this folder, you would get "V.A" 3x.
If you want to keep an certain depth of folders, use an absolute path, e.g.
Format value for _DIRECTORY
Format string: F:\Testing/Compilations\%albumartist%\%album%
Unfortunately it defeats a purpose to have an action in a first place, and still it does not explain why it happens.
If you had 3 files in this folder, you would get "V.A" 3x.
Even having it behave recursively, would make sense, but it does not behave that way.
What I don't understand is why it works, when _FILENAME action is removed from group,
while at the same time, order of those 2 actions in group does not change result.
OK, fine...but _FILENAME action should not affect it's behaviour,
since that action does not have / hence it does not alter the _DIRECTORY in any way.
That is basically the part I fail to understand...
But what I do see, is that it is somehow still related according to my testing.
For testing purposes you could modify the _DIRECTORY action to set as format string: %_directory% - which should not change the folder.
So if the action for _FILENAME is the culprit, this should prove it.
If the action for _FILENAME is OK, test it the other way round: keep the filename and modify the folder.
For testing purposes you could modify the _DIRECTORY action to set as format string: %_directory% - which should not change the folder.
So if the action for _FILENAME is the culprit, this should prove it.
If the action for _FILENAME is OK, test it the other way round: keep the filename and modify the folder.
Actually wait a minute...will retest.
EDIT: Verified, indeed, in both occasions result is desired for all files.
Given from your example, it should work as you've expected it to work.
The current folder /Various Artists - 24-7 Dub Pack (Special Edition)/ should be renamed to /Various Artists/24_7 Dub Pack (Special Edition)/ and all the files within it.
Actually I found a way, when it works.
Basically, if I do this instead:
_FILENAME -> %DISCNUMBER%$num(%TRACK%,2) %TITLE%
_DIRECTORY -> ../%ALBUMARTIST%/%ALBUM%
It also limits the recursion so if I run action group 3 times, it does not spawn: /Various Artists/Various Artists/Various Artists/
But it moves everything one level up, as expected
Doing:
2. _DIRECTORY -> ./%ALBUMARTIST%/%ALBUM%
Has same result, as without ./
