John Chester
My feedback
2 results found
-
6 votesJohn Chester
supported this idea
·
An error occurred while saving the comment An error occurred while saving the comment John Chester
commented
I just came up with a method to help myself as a "work-around" to this problem. I can manually tell Bliss that my root music folder is one of my self-named genre's at the top level and then use the automatic organization to help me organize by {artist-name} / {album} / {tracknum - title-of-song} for one genre at a time for me. This isn't perfect but a fairly good work-around for me now.
It means that I must go into each of my genre's (one at a time) and use Bliss to organize by artist / album / tracks, etc. This does work albeit not as efficient for me as having Bliss automate this process in a single step.
A new problem that I have just discovered however, is when Bliss "moves" my albums into the target organization (within my self-named genre as a root level), Bliss leaves behind "scans" and "Artwork" type folders. It would be very nice it Bliss moved "all folders" underneath it's directed automatic file reorganization, rather than leaving behind "orphan" folders like "scanned" or "Artwork". It should (at least with an option), move those sub-folders into the new target directory structure as well.
If it did this, I would not have go behind Bliss and "clean-up" after I've run it to reorganize my albums within a particular genre. Right now if I want to save those sub-folders (and I definitely do), I have to manually move them into the new album structure and then go back and delete the empty original album directory structure.
I would like Bliss to have an option to "move all sub-folders" within an album's file organization. This would be equivalent to a "wildcard" character at the end of the specification forcing Bliss to move everything it finds underneath that token to the new structure. This would be enormously helpful to me. I couldn't find this last issue / problem as a suggestion in the forum. If it's already present - please let me know and I'll vote for it. It appears to be yet an extension of my original suggestion.
Thanks - John
An error occurred while saving the comment John Chester
commented
Still awaiting for this fix. My music library is now almost entirely non-compliant because of this.
Bliss has become a terrific tool for finding and updating Art. It's usefulness for other organizations like the personal directory structure would be extremely helpful to me. See my 1st post from January 4, 2013. I use my own genre description - because frankly the music industry can't seattle on standard definitions and have far too many genre's - they have an absolute mess of genres. My music would be "scattered" all over hundreds of genre's if I let Bliss autotag with a "genre" in front of it and I'd never to be to use or find any of my music.I'm re-requesting both of my comments for the * wildcard token below the root level. It would solve my music library problem once and for all.
Thanks - John
An error occurred while saving the comment John Chester
commented
It would be great if the wildcard would work as token underneath the already specified Bliss library location - which Bliss already knows about.
A single token would work for me, as I only use a single level type "genre" - but I can see others
possibly needing more than one token if they "nest" a structure before one of the standard hierarchy sets (artist / album / tracknum-songtitle).....So I would only need something like this:
*/<artist>/<album>/...
Each * wildcard token gets interpreted as the consecutively next current folder underneath the Bliss library location.
Others might need more such as using multiple wildcards, For example:
*/*/<artist>/<album>/...
Thanks R / - John
An error occurred while saving the comment John Chester
commented
Very strongly support this suggestion. I have a slightly different but similar issue that would be fixed with the wildcard suggestion.
I use something like "My Music Library / {my-personal-genre-description} / artist / album / tracknum-songtitle. It would be tremendously beneficial for me to not have Bliss be "non-compliant" and allow me to use the Organize File ruleset with a wildcard for "current-directory" underneath my library location of "My Music Library". Otherwise the automatic adjustments force my entire music collection (very large) to be directly underneath my library - which I certainly don't desire.
Great suggestion and would help me and probably many others that bother to categorize their music library.
Strongly support this suggestion.
Thanks VR / - John -
2 votesJohn Chester
supported this idea
·
An error occurred while saving the comment John Chester
commented
Still in support of this suggestion as well. It would be greatly helpful to allow navigation and at least manually fixes by the grouping of noncompliance. Right now manually fixing of noncompliance for me is not an easy task.
Summary groups and navigation would help greatly.
That sounds like a good solution to me. Most file organizations with a single directory underneath are likely to be "art" or possibly a "playlist." If you didn't move the music and waited for the * wildcard implementation for that (assuming that eventually happens) that would be a good compromise for me. This would pull the scans and artwork and would work for me and not leave behind orphan "clones" of the album after file organizations. :)