That's an interesting subtlety any implementation would have to cater for...
> am I missing something?
Only a time machine ;-)
Seriously, this is on the roadmap, it clearly has a lot of support.
It appends a suffix number, e.g. _2, _3 etc...
Jake, if you have the time it would be interesting to know if the fpcalc tool (the same fingerprinter bliss uses) generates the same fingerprint for the tapes and the other recordings: https://acoustid.org/chromaprint . If you get the chance, run fpcalc from the command line giving the music file as an argument. Copy and paste the results and send to email@example.com ... if you don't get the time, don't worry ;)
I remain to be convinced!
Sounds like it would be a case of adding these to the list, and also forming them as part of the genre tree.
Note that the R128 algorithm/method is an emerging standard in this space and should probably be implemented too!
bliss uses something called inotify to be informed of file changes (not made by bliss).
There's a limit to how many files you can listen to. On Synology the limit is set quite low (if I recall correctly) and so these error messages are triggered.
It means bliss won't listen to file notifications from some files, but should still work otherwise.
Note it may also impact other software; the limit is global.
Thanks for posting this. I definitely think the repeated messages are a problem!
Hi - only certain rules are automatable, e.g. the maximum size rule (but this only applies to resolution, not data size). The image format rule is not automatable.
The semi workaround is the "fix all visible" buttons on the Inbox. Do these help?
"When time allows you can search for no album art files"
Why can't you use the missing art filter for this? On the left of the albums page?
@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?
It has always been intentional not to move other files (note we should also move image files though). That's partly because I'm not sure what to do about name clashes.
Great idea - should they be exactly the same? I think that's the easiest place to start.
Ok, I misunderstood this, and I understand you now.
For example, if a licence expires on 31st March 2018 and a new licence is purchased on the 25th March 2018, once installed the new expiry date will be 25th March 2019. You're correct, it should be 31st March 2019 (we ain't Costco ;-) ).
This requires a fix in bliss, and I'll look at it for the next release.
Hi - please get in touch with me by the support email address. There are actually two types of renewal to cover this, and I think one batch may have been submitted of the wrong "type".
Sorry - shouldn't have marked this completed before...
I think there are a growing number of ideas relating to actions following compliance is met. Some more:
Compliance status could be considered a selector as part of ruleset selectors: https://www.blisshq.com/music-library-management-blog/2017/08/01/ruleset-selecta/
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?!
Certainly no reason other than it hasn't been implemented yet ;-)
I merged Matt Jenkins idea into this one:
"Being able to search your database for artists, albums, albums of a specific genre, etc would be a huge bonus.
When you have thousands of albums spread amongst many hundreds of artists finding the album or artist within the artist and album displays is an onerous task. A simple search box that returns simple text matches for artist, album, genre, etc., would be a good start. Advanced searches where you can search for strings within the specific topics of artist, album, genre etc., would be even better."
I agree. As more stuff is added to the interface, a search function becomes one of the easiest way of finding things.
I think it should be top level (accessible from any page) and it shouldn't just search for albums, artists etc.... it should also search for bliss concepts. E.g. search for 'settings' - suggests a settings page. Search for 'albums' - suggests the album overview page. Anyway, that's a vision, maybe first step would just be album/artist search as you say.
@eaDir folders should be ignored already, as should most image files and desktop.ini files.
Does this relate to moving files, or are you saying the album isn't even being scanned or shown in the UI?
Could you send a debug archive? "Help" > "Download debug archive". It should show any files that stopped old folders being removed in the event of folder movements.
Yeah, the selection by genre bit would be covered by rulesets for those not familiar: https://www.blisshq.com/music-library-management-blog/2017/08/01/ruleset-selecta/
There's no separate idea for that, although see http://ideas.blisshq.com/forums/21939-bliss/suggestions/5490000-individual-rulesets-for-different-locations
You're right - OMA uses release group tags, that are within a defined set of genres, as genres. It also uses Discogs genres. So it would just be a case of importing the style information as well to at least get at the data. As you say, the most tricky question is how these should be treated and inserted in a library.
Nice idea. In the new versions of the metadata server we do allow multiple genres to be returned, this would fit into this. The question may be whether it's important to have styles and genres intermingled. I think the distinction is highly subjective in a lot of cases.
Nice idea, also see https://www.blisshq.com/music-library-management-blog/2015/09/08/big-idea/ .
No, fixes could still contradict or depend on each other to some extent, I was just suggesting a general approach. It needs to be done on a case by case basis really.
"Missing tags Genre / years" should be filed under "Tag fixes"; the tag type rule is simply for changing ID3v1 to and from ID3v2.x.
Your other examples were correct.
Anyone finding this thread interested in "it would be great to have one button to fix all the above" see http://ideas.blisshq.com/forums/21939-bliss/suggestions/10273929-fix-all-tags-instead-of-the-viewable-ones
I changed the title because this is a general issue.
Yes, some fixes can conflict, e.g. changing the album name will mean there should be a different file path, if you have those settings configured. In that case, at the moment, you should refresh the Inbox page. But you have a general point...
Generally, I would fix in this order:
- Tag type fixes (e.g. ID3v1 -> ID3v2)
- Tag fixes (e.g. fix album name etc)
- File paths
- Cover art
Can you send a screenshot by email (or somehow upload)?
Well, one thing might be to fully automate all rules in some way, then you wouldn't even need the button... is this max data size?
A workaround to get a larger inbox is to edit the URL. Check the URL, you'll see "albumsCount=48"... change "48" to whatever number you like... note this might crash bliss so be a bit cautious!
Thanks for suggesting this. When I was writing this up it was a quandry what to do - if we have a "Fix all" then it's more difficult to show progress (currently we just rely on the visible buttons that are clicked for you, and any errors should show next to those).
Maybe a small activity popup at the bottom of the screen would help.
Where you see folders being left behind, please send a debug archive "Help" > "Download debug archive" to firstname.lastname@example.org
Broadly speaking this is a common requirement in different environments, because many music players require a "rescan" even if its only tags that have changed.