AdminDan Gravell
(Founder and programmer, bliss)
My feedback
502 results found
-
1 vote
An error occurred while saving the comment -
2 votes
An error occurred while saving the comment No... but what car and radio system is this?
An error occurred while saving the comment Sounds like a bug, can you send a debug archive?
-
3 votes
An error occurred while saving the comment The trouble with infinite scroll is the back button is often broken...
You can hack this by changing the parameter in the URL "albumsCount" to a number of your choice.
-
2 votes
An error occurred while saving the comment This would have to be done on a case by case basis, and I would suggest saving the information in the Activity page with a specialised filter (or maybe the "scan" category could be used)...
Could you also send us a debug archive to support@blisshq.com with the files that weren't processed for you? We can check the cause is logged.
-
2 votes
An error occurred while saving the comment Titles?
-
2 votes
An error occurred while saving the comment bliss does keep a watch but it does so using inotify; there should be no-where near 25% CPU usage. Something else must be going on. Note if you have the Web UI showing this can sometimes use some CPU, and obviously if there's a scan going on that will too.
An error occurred while saving the comment Thanks Nathan, nice idea. Would this be covered by: http://ideas.blisshq.com/forums/21939-bliss/suggestions/9161260-move-music-files-between-libraries ?
-
2 votes
An error occurred while saving the comment If we just supported different cases in the filename field, would that work?
-
2 votes
An error occurred while saving the comment Do you mean file size (I changed the title)?
-
2 votes
An error occurred while saving the comment I'm surprised a scan of an individual album should take so long and slow down other albums so much. What are you seeing that suggests this is the case?
-
1 vote
An error occurred while saving the comment I think the nicest way of solving this would be:
1) Not discarding compliance data between releases and
2) Maintaining historical stats (and a way of viewing them)I've had the thought that (2) should be part of a dashboard on the home page of bliss (rather than albums).
-
1 vote
An error occurred while saving the comment It really depends on what the canonical release name is. In some cases, this will include the composer name, in others it won't. And in other cases the data from the databases might be wrong, as you identify.
I can see the value with this, just explaining why bliss does what it does.
One way of ignoring some releases would be with https://www.blisshq.com/music-library-management-blog/2017/08/01/ruleset-selecta/
An error occurred while saving the comment Interesting, thanks.
That style guide is written for the benefit of the iTunes Music Store, not a music collector. Most music databases will seek to preserve the release name as the sole release title, removing any other polluting data. So I would start by assuming the current approach is the correct one.
That said, it doesn't help working with iTunes music store collections if consistency is key. This sounds like a good application of http://ideas.blisshq.com/forums/21939-bliss/suggestions/31738582-derived-tags
-
5 votes
An error occurred while saving the comment I'm not familiar with them - they appear to be standalone programs.
An error occurred while saving the comment Erm, which image is that?
An error occurred while saving the comment Indeed - but automation can only happen, really, when there's some intelligence about allowing one file to remain.
An error occurred while saving the comment 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.
-
1 vote
An error occurred while saving the comment Just tried this - it works fine. It requires cookies to be enabled - could that be the problem?
-
22 votes
An error occurred while saving the comment 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...
An error occurred while saving the comment 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.
An error occurred while saving the comment You either:
- 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/An error occurred while saving the comment An error occurred while saving the comment 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.
An error occurred while saving the comment 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:
http://www.blisshq.com/music-library-management-blog/2012/01/13/organising-multi-disc-album-files/
... but that doesn't work where discnumber=1 and it's single disc.
-
1 vote
An error occurred while saving the comment This would be useful for sure! Thanks for posting.
-
1 vote
An error occurred while saving the comment Should they? Some people might want to find duplicates and delete the MP3 (for example). I think this should be setup with a heuristic.
-
21 votes
An error occurred while saving the comment 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.
An error occurred while saving the comment Deleting from bliss, and/or deleting the actual files from disk?
-
2 votes
An error occurred while saving the comment On the albums page you can use the compliance filters on the left to narrow down to just albums with duplicates. Does that help?
-
13 votes
An error occurred while saving the comment Agree - it does point to having special ways of forming file names being a good idea.
An error occurred while saving the comment 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/
An error occurred while saving the comment <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!
An error occurred while saving the comment 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).
An error occurred while saving the comment Thanks. Is this for the file organisation feature?
-
1 vote
An error occurred while saving the comment Thanks - which list in particular?
I don't know of an "official" API for controlling Sonos devices (or performing a rescan) but I do know there are unofficial approaches: https://github.com/jishi/node-sonos-http-api