AdminDan Gravell
(Founder and programmer, bliss)
My feedback
499 results found
-
3 votes
An error occurred while saving the comment An error occurred while saving the comment This is a nice idea. Internally in bliss there is a rule language, used by some of the rules. It's of the form:
noncompliant because "[reason]" when [boolean condition] {
fixedby
[list of responses]
}The language itself is just the start, the language then needs objects and API a plugin writer can introspect. So here's a more complete example, the track artist rule (checks only one track artist in each album):
noncompliant because "Track artists differ" when album.trackArtists.size > 1 {
fixedby
com.elsten.bliss.music.policy.tagsync.trackartist.SetTrackArtistsInStorageNodesResponse(album,album.trackArtists),
if album.artist != mode(album.trackArtists) com.elsten.bliss.music.policy.tagsync.trackartist.SetTrackArtistsInStorageNodesResponse(album,album.artist)
} otherwise "All track artists are the same"Here you have the "album" object which contains all the info about a given album, according to bliss. The xResponses are essentially 'fixes' which may or may not run automatically.
If anyone has any feedback they're welcome to share.
-
1 vote
An error occurred while saving the comment The first point may mean the playlist has to be edited, if it's using relative paths.
For the second point, see http://ideas.blisshq.com/forums/21939-bliss/suggestions/1189065-manage-playlists-with-regard-to-the-planed-organi
-
2 votes
An error occurred while saving the comment We might also need to define "unidentifiable". Does that mean:
- Untagged?
- Albums that have no linked releases?An error occurred while saving the comment Do you mean select to then move the albums to a separate folder, so you can work on them?
An error occurred while saving the comment Would it also be useful to simply list the rogue files/tracks/albums somewhere in the UI?
-
2 votes
An error occurred while saving the comment Interesting idea.
Note that if the original cover is less preferable in a consistent way to bliss's you could define a rule that means bliss will replace the art.
For example, if the original cover is always 300x300 you could define a min size rule of 500x500 and ask that bliss always replace automatically.
But I realise this might not always be the case.
-
1 vote
An error occurred while saving the comment Do you just mean a text search of your library (inparticular the release title)?
-
6 votes
An error occurred while saving the comment Yep, moving all the albums in a genre to another would also be easier then.
An error occurred while saving the comment There was a bug where this could sometimes happen with music files that have mandated genre lists, e.g. MP3s, although I thought it was ok now.
Can you send a separate email and include a debug archive which includes the attempts to change in the log (i.e. recreate the problem, then create a new debug archive)?
AdminDan Gravell
(Founder and programmer, bliss)
supported this idea
·
An error occurred while saving the comment I agree - and I wonder if a treemap visualisation would be helpful for it too - https://en.wikipedia.org/wiki/Treemapping
-
4 votes
An error occurred while saving the comment It looks fairly easy to enable automation but I also have to double check how it works when it actually runs. I can't make any promises about when I'll get to it - I've got loads of stuff backed up.
An error occurred while saving the comment Sounds like a sensible one we can automate...
-
2 votes
An error occurred while saving the comment I agree - short term I could change that text. Longer term we could just offer any existing art anyway.
An error occurred while saving the comment The problem is that the _Embedded art_ option is set to _Ignore embedded art_. Setting it to _Embed art where possible_ will cause bliss to use the artwork for folder.jpg.
However, it will also cause bliss to embed artwork from folder.jpg. Maybe that's what you don't want?
An error occurred while saving the comment Thanks Steve.
An error occurred while saving the comment This should already happen (unless the embedded art is itself non-compliant for another reason, e.g. too large).
Can you send screenshots and the debug archive?
-
1 vote
An error occurred while saving the comment Nice idea - I don't think we can show all this information all the time though, it would have to be a popup of some kind.
Resolution (x by y) should already show at the bottom left of the image. If it doesn't - which page are you looking at?
-
1 vote
An error occurred while saving the comment You could probably do this with a find and replace regex - https://www.blisshq.com/music-library-management-blog/2019/02/13/find-replace-rule-fix-html-encoding/ (and also the consistent hyphen spacing too).
A not very easy to use solution but...
-
1 vote
An error occurred while saving the comment Are these albums where the track titles have been corrected? I suppose this is an inconsistency in source databases, therefore we'd have to have a setting in bliss to reconcile this to a consistent form in some way.
-
1 vote
An error occurred while saving the comment Yeah, I agree on the before/after text. I've been trying to think up a common UI for such changes which would be used on all the screens. As ever it's a case of balancing the real estate required for such a change.
-
1 vote
An error occurred while saving the comment This is an interesting development of http://ideas.blisshq.com/forums/21939-bliss/suggestions/1928497-ignore-compliance-for-certain-albums I think - it takes it one step further, giving a _reason_ for 'ignoring' the compliance, as it were.
-
1 vote
An error occurred while saving the comment Why not just click the button again?
-
3 votes
An error occurred while saving the comment Yeah, I agree. We could even make the single fix buttons a bit less prominent (currently they can look a bit... ugly) and have a separate "Fix album" button with a pick list for all fixes you want executed, and then a single rescan.
-
6 votes
An error occurred while saving the comment Nice idea - I think this would have to be built into the existing rules, because otherwise they would conflict (e.g. what would it mean to have the missing tag and remove tag rules configured for GENRE?)
-
4 votes
An error occurred while saving the comment Cool, thanks for the update. Obviously this approach isn't ideal, but wanted to provide a workaround if you needed it.
An error occurred while saving the comment You'd have to use ssh, like in https://www.synology.com/en-global/knowledgebase/DSM/tutorial/General_Setup/How_to_login_to_DSM_with_root_permission_via_SSH_Telnet
Then:
cd /var/packages/bliss/target/var/.bliss
cp setttings settings.bak
nano settings
[make the changes then ctrl-o, ctrl-x to save and exist]Then restart bliss.
An error occurred while saving the comment So, similar to http://ideas.blisshq.com/forums/21939-bliss/suggestions/3132936-allowing-for-custom-sizes-and-dimensions-for-the-a
Workaround: this is possible to do yourself by following these instructions: https://www.blisshq.com/music-library-management-blog/2018/01/09/custom-album-art-sizes/ except change:
com.elsten.bliss.music.policy.coverartpolicy.CoverArtPolicy.maxDataSizeBytes=262144
To the number you want...
-
3 votes
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment Yeah - currently we just use the fingerprints on their own. If we combine this with data online, we could recognise where the fingerprints _should_ be the same.
An error occurred while saving the comment Do you have an example album when this happens? If it happens it's not because of the name, it's because the audio is judged to be too similar.
-
1 vote
An error occurred while saving the comment The Inbox is due to be replaced soon; this is good feedback that can be applied to the new page.
An error occurred while saving the comment Which page are you referring to?
See also https://www.blisshq.com/music-library-management-blog/2017/10/25/setting-various-artists-name/