For the next release, a more complete list of files/folders permitted for deletion is included. Please report re-occurrences of this with a debug archive.
For the next release, a more complete list of files/folders permitted for deletion is included.
That includes desktop.ini files and @eaDir folders.
Please report re-occurrences of this (subsequent to the next version) with a debug archive.
That's interesting; bliss should move image files into the target folder. If you get the chance, send me a debug archive - "Help" then "Download debug archive" and mention which folder/album this occurred with.
Oh yes, if the permissions are ok it should still move them... as before, please send a debug archive - http://www.blisshq.com/support/faq/general/how-create-debug-archive.html
Ah yes, in this case that will be a problem.
Thanks, please do!
Can you send a debug archive? http://www.blisshq.com/support/reporting-problems.html
This should actually happen. Can you send me a debug archive? Click "Help" then "Download debug archive". And also say some example albums where the folder wasn't removed.
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...
Agreed - same goes for the total count in the [left/right] page navigator...
Can you explain - there's already an "Artists" link which lists the artists... do you mean a list instead of a grid? What else should be in the list?
Slightly meta, but this would be an interesting one in the sense that always-automated missing artwork completion was bliss's very very first feature - I took the decision at the time that it shouldn't even be customisable to make the tool as easy to use as possible with as few settings as possible: https://www.blisshq.com/music-library-management-blog/2009/11/06/first-release/
I think it's a valid idea though.
Presumably you mean when the music is NOT synced locally? If it is synced locally, might it work?
I've seen problems before where some services store an empty "shell" file representing the real cloud based file, bliss assumes it's a full music file, and baulks when trying to scan it.
This would be useful, especially if the report button had a field where you could provide a URL for the correct release.
Can you send a debug archive separately - Help > Download debug archive? And confirm the name of the album.
Good idea. Do you mean adding the URL for the release? Where would you want to find the data from?
Also, it would be good if the incorrect release wasn't chosen in the first place...
Thanks. Things to consider:
- Total length of file path
- Length of individual parts of the file name (folder/file names)
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?
Yeah, this is definitely something that could be done. I like the idea, goes well with other "integrity" ideas like checksumming etc.
How big a problem is CDs being sold that are lossy transcoded to PCM?
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.
Jim, you're probably not missing something. The automation settings are in the settings page, where automation is possible.
I tend to take the approach of making a rule manual first, then after some testing and iteration, make it (potentially) automatic.
If there's a specific rule you think can be automated, add that as a separate idea.
I've had similar comments that it gets difficult to work with multiple track name fixes on the same album page, because compliance re-assessment occurs after each fix.
The Inbox might be closer to what you want, although it uses the same button-to-describe-fix approach. Thoughts on that?
Nice idea - maybe on the album detail page too.
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!
When using the release-canonical artist name, it would be just on a release by release basis. Maybe an artist released different albums with slightly different names!
I was referring to your comments on other ideas such as http://ideas.blisshq.com/forums/21939-bliss/suggestions/4461522-albums-and-artists-fusion
Agree about artist names being a difficult problem in isolation (we've seen that with the existing canonical artist name rule) but maybe what is easier is, when the release can be identified, the canonical artist *for the release* is used.
I can see how this would help; in some ways it might be a short term fix to help you find these artists until a rule can be developed?
Ok, so update on this is that I think to an extent release canonicalisation fixes this - if albums are split or duplicated with slightly different names, the album name correction rule should find them and suggest changing the names to the same thing (this would occur separately).
But I think this idea should remain open, basically because it could work around not being able to find the data for a release.
I see this more as a UI feature right now, rather than a rule. For example, being able to multi select as Bruno said to combine albums.
Yeah, there's definitely an aspect of this where you'd want to just fix it in your library, not necessarily use external definitions of canon.
Would canonicalisation fix this? If the "correct" name for the release was found and both albums were changed to match this (maybe one doesn't need to be changed) wouldn't that work?
I ask because we already have this for artists: http://www.blisshq.com/music-library-management-blog/2012/02/28/errant-artist-names/
I posted a way of automatically setting file ownership using inotify: https://www.blisshq.com/music-library-management-blog/2017/06/06/changing-permissions/
Took me a while to notice this one but here I am...
As bliss is written on Java 6, which has poor support for file permissions, this is difficult to do. If/when I move to Java 7, this will become much easier.
Yep, I think we'll end up going this way eventually. Did you see http://ideas.blisshq.com/forums/21939-bliss/suggestions/5490000-individual-rulesets-for-different-locations ?
The idea would be to convert all files from any format to one specific format, ignoring (but including) files already in that format.
Interesting comment. You don't think maintaining different versions of a file is a form of management?
The idea was also partly inspired by mp3fs ( http://mp3fs.sourceforge.net/ ) although obviously without the FUSE filesystem having the mirror leads to more duplication, so it's not quite as elegant.AdminDan Gravell (Founder and programmer, bliss) shared this idea ·
Very true, but then it's a similar situation elsewhere - depending on your player different fields can be interpreted in different ways.
Yeah, that's a concern when changing existing fields, but if we combine that with online data, where the date is formatted in a consistent way, we can work around that.
Also, more generally, support for formatting date/time fields. So you could specify:
As your format, so only years are stored. Or:
For a full date in the common US format.
Not sure how the date should be filled when there isn't enough information... maybe simply omitting the more specific parts would be fine.