AdminDan Gravell
(Founder and programmer, bliss)
My feedback
502 results found
-
1 vote
An error occurred while saving the comment An error occurred while saving the comment This is a timely request as I'm currently looking into the way we communicate upcoming changes (although outside the album page).
The challenge is balancing information and *too much* information. The obvious solution is some form of progressive disclosure (a "more detail" button") but this and the expanded panel need to be designed in.
I think broadly you're right though, it's too confusing and not easy enough to see what will be done. Although, generally speaking, if it's an album level change, all files in an album will have (in this case) the artist tag (and/or album artist) changed.
-
1 vote
An error occurred while saving the comment You should be able to click "Edit" underneath the cover art, or "Change cover art" on the albums list, and change the art there.
This will give alternatives and allow you to upload an image.
So when you say "it would not accept my phots" this sounds like a bug - please send a debug archive "Help" > "Download debug archive" to support@blisshq.com
-
1 vote
-
2 votes
-
4 votes
An error occurred while saving the comment I think this gets a new lease of life with "linked releases".
An extra option could be added to put an album into "synchronised" mode - whereupon the data contributed from all linked releases overwrites the existing metadata.
This would've been useful recently when I imported one disc from a multidisc classical release which was incorrectly identified, and the artwork automatically filled in incorrectly. The release title was also badly formed, coming initially from CDDB. The correct release was in the linked releases list.
It would've been convenient to link to this one release and then also synchronise the data in one step.
An error occurred while saving the comment I've had this in mind for a while. What I thought was that markers could appear next to existing metadata saying some online database (probably MB) has different data, with an option to change.
This data would have to be run through the 'pipeline' to make sure it's valid for your current rule settings. For instance, if MB has a certain genre for an album, then bliss should convert that to something you are allowing (if that rule is enabled).
-
3 votes
An error occurred while saving the comment I updated the title to be more specific. At the moment it's assumed all tracks are in the same album, and there are fewer than 100.
Also see http://ideas.blisshq.com/forums/21939/suggestions/1871581 which relates to "odd tracks".
-
1 vote
An error occurred while saving the comment This is similar to other requests to have different data per track. Note this might cause issues in players, because if an album is shown, what date should be shown for it?
There are fields for storing the dates of individual recordings, which in principle could be used, but it depends what music player you are using as to the tags it will support.
-
3 votes
An error occurred while saving the comment Natürlich!
-
12 votes
An error occurred while saving the comment Sorry - what do you mean by "route" folders?
An error occurred while saving the comment As per some other ideas here, I often come up against the need to have different rulesets, although sometimes for different reasons, e.g. different rules for compilations
It's been a long term vision to have a way of "selecting" music to be managed in different ways. Here you might have a selector "album.tracks.size==1 || track.album.isEmpty" (or something) and then any release that matches that gets organised in a different way. Does that make sense?
Once you do that, it becomes a case of implementing the data points which mean you could differentiate your music. It sounds like it's just odd tracks, so in my example above that's: files with an album with only one track OR files without an album tag. I think that would generally pick out what you wanted.
Also see:
An error occurred while saving the comment This is a really nice idea. The main question in my mind is: what if one library is a child of another? E.g. say your libraries are C:\music and C:\music\compilations. Should the most specific rules win?
-
3 votes
An error occurred while saving the comment I think you can run two separate instances by customising a few things:
The port number: https://www.blisshq.com/support/faq/general/what-port-bliss-run-changed.html
The .bliss folder: https://www.blisshq.com/music-library-management-blog/2016/01/19/changing-bliss-settings-location/
An error occurred while saving the comment Having two instances might work if you were strict about the settings, although liable to confusion if both instances are looking at the same files and trying to do different things to them.
This sounds a bit like rulesets - https://www.blisshq.com/music-library-management-blog/2017/08/01/ruleset-selecta/
-
1 vote
An error occurred while saving the comment Yes, I can see it's broken right now - it's not just the thumbnails either.
I think really a print-friendly output should not include the headers nor the filters.
Some more about it here: https://superuser.com/questions/846082/how-to-get-wysiwyp-print-what-you-see-in-a-web-browser
-
1 vote
An error occurred while saving the comment Sorry, I missed this one!
What would be good is if the cover art filename allowed absolute paths to be specified, with tokens.
So "cover" means store a file called "cover.[whatever]" in the album folders (this is what happens now).
However, "/covers/<album name>" stores them in the "covers" folder off the root of the library, with the album name as the filename (the same tokens as in the file organisation rule should be used).
-
1 vote
An error occurred while saving the comment This is going to have an overhaul in the coming weeks, although the initial target is not to use a native browser as such, just make the current browser easier to use.
We *could* use a native browser, _if_ bliss was running on the same computer that it was being accessed from. This is a very common use case, so it's probably worth doing.
-
3 votes
An error occurred while saving the comment Typically this would mean a conversion from A or B to DISCNUMBER 1, C and D to 2 etc. However there's also autocoupled releases, where A and D are DISCNUMBER 1, C and B are 2. Luckily that is recorded in our metadata so this is definitely a possibility.
-
1 vote
-
2 votes
An error occurred while saving the comment Are these individual songs, not part of a release, or are they singles with B sides etc?
Also see:
- http://ideas.blisshq.com/forums/21939-bliss/suggestions/1871581-handle-folders-containing-singles
- http://ideas.blisshq.com/forums/21939-bliss/suggestions/3285112-allow-for-multiple-sets-of-rules-depending-on-sing -
1 vote
An error occurred while saving the comment Could you give some examples of album and artist names this leads to? I assume you're just talking about album and artist?
This sounds like http://ideas.blisshq.com/forums/21939-bliss/suggestions/31738582-derived-tags , would you agree?
-
4 votes
An error occurred while saving the comment Agree - if an album is named incorrectly and an album is "split" this will mean duplication detection will not work across that album - the album name needs to be fixed first.
-
21 votes
An error occurred while saving the comment Yeah - I was actually wondering if simply varying the case of the token would be elegant:
<TRACK NAME>
<track name>
<Track name>
<Track Name>Unfortunately it's difficult to communicate all capitalisation possibilities in that way. But simply "parameterising" the token could work:
<track name:uppercase>
<track name:lowercase>
<track name:sentencecase>
<track name:titlecase>An error occurred while saving the comment I'll merge this with the more general "Control over the case of a file/folder name" - this way upper, lower, title or whatever case could be chosen.
-
1 vote
An error occurred while saving the comment Yeah, I can understand. Personally I would suggest just performing a copy to a consistent name. How you'd do this depends on your OS...
An error occurred while saving the comment Yeah - you can't. _All_ of the filenames are used. I can see the use here (I think) - you want to just work with what you have. But wouldn't you also rather change all artwork to a common name, if you could?
Yes - I think some level of consistency is also important.
A similar UI could conceivably be used to communicate what _has_ been done.