Ability vary the depth the file path rule investigates
Abou 25% or 1000 albums in my library are marked as uncompliant on file path. The vast majority of these albums have one or two tracks that are uncompliant because the file name does not exactly match the tags and in most cases it is because the tag contains a character such as "\" which is invalid in a file name. This is not an issue to me and I would rather leave the tag alone rather than change it so that the file name is valid. I would like to able to set the file path rule so that it only investigates down to the Album level and does not check the file names of each track.
tippo
shared this idea
-
"The vast majority of these albums have one or two tracks that are uncompliant because the file name does not exactly match the tags and in most cases it is because the tag contains a character such as "\" which is invalid in a file name"
I wonder if we could do something there. Consider a track title:
How Soon Is Now?
Question marks are disallowed in file paths like slashes. The disallowed characters are:
/, \, ?, :, *, >, <, |, "
Currently the disallowed chars are simply removed from the expected filename, meaning bliss would expect:
How Soon Is Now.mp3
We could either accept no character, or maybe any one character, e.g.
How Soon Is Now_.mp3
Is an approach I've seen other music tools take.
Would this fix your case? I have a concern that while the depth approach would certainly work for you, it would work *too* much, leaving your track names not regulated properly.
