Hal
My feedback
3 results found
-
2 votes
An error occurred while saving the comment An error occurred while saving the comment Hal
commented
In fact, I think I have to answer "no" to that question.
That would add an enormous manual job of selecting those folders/files manually after reading the list in the UI. It would not really add much value if it worked that way.
Hal
shared this idea
·
-
89 votesHal
supported this idea
·
-
11 votesHal
supported this idea
·
An error occurred while saving the comment Hal
commented
One thing that intuitively was missing for me when trying Bliss for the first time was a way of differentiating between singles and albums when setting up the rules.
I mean, assuming that I myself manually have split my collection into 2 separate main folders, 1 main folder containing singles in the root of the folder + custom collections of mp3s in their own subfolders, and 1 main folder containing complete albums: I would want different ruleset profiles for those two folders. For the albums the files should have album/artist folder structure and so on.
But for the singles I would want the files to have all relevant info in the filename and have no folder structure but instead be thrown alltogether in the root (with a tick box option if you want that they should just stay put within the subfolder they already were living in)
By "singles" I mean a single track that may as well be part of an album, I do not mean a dedicated single that you necessarily can buy in the store.
Correct, I want Bliss to migrate the files and folders it does not identify or cannot make compliant to a directory outside of the directory that Bliss manages.
This way I can work on these confirmed "rogue items" by other means.