AdminDan Gravell
(Founder and programmer, bliss)
My feedback
-
150 votes
TL;DR: We’ve just pushed the first tranche of code to implement ignoring-compliance. This is preliminary backend work – there’s no button yet to click so this “just works”. That’s the next step.
Working with rulesets in mind (https://www.blisshq.com/music-library-management-blog/2017/08/01/ruleset-selecta/) bliss is now capable of finding extra settings files in its settings directory with the extension .settings.
If an entry in the file of the form:
albumSelector=_.name.equals(“Scott 4”)
This means bliss will attempt to match the album to the selector on the right-hand side of the equals. If it matches, the rules defined in this settings file are used.
This is hopefully pretty powerful functionality – it means we can soon setup different rules for different types of albums (not just the ignoring-compliance use case, which I always saw as a special case of rulesets).
There’s no UI for this yet – it only works on the basis of files.…
An error occurred while saving the comment An error occurred while saving the comment We already have that for ignoring files and folders altogether: https://www.blisshq.com/music-library-management-blog/2011/08/16/new-release-20110809/
The trouble for adding _another_ file for this is that this is something we'll have to continue to support in the future. And the edge cases - does the file get moved when bliss's file org feature moves files? Lots of stuff like this will crop up.
An error occurred while saving the comment Yes - although this idea would merely ignore that.
For dates, three dates spring to mind:
- Recording date
- Original release date (the original album/single whatever release date)
- Release date (e.g. for remasters)But that should be in another idea thread.
An error occurred while saving the comment This would also be useful for having your own fields calculated from other data - https://www.blisshq.com/music-library-management-blog/2017/10/03/derived-tags/
An error occurred while saving the comment "Unknown" doesn't mean the album is unknown, it means the album's _compliance_ is unknown, i.e. whether it obeys the rules or not.
Normally this is indicative of another problem - send a debug archive to us as per https://www.blisshq.com/support/reporting-problems.html Thanks!
An error occurred while saving the comment This would also be useful for that: https://www.blisshq.com/music-library-management-blog/2017/10/03/derived-tags/
An error occurred while saving the comment Great ideas. The main progress has been identifying a way of fixing these problems, although work has not begun on them yet.
Ignoring certain compliance for certain albums can be seen as a special case of https://www.blisshq.com/music-library-management-blog/2017/08/01/ruleset-selecta/ - i.e. the "selector" selects this album in particular, and the ruleset assigned to that selector is the same as otherwise, except with the "ignored" rule removed.
An error occurred while saving the comment Are you saying you want the subtitles in the album name, or just that bliss is matching to the incorrect release?
One thing that might be useful is the ability to choose a subset of the Linked Releases to use.
An error occurred while saving the comment Yes, good example.
An error occurred while saving the comment Just wanted to make a note to myself...
Rather than specific "ignore" functionality this should work by implementing "selectors". Create a new selector for this specific album, with a slightly-changed ruleset.
This would be preferable, because selectors are a more powerful, less specific implementation and it should mean less code overall.
An error occurred while saving the comment Yes, although the way I look at it is having a "selector" to which rules can be applied, e.g.
select all albums where genre = "christmas" => [specific rules]
I just have a natural aversion to conditional statements :D
An error occurred while saving the comment Nice idea! Might need to add that as a separate idea, though... I'll close this once "ignore" is implemented.
AdminDan Gravell
(Founder and programmer, bliss)
shared this idea
·
-
59 votes
An error occurred while saving the comment @Pete Yes, I don't think we can do that right now - it's the wipe-then-fallback-to-original that we are missing.
What if it worked from the point of view of genres first - you could think of it as a table of genres, and then if you update that genre, all albums with that genre would be updated? That way you can change to the consolidated list of genres. It assumes that all albums for a genre want to have their genre changed in the same way.
An error occurred while saving the comment I don't understand why the custom genre column would be needed?
An error occurred while saving the comment Thanks. Internal to bliss there is a genre tree. It's here -> http://www.blisshq.com/app/genre-tree . When bliss encounters a genre not in the allowed list, it looks in the genre tree and looks up, parent by parent, until it encounters an allowed genre and suggests that.
Currently this tree is fixed, static.
For your case, this would imply Jazz parenting "Stride Piano" etc. It would also suggest a way of editing the tree itself as part of the configuration... or maybe simple "parent of" relationships between genres can be stored and shared by bliss users to make the genre tree both more accurate and more complete.
-
1 vote
An error occurred while saving the comment Thanks Bob. What sort of scenario are we talking about here - where there are no track names?
Take a look at https://ideas.blisshq.com/forums/21939-bliss/suggestions/2458603-use-the-folder-and-file-name-to-help-identify-song
And in a similar area: https://ideas.blisshq.com/forums/21939-bliss/suggestions/2714313-auto-suggest-album-art-based-on-file-name-or-tags
-
1 vote
An error occurred while saving the comment I initially thought I would have to merge this idea elsewhere because people have asked me about it so much by email etc... but it turns out it isn't on the ideas forum yet!
Here's one which is close, but I want to keep the ideas separate because they have different intents: https://ideas.blisshq.com/forums/21939-bliss/suggestions/9161260-move-music-files-between-libraries
Also see https://ideas.blisshq.com/forums/21939-bliss/suggestions/4191110--big-one-changing-bliss-to-a-task-queue-work-flow which has some overlap.
This idea would qualify under a broad idea I've had called "post actions" which means: once an album matches a given state (say: it is compliant) then perform some action.
Ideally, to improve maintenance, these actions would be derived from the potential rules encoded in bliss. I've also thought about making these actions available on a manual invocation basis for each album (e.g. just an action on the album page to change the capitalisation of tracks, or whatever), but that's another subject!
-
27 votes
An error occurred while saving the comment @Markus do you mean if you have nested directories? E.g.
All Things Must Pass/
- Disc 1/
- Track 1.flac
- Track 2.flac
- Disc 2/
- Track 1.flac
- Track 2.flac
- cover.jpgYou're referring to "cover.jpg"?
An error occurred while saving the comment The URL that you would need to paste would have to be the direct one to the image. You can find it by clicking an image on the album overview. For example: http://localhost:3220/thumbnail/LCD+Soundsystem/This+Is+Happening/?1330939691913
An error occurred while saving the comment Yeah, good point. This is something I have wondered about before, briefly. It would be very useful for those multi disc albums as you say.
-
1 vote
An error occurred while saving the comment This seems a common request for DJs inparticular.
Did you see:
- https://ideas.blisshq.com/forums/21939-bliss/suggestions/1871581-handle-folders-containing-singles
- https://ideas.blisshq.com/forums/21939-bliss/suggestions/42192883-mark-as-singlesDo they cover similar ground?
I assume you mean "singles" as an individual track rather than an actual single release (which often, although not always, contain other tracks). In that case, "album" is synonymous with "single" - what it really means is "release".
-
1 vote
An error occurred while saving the comment What appears to be happening here is some confusion around what is denoted the "album artist" for the album.
We choose the album artist based on:
- The ALBUM_ARTIST tag
- The ARTIST tag
- The COMPILATION tag
- The location of the files (which act as a grouping indicator - the file/folder names are not used)If "Various" is chosen at any point, this normally means the album was combined for some reason - is it a compilation, or are the files in the same folder?
-
1 vote
An error occurred while saving the comment Thanks - what do you mean by music "assignment"? Do you mean lookup so that Plex can find information about music?
-
1 vote
An error occurred while saving the comment Thanks for this.
This can already be done with the file organisation rule if the \ImportMusic folder is in the same root as the music folder.
If it's important that \ImportMusic is separate, then https://ideas.blisshq.com/forums/21939-bliss/suggestions/9161260-move-music-files-between-libraries would work, with the proviso that the "target" isn't being analysed.
Agree?
-
1 vote
An error occurred while saving the comment Could you use the ARTISTSORT field for this: https://ideas.blisshq.com/forums/21939-bliss/suggestions/2249593-for-file-organisation-create-a-new-album-artist-v ?
-
1 vote
An error occurred while saving the comment So are you suggesting interpreting release information from folder and file paths?
I guess you could come up with heuristics for this, but I'd be a bit wary about it.
It shouldn't really take _that_ long to just read these files, although I agree writing data can be slow. I'm not showing much empathy here, so maybe I misunderstand just how high a speed you require!
-
2 votes
An error occurred while saving the comment Thanks - so does this happen to all HTTP traffic to the NAS's IP?
An error occurred while saving the comment Hi - can you explain what you mean by "synology servers, configured with HTTPS access" - are you referring to a setting in DSM?
-
14 votes
An error occurred while saving the comment I think there are two cases of this:
- Handle tracks that are single tracks (*not* single releases) - these may or may not have album tags
- Handle individual tracks as part of an album, or more generally subsets of albums, better, so they are more likely to match to linked releases (right now the certainty is lower for subsets, especially individual tracks)I think these should be implemented separately, as two separate pieces of work.
An error occurred while saving the comment Ok. In theory that should work for a small number of singles - in the same way you can have one folder of multiple full albums. However, this wouldn't scale to 4000 tracks at the moment.
An error occurred while saving the comment Just want to add a clarification here (for anyone reading)...
When it is said bliss is "album" oriented, what is meant is that it is "release" oriented.
If you have complete single releases, they should work just as well as albums. For example, if you have the A side, B side and other tracks, and they are in their own folder together.
It's more "odd tracks" that are the problem, and what is meant by "Singles" in the title. But I can understand the motivation.
An error occurred while saving the comment Max, maybe see http://ideas.blisshq.com/forums/21939-bliss/suggestions/3758349-add-logic-to-conditionally-use-tags-in-filename also?
Do you have tags that dictate whether a given release is a single, compilation or album? There's such as thing as a COMPILATION tag but no well agreed "single" tag or similar. I ask because it may not always be possible to look the data up - it may be missing for more exotic releases.
An error occurred while saving the comment Yes, I suppose there's a few ways of cutting this particular cake. Different libraries with different rules is one. Specifying certain directories are ignored for the file org is another.
I kinda like your original idea though. Seems quite powerful.
-
11 votes
An error occurred while saving the comment Thanks @Christopher . Those are some good heuristics to add to the list.
An error occurred while saving the comment -
2 votes
An error occurred while saving the comment Ok - but just to confirm: any slowness on those sites shouldn't affect bliss, because although we source the same data, it's served from our own database and servers.
An error occurred while saving the comment Another alternative is to do this at the linked releases level - i.e. only link releases from MusicBrainz, Discogs etc.
An error occurred while saving the comment Why, is one database providing data you are not happy with?
-
2 votes
An error occurred while saving the comment Love this idea. I think there are some rules that can't be fixed by bliss - this is one of them, because upsampling in most cases would probably not be desirable.
-
1 vote
An error occurred while saving the comment This should only happen when one of the following conditions is true:
- The files are all in the same folder.
- The ALBUM ARTIST or ARTIST fields vary such that there's no one distinct artist present in at least 70% of the tracks.So try reviewing the current fields, and see if changing them helps...
-
1 vote
An error occurred while saving the comment The word "album" is used a lot in music library management. However, in reality, in most cases, "album" means "release" - https://www.blisshq.com/music-library-management-blog/2013/08/06/album-name-think-release-name/
A single should basically be organised like an album. The ALBUM NAME tag should be filled with the name of the lead track (in double A sides this might be two tracks). Here're a couple of examples from MusicBrainz:
https://musicbrainz.org/release/b5109c8b-9808-4e28-8e03-36d100b5d86e
https://musicbrainz.org/release/b6cc6503-2f64-4dd2-91e3-a27b9ab526feIn theory, then, singles should be able to be identified, _however_ because of the lower number of tracks in the release, achieving a satisfactory confidence in the software might be more difficult.
In terms of actually marking a release or group of tracks as a single, this is up to you to define a field name - there are no commonly used field names for this purpose (that I know of). In which software do you want to see the releases separated by release "type"?
-
1 vote
An error occurred while saving the comment The album artist _and_ the album name is a _sort_ of primary key.
I think this might happen if the files are in the same folder. Is that the case for you?
-
1 vote
An error occurred while saving the comment When you say "move a genre or sub genre of music in and out" you mean "in and out" of a top-level music folder, right?
Sounds like one for http://ideas.blisshq.com/forums/21939-bliss/suggestions/36753685-individual-rulesets-for-different-genres
Also see https://www.blisshq.com/music-library-management-blog/2017/08/01/ruleset-selecta/
I think it's important to show when the assessment of albums are ignoring an element of the ruleset, so here's the first stab at a panel that shows on such albums' pages.