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/
"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!
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 ·
Trim rules (removing whitespace from the start and end of the tag) are in the current beta, due to be released next week. Removing HTML encoding will probably have to follow in the release after that…
See the comments for a screenie of the trim rule.
Where do you see that problem? Please see http://ideas.blisshq.com/forums/21939-bliss/suggestions/20164318-truncate-filenames-to-comply-with-file-system-limi .
As mentioned in http://www.blisshq.com/music-library-management-blog/2015/11/17/new-release-20151110-aiff-wav-tagging/ it's now possible to drop a custom rule into a file for removing HTML encoding. I'm intending to write a blog post in a little while to describe how to do this. Once that's done I'll close and "complete" this idea.
It's a way of writing a rule which you save as a file in a well-known folder and bliss finds it then shows it in the settings. It's early stages (which is why I don't want to "officially" support it yet) but should work for this, possibly inelegantly at this stage.
The new beta (out next week) does have an interesting undocumented and unsupported feature (which I'll blog about anyway) where you can write your own rules using regular expressions. You could implement HTML decoding yourself using that... remind me and I'll provide an example.
Here's the trim rule work in progress: https://twitter.com/bliss_music/status/632573983179694080/photo/1
When you edit music in bliss the file will be re-written and that might clear any corruption. You might also want to read http://www.blisshq.com/music-library-management-blog/2012/10/16/mp3-repair-fixing-mp3s/ .
This is a bit off topic for this idea I think... See http://ideas.blisshq.com/forums/21939-bliss/suggestions/2599926-the-ability-to-check-the-integrity-of-music-files
Fred, I edited the title to include the actual work to do... I like to keep these ideas easily measurable, and the title was arguably too broad to measure (just "Auto tag cleaning options") before.
Thanks for this extra detective work, it will make it easier to find the issue!
The only way to make this faster is, as you say, to scan a subset of folders, such as just the root. However I'm having trouble framing that as an option - seems a bit too technical for some to understand.
Maybe the ability to import/add a folder would be better?
In theory this is simple, but to reduce confusion I think we'd also have to clearly indicate when the saved rules are different to those that were last used to assess albums (we could call them "dirty" or "unassessed" or something).
To an extent, 2a is in principle already covered by the accuracy rules - only trouble is it doesn't work for completing missing fields!
Thanks for the very clear clarification!
What sort of problems? Do you mean issues with the way bliss updates the album artist tag?
Right now, bliss shows different tags depending on the album artist... If an album artist is set, that is what is shown in the artist field. If not, it's the track artists.
Sounds good. I think the 'rule' for this might be a checkbox declaring "album artist" must be set for each album, and the response (when it isn't) is to set the album artist as you say.
Could also check that the album artist is accurate... I had a case the other day where two tracks on an album had different album artists, and the rest of the tracks had no album artist. That's asking for trouble...
Do you mean the label etc should be considered when scoring and auto linking releases?
Nice idea. Also, latest albums, or stats (% compliant etc).
I guess this is the other side of http://ideas.blisshq.com/forums/21939-bliss/suggestions/2739754-automatically-complete-album-artist
i.e. if there's no consistent artist, use "Various" (or whatever you want!)
The capitalisation rule only works on existing tags... is that what you mean? It doesn't use any online resources.
If you make a copy of these files you're sorted: https://www.blisshq.com/support/faq/general/move-new-computer.html
You will need to use ssh to log into the QNAP to find the source folder, and then potentially scp to copy the files.
Could definitely be done!
Just in case anyone wondered how to do it manually...: https://www.blisshq.com/support/faq/general/move-new-computer.html
There is a cancel scan button - https://www.blisshq.com/music-library-management-blog/2018/04/03/release-20180326-cancel-button/ - was it specifically pause you wanted?
Oh, I see. Yes, I agree. I think a better filter would be useful - I see you've already seen http://ideas.blisshq.com/forums/21939-bliss/suggestions/2591793-add-ability-to-filter-and-print-the-activity-log
@mactigerman - the message is saying bliss *has* ignored that folder. The folder consists of files with .mp3 extensions but they aren't mp3s, they are metadata of some sort that the Synology stores.
Is that what you expected?
@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.
While it still rescans, the new version of bliss should have some improvements to rescan speed; it now caches fingerprints (a big deal on Synology and other lower speed devices) and lookup results across versions.
I like it. I believe AcousticBrainz might do this, e.g. https://acousticbrainz.org/7eef7a92-e282-4cf7-89a4-c35d39ff3d4d .
Also see (for different types of mixing): http://ideas.blisshq.com/forums/21939-bliss/suggestions/1475605-update-bpm-field
Do you mean show them all as a single entry in Sonos or bliss?
Are these re-releases of previous releases in one box-set release?
Nice idea! Alongside playlist generation...
We don't actually use AcousticBrainz - we use Acoustid for fingerprinting, maybe you're getting mixed up with that?
No reason we can't use AcousticBrainz, of course...
3 votesAdminDan Gravell (Founder and programmer, bliss) supported this idea ·
It shouldn't work like this. If *at least* one linked release is correct, it's compliant. So what are you seeing?