How to parse Alpha from Numeric in Masks [4810]

[BrickTop]

I am trying to do a lot of auto-organization and tagging and I came up on something that challenged me. I have a lot of multi-disc collections, and in most of them I have them orgainzed something like:

C:Music/Alternative/Alice in Chains/Dirt (Special Limited Edition)/CD1/[Track# Title]
C:Music/Alternative/Alice in Chains/Dirt (Special Limited Edition)/CD2/[Track# Title]

In other words, inside the Album folder, I have two sub-folders, CD1 and CD2.

So I wanted to have the Auto Tag from Filename feature take the number following the "CD" and have it fill in the Disc# field. In this case, "CD1" is considered a text field, so I needed to figure out how to get to that third character so I could use it as numeric data. I could not figure out from the help documentation or forum how to create the proper mask. I tried a bunch of things and then decided to try the following mask:

CD<Disc#:>\<Track#:2><Title>

And it worked! To be clear, I put the EXACT text that was in front of the numeric data right in front of the mask element. In this case, I put the characters "CD" in front of "<Disc#>".

I have some multi-disc folders that have Vol1, Vol2, Vol3 instead of CD1, CD2, CD3, so I suppose I'll have to create another mask that uses "Vol<Disc#>" instead of "CD<Disc#>", but at least I found a decent work-around.

If any of you techno-geeks out there know of a trick that would be able to use ANY alpha-numeric characters (instead of having to type "CD" and "Vol", it would be a great help. I tried a few common ones but did not stumble into the right one. (For example, I would like to be able to enter "NN" or "##" and it would automatically assume that ANY two characters would be parsed out leaving me with the desired leftover character.)

If anyone has any suggestions along these lines, I'd greatly appreciate it.

BrickTop

[Peke]

You are right, for now workaround works but <Disk#> can't be used in mask like this <Disc#:-1>\<Track#:2><Title> which will solve your problem.

I'm adding this to our To-Do, thx for noting this out.