Just tried this - it works fine. It requires cookies to be enabled - could that be the problem?
One of the other problems is that bliss currently runs when it sees an album. So if it sees an album with "Disc 1" - is that a multidisc album or not? It might not have scanned the other album yet...
Unfortunately you can't. See https://www.blisshq.com/music-library-management-blog/2017/08/01/ruleset-selecta/ which is my favoured way of implementing this.
- Don't use the rule!
- Use discnumber in the pattern
- Use a conditional discnumber in the pattern, and remove discnumber from the albums with one piece of media: https://www.blisshq.com/music-library-management-blog/2013/07/30/more-uses-conditional-file-org/
I just wanted to add... The trouble with using disc number in this way is - how do you know if another set of files has disc number >= 2? Because if there is, the decision should include the disc folder, and not otherwise.
The more deterministic way of doing this is to look at disc max number which should indicate how many discs are in a given release. Then use your logic on that tag rather than discnumber.
Ah, ok, so when you have single disc albums with discnumber=1 then you want to be able to choose a different pattern.
If the discnumber is absent then it is already possible to do this:
... but that doesn't work where discnumber=1 and it's single disc.
Erm, which image is that?
Indeed - but automation can only happen, really, when there's some intelligence about allowing one file to remain.
Perhaps files ending with a number could be detected as the most-likely duplicate and have the fix by default - that way the Inbox and grouped album fixes could be clicked once.
This would be useful for sure! Thanks for posting.
Should they? Some people might want to find duplicates and delete the MP3 (for example). I think this should be setup with a heuristic.
This would also be useful for that: https://www.blisshq.com/music-library-management-blog/2017/10/03/derived-tags/
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.
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.
Yes, good example.
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.
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
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 ·
In the version just gone to beta, out next week, entire albums can be removed from bliss (and optionally the folders can be rescanned). The files are not deleted though, so I'll leave this open.
Deleting from bliss, and/or deleting the actual files from disk?
On the albums page you can use the compliance filters on the left to narrow down to just albums with duplicates. Does that help?
Obviously I'd prefer bliss to provide the controlled correction environment! Let me know how it doesn't...
What do you want to do with the resulting CSV?
Agree - it does point to having special ways of forming file names being a good idea.
For reordering artist names in the tags (which will then propogate through to file names) see https://www.blisshq.com/music-library-management-blog/2017/07/04/reordering-the-artist-name/
<raw:artist_sort> is now implemented! https://www.blisshq.com/music-library-management-blog/2016/11/15/release-20161108/
I'm of a mind to now close this - artist_sort or album_artist_sort can now be used, and is a simpler solution to the problem - the only requirement being you still need to store _sort tags!
Another way of approaching this would be to add artist sort name tags and use those, with a <raw> token (not implemented yet, but would be a good general addition).
Thanks. Is this for the file organisation feature?
Thanks - which list in particular?
You mean on the artists list? So long as it's information in your library, I think this would be ok.
I think this should work within the same page, e.g. if you choose 96 albums it should stick for albums, but not artists.
Are you saying it should stick across all types?
As it's unlikely browsers will lower their security standards, I can't see a link to the folder ever being a possibility.
Since https://www.blisshq.com/music-library-management-blog/2018/03/01/release-20180301-album-tags/ we've had the ability to see the folder name. In addition I've added the ability to copy/paste to the next beta.
The final option is to add a file based browser to bliss, and link to that. If there's some support for changing this idea to support that, I can change this idea's title. Otherwise, I'll mark it declined.
It depends what you mean by "bring the user to the location in the file system where the represented album exists".
It's hard to just pop up an instance of Windows Explorer pointing at that folder.
Chrome won't even let you open file:// links *at all* when the original content is served over http.
However, if you just want to see the locations listed so you could copy and paste into Explorer, that's easy.
I like the intent of this idea. There's a fundamental problem though, in that bliss is designed as much to work on servers as it is a local desktop or laptop. If bliss is installed on a different computer you cannot open up the OS's file navigator to that location.
This is why the 'Browse' button, when choosing your music library, doesn't show the standard OS navigator, it shows the file system for the server that bliss is installed on.
If bliss listed the actual files within the Web UI, would that be ok? Were there things you know could not be achieved by doing this? I guess I'm asking what sort of things you would do with the OS navigator.
As stated, for tag *completion* this should work with the "autopopulate" checkbox. If it doesn't it's a bug.
Can you confirm this is with the missing information rule, or the accuracy rule?
@Mike you mentioned missing genre in the other thread - that should be automatable, there's a checkbox next to "Fill in missing" "Genre" for "Autopopulate".
@Joe Year, genre and disc number should already be automate-able... send an email to support if that isn't working.
So the way I expect to implement this is similar to http://ideas.blisshq.com/forums/21939-bliss/suggestions/5746094-tag-correction , only instead of changing an existing tag, the tag is populated. Each album gains the ability to be linked to an online record of the release.
That way, we could also implement http://ideas.blisshq.com/forums/21939-bliss/suggestions/1043507-realtime-album-info (three features for the price of one... almost).
Thanks. You're right, only certain things can be automated, and these can be seen from the settings page.
Automation of the filling in of tags is very much in my sights. Just like http://ideas.blisshq.com/forums/21939-bliss/suggestions/5746094-tag-correction but for tag completion.
Shall we change this to "Automatic tag completion" and then if you have a requirement for other items to be automated we can add them as separate ideas?
Interesting use case @jake ... let me know if it works!
@Anonymous (Johan Kraus) you can do this already using the track number padding rule (https://www.blisshq.com/music-library-management-blog/2011/07/16/padding-track-numbers-with-zero/) or if it's the files that are out of order, use <tracknumber:nn> : https://www.blisshq.com/music-library-management-blog/2011/12/14/new-release-20111206-padding-file-org-acoustic-fingerprints/index.html
Yep, agree with that.
Not sure what you mean by "Once the files are hashed it's easy to detect corruption, but what about before that?" - isn't detection, and alerting of the issue, the end point?
It's not supported by bliss currently but it's supported for any application that wants to get to it. It's in the METADATA_BLOCK_STREAMINFO header inside a FLAC file. The FLAC command ilne supports using it to test files: https://www.blisshq.com/music-library-management-blog/2015/03/31/test-flacs-corruption/
The more I think about it the more I like this overall idea. Seems to be something a lot of audiophiles want.
It should also have the ability to plug into existing checksums, e.g. FLAC's own.
@Bernardo, in your case (2) would definitely be preferable.
I think this would just be a rule to monitor checksums and alert if one has changed.
I've been talking to another user on email about this. The way he described it really made it sound like it would be a fitting part of bliss. These kind of things are discussed often over at Computer Audiophile.
It fits into the consistency - completeness - correctness mantra - maybe adding a new dimension: integrity or security?!
Which backup are you referring to? Normally you'd only run bliss against a "gold" master library, and back that up separately, which bliss wouldn't touch.
One general way of achieving this might be to support copy/paste for multiple lines/columns. This is the way it's done in some other tools. It depends on the support for the approach within the table component we use (SlickGrid atm).