I suppose my component has some other unexpected benefits.
It sure has :-)
But thats only by design and because
There are no plans to make the Renamer component more user-friendly.
:-)
The attached Screenshot shows a simple problem:
The folder is renamed and foo_renamer cannot access further files in this folder now.
The Renaming-Error is "Object not found".
(No album artists are set in the files.)
pattern used (WIP): $puts(D,[$cut($if3(%DISCOGS_RELEASED_RAW%,%DISCOGS_RELEASED%,%DISCOGS_MASTER_RELEASE_YEAR%),4)]) $if($get(D),,$puts(D,[$trim($cut(%DATE%,4))])) $puts(AL,[$trim($cut($swapprefix(%album%,The,Die,A,Das),120))]) $puts(AA,[$trim($cut($swapprefix(%album artist%,The,Die),120))])$if2($get(AA),)$if2(' - '$get(AL),)$if($get(D),$if($strcmp($get(D),' '),,' ('$get(D)')'),) OK\%filename%
I understood why the error pops up, so there is not help needed, just wanted to add some prove for improvement :-D
EDIT:
Also, the fine component does not throw an error, if the new renamed folder (column "New Name") already exists.
The component tells that everything worked good, but f2k indicates then, that the path is wrong. (it shows a ? in the lenght column and all tags are gone, because the new path in the media-library are wrong now. I attached a new screenshot.)
This happens mostly, if the folder contains subfolders like CD1, CD2, etc.
Thanks again for your help and your piece of software! Very useful.