The thing that helped me get past the How The Heck Does This Work?! curve …
Put letters, numbers, whatever, in between your stuff while you’re editing so you can see what is doing exactly what in your scripting.
… and it goes from top to bottom, everything is done in order, and the output being generated is a continuous line that you’ll see in the example text as you build it.
Put “X:\musik\sorted” in the Destination Directory entry.
Your scripting will be generating the rest of it and in the example at the bottom you’ll see the combined result.
Starting with something like this:
$noop(★ Artist with first letter of first name ★)
Willl show your example as:
(however the Windows version shows the example with drive letters and back slashes. I’m not using Windows, but the idea is the same)
/musik/sorted/B/The B-52’s … etc.
If you type some characters in up there after the / (e.g.: abc123)
The example will be:
One part at a time, $if, $set, $eq …%label% %year% %artist%
Just type that stuff in and watch what the example does. Go from there.
Some of the tags you will NOT show anything on the example because they’re not hard coded into the routine that is generating the example, like %label%, but the basic stuff is.
In my example screen shot, you see where I typed aaaaaa in and it’s showing right before the track number. Thats how you can see what part of the script is affecting where in the output.
(and I also added extra stuff to the hard coded example stuff, so if you entered exactly what I have in the script box, you would NOT see the same example, but it would create the intended output on disk.
An earlier version of that script I’ve got going on there is in that thread referenced in the above post. As soon as I get one more thing unscrambled, I’m going to post the revised one. I posted a thread for the “one more thing” , too… (I want to see the track time in the filename with a ‘colon’, not underscore. That is, a unicode filesystem safe character that happens to look very close to a colon.)