Closed regorxxx closed 1 year ago
I'm fairly certain this was by design (and is why the two fields are specifically named "file name" and "directory"). Although off the top of my head right now I can't think of a good user-facing reason to actually enforce it.
If you're using "Custom directory" for the directory then I don't think there's any reason why you'd specifically need this but in other cases it provides more flexibility (maybe you want it next to the track but in a lyrics
subdirectory, as in your example, although you could already achieve that with the formatted custom directory so ¯\(ツ)/¯).
In either case that's a bug (display or functionality). Lyrics 3 allows to do that btw.
Now about why to allow that... note only the custom directory option allows to create folder
But what about saving lyrics using the other 2 options? You can not create subfolders, since the track TF doesn't allow it
So that was the original reason to support it in Lyrics 3. To create nested levels in the other 2 options.
I understand you can already mimic the other 2 behaviors with the custom format directory, but it requires more TF work. In any case, either the displayed result should be fixed or folders allowed to not confuse final users.
File name format doesn't accept folder levels, although the displayed example works fine (image 1). Backslashes are converted to '-'![image](https://user-images.githubusercontent.com/83307074/196009716-c155e752-72dc-4ebc-a1f2-3648f699f0cc.png)
So the subfolder must always be put at the directory TF.![image](https://user-images.githubusercontent.com/83307074/196009708-a2fcb0b2-8e52-424c-83a7-e25476a8053e.png)
Steps to reproduce
Expected behavior
File name should also create subfolders.
Versions