Mike Lerch
My feedback
5 results found
-
12 votes
An error occurred while saving the comment Mike Lerch
supported this idea
·
-
4 votesMike Lerch
supported this idea
·
-
3 votes
An error occurred while saving the comment Mike Lerch
commented
While I would love it to be in the same UI, two separate instances would totally work in my implementation of this use case... I am using vortex box, and the default folders are /storage/music/Flac and /storage/music/mp3, so never the twain shall meet.
That said, the ruleset idea would also be a pretty elegant solution.
Mike Lerch
supported this idea
·
-
153 votes
An error occurred while saving the comment Mike Lerch
commented
I like this idea but have a slightly different spin. I already have the ability to have a lossless library mirrored to lossy through vortexbox, but it is a little monolithic so it would be neat to have other options (e.g. to have a fixed 320k mp3 mirror as well as a 128k VBR mirror). I particularly like the suggestion here that Bliss would take care of those cases where the file format was the same in the source and Target libraries, e.g. when I have bought mp3s from Amazon and that is the highest quality I have. I had to change the Vortexbox scripts to accommodate this.
More importantly, what I would really like from Bliss is the ability to apply different sets of rules to different libraries, even if Bliss didn't create the libraries itself. My in-car infotainment system is very picky about its tag formats, and I have to do a lot of manual stuff to make an MP3 library that is really compatible with it as opposed to the mp3s that will work with other players. I'd LOVE it if Bliss could apply different rulesets to different libraries as well as automatically maintain multiple mirrored libraries, but do see them as distinct features.
Mike Lerch
supported this idea
·
-
10 votes
An error occurred while saving the comment Mike Lerch
commented
I too would appreciate this feature, and have a preference to be able to specify the ISO date format. For releases where Bliss can't find the info and where I didn't know it I would just use January first of a given year.
That said, will different players interpret the values in this field differently? E.g. if some users wish to format as YYYY and others format as DD/MM/YYYY, how will different software interpret those very different strings?
Mike Lerch
supported this idea
·
I love this idea and wanted to add my two cents. Like some other folks, I have a collection of lossless files that I used to generate one or more collections of lossy files. While maybe not everyone would want to follow this folder scheme, I have no problem with having completely separate route folders for those collections, and would like to have different rules for them wholesale, specifically around the ID3 tag type and album cover size.
with that said, I very much like the idea of having the most specific rule win, like within my lost this folder, having a folder of compilations or singles or classical music or what have you, and applying separate rules within the broader root folder. This certainly would provide the most flexible configuration.
Of course, the ultimate would be if Bliss could *figure that out* for me. In other words, my folders are currently arranged as /storage/music/Flac/{artist}...if I had separate naming rules for classical music, it'd be stunning if it found the stuff in my ../Mozart folder and moved it to ../classical/Mozart or whatever.
for me though, that would merely be a nice to have rather than a have to have. Just being able to apply separate rules for separate route folders would bring me 95% of the way there.