AdminDan Gravell
(Founder and programmer, bliss)
My feedback
502 results found
-
2 votes
An error occurred while saving the comment An error occurred while saving the comment Wouldn't you normally use your music player's own rating system to do this? How would bliss help here?
-
2 votes
An error occurred while saving the comment Thanks Andrew. To clarify: where are those filenaming conventions and string replacements important?
An error occurred while saving the comment Ok, assuming you have enough votes left, could you create a new idea for the scaper idea? Describing what it does (you can just copy and paste).
I can change this idea to be the control over filenames.
The 'support for more media streamers' can only really be added when the media streamers that are required are named, and the nature of the support is described. I need these ideas to be 'SMART' - http://en.wikipedia.org/wiki/SMART_criteria
An error occurred while saving the comment Ok, I'll change the title to "More control over the image file name" and do a little editing of the description (remove the first para, maybe introduce with the concept of more control over the filename and then have the rest of how this works with the WD TV Live). Is that ok?
An error occurred while saving the comment Ok, now I see why you said "This leads onto support...". If you had the control over the filename you could do that, right?
An error occurred while saving the comment Thanks for this Andrew. It's always interesting to hear of specific uses with different pieces of hardware/software.
I really want to keep to a one idea:one thread approach so it's easy to measure how in demand different features are. In this idea I count at least three ideas, so I'd like to split them:
* Increase number of sources
* Allow for optional naming of external files
* Better interoperability with the WD TV Live metadata facilityFor the first one, I've already declined http://ideas.blisshq.com/forums/21939-bliss/suggestions/2980994-more-cover-sources and I'd want specific sources to be suggested, ideally one per thread again. WRT Google and Amazon, both of these do not allow automated querying of their API via bliss. Google allows manual querying (which is why bliss uses it for the change cover art screen). Amazon changed their ToS recently to stop certain accounts that don't sell etc via Amazon, which stopped bliss using Amazon. So please don't add either of them.
The optional naming of the external files is a great idea and should be in a separate thread I think. I could add my own ideas about how this could be parameterised.
Which leads me to the meat of this idea, I think. Unfortunately I don't fully understand whether you are asking for bliss to read the .metathumb files (and so use this data to populate tags inside your music files), or bliss to write the .metathumb files from the data it finds (and so help the WD TV Live to show data that bliss has found).
I think all of these ideas are valid, I just want to organise them appropriately so that they can be voted for and the votes mean something.
-
6 votes
An error occurred while saving the comment It depends on the music player. If your music player doesn't show the composer tag, and you want to browse my composer, then you're stuck.
I agree that ideally the composer tag should be used.
The whole manner by which 'classical' composers, performers, conductors and the like are tagged is discussed in http://www.blisshq.com/music-library-management-blog/2011/03/23/composers-performers-soloists-conductors/
-
27 votes
An error occurred while saving the comment @Adam adding new maximum sizes is easy, so I just added that in. It'll be in the release after next, in about two weeks.
An error occurred while saving the comment There is a possible workaround for this that I haven't tested. The settings are kept in a text file in the following location:
{user folder}/.bliss/settings
Inside you'll see lines such as:
com.elsten.bliss.music.policy.coverartpolicy.CoverArtPolicy.approxMaxHeight=2147483647
com.elsten.bliss.music.policy.coverartpolicy.CoverArtPolicy.approxMaxWidth=2147483647
com.elsten.bliss.music.policy.coverartpolicy.CoverArtPolicy.approxMinHeight=0
com.elsten.bliss.music.policy.coverartpolicy.CoverArtPolicy.approxMinWidth=0Stop bliss, then change those numbers to what you want the max height, width and min height, width to be (in pixels).
Then restart bliss.
I don't recommend keeping it this way for a long time... I'm not sure how the user interface will 'react'.
An error occurred while saving the comment I've not added in a new size since in 900x900 option... Maybe the final step should be a custom sizing option.
An error occurred while saving the comment Luca, what's possibly not that clear is that there's actually a leniency allowed for looking for art, which is 10% either side, or 10 pixels maximum. So if you have 500x500 minimum, it will find art that is 490x490. However, such art will still be marked uncompliant. It would be good to allow leniency in the rule (and also maybe alter the leniency so that, in your example, 450x450 is allowed).
An error occurred while saving the comment I added in a 900x900 option, but custom sizes are still left to do.
-
2 votes
An error occurred while saving the comment Thanks Bernard, this applies to all platforms so I removed the 'ReadyNAS' from the title.
The reason for this is mainly programming expedience. Different versions of bliss have different internal code, mapping the stored data to that code can be complicated when things are added or removed.
It's certainly possible to do though...
-
8 votes
An error occurred while saving the comment Sorry for taking a while to get back to you....
This is quite an interesting one; I could get philosophical! In my opinion, a single is still part of a 'release' - that of the single. To me, the 'album' tag is misnamed, it should be 'release'. Therefore, in these occasions the single file should be tagged after the single release from which it came. In the case of CD, cassette or vinyl singles you will also have B sides on the same release.
But, of course, it's up to you how to organise your own collection. How would being able to designate tracks as part of an album help? Would you like the album's cover art adopted?
-
3 votes
An error occurred while saving the comment Sorry it's taken a while to get back to you on this...
If the source of the art is Google that's a problem... It's against the ToS of the Google API to automatically query and use that art.
I don't quite understand what you mean by "the difference is that right now there's NO artwork - I'd rather have some with the wrong artwork until I've reviewd them.". Do you mean that the automatic scan is not finding anything so you'd rather take your chances whatever would be found by the manual scan? If so, see above... it's likely that it's Google that's finding the ones under the manual scan.
Have you tried: http://www.blisshq.com/music-library-management-blog/2012/01/24/new-release-20120119-cover-art-alternatives/ ?
-
2 votes
An error occurred while saving the comment Thanks Mark. That's a good point about the UI not scaling... something that will have to be addressed as more tokens are added.
-
3 votes
An error occurred while saving the comment I really like this idea. I would remove the top level 'tags' item, and instead within albums, artists etc have an 'advanced' view which used the general filter criteria currently applied. It's a bit like a file explorer's grid/details view (see http://ideas.blisshq.com/forums/21939-bliss/suggestions/1859381-add-a-table-details-overview-in-addition-to-the-g )
-
2 votes
An error occurred while saving the comment Yeah, you're right, FreeDB has an enormous amount of data. Trouble is it's lower quality (IMO) than MusicBrainz. That said, I think by passing it through bliss's 'pipelines' of processing (e.g. changing the genres, changing the capitalisation) we may be able to improve the quality.
An error occurred while saving the comment Ok so more like a general tag correction/completion feature for existing albums?
An error occurred while saving the comment Thanks Bo. bliss already auto populates the year and genre information using the MusicBrainz and Wikipedia databases. See http://www.blisshq.com/music-library-management-blog/2010/11/28/mp3-tagging-software-new-release-20101120/ . Are there improvements to this you'd want to see?
-
2 votes
An error occurred while saving the comment Thanks Pär. Sounds useful. Maybe it could be an extension of http://ideas.blisshq.com/forums/21939-bliss/suggestions/2387358-automatically-rename-genres , e.g. wildcard * -> Jazz
-
2 votes
An error occurred while saving the comment Yes, nice idea. The 2MB maximum size is a limitation right now.
-
3 votes
An error occurred while saving the comment Thanks Todd!
An error occurred while saving the comment Thanks for letting me know. I'll leave this open; theoretically this could be added.
Could you paste the entry in your service manager php file?
An error occurred while saving the comment Thanks. This looks fairly simple to do manually - it's documented here: http://info.vortexbox.org/tiki-index.php?page=servicemanager
Doing it automatically upon install might be a bit more scary. It would be easier if there was a separate conf file for these items that could just be appended to.
-
3 votes
An error occurred while saving the comment Nice idea. I was thinking about actually building in the Wikipedia content into the page, although clearly separating Web-sourced content from the content represented from your music files might be a challenge.
-
2 votes
An error occurred while saving the comment I edited the title to specify simply Musepack support. It's easier to track these ideas if it's just one per page.
As you said, a workaround may be for bliss to identify music via filenames. For identifying music via file names, please vote for http://ideas.blisshq.com/forums/21939-bliss/suggestions/2458603-use-the-folder-and-file-name-to-help-identify-song
However, note that even when identifying music via file names, embedded art would not be a possibility for Musepack files until the Musepack support is written... folder.jpg style files should be a possibility though.
Hope this is ok...
-
5 votes
An error occurred while saving the comment Thanks Barry, I think I understand now. You are referring to the <album artist> token in the file organisation rule.
Yeah, you're right this is hard baked to use whatever bliss works out to be the album artist. In this case, either the album artist tag in your music files is "1987 Broadway Revival Cast" or all the track artist tags in each track are.
This is a little different because essentially you want to override what the <album artist> token evaluates to.
I wonder if your other idea - "custom toggle for cover art threshold specs" - actually hints at a solution? One way of approaching it may be a way of overriding compliance for a given album with different rules. In this case, you could reset the file org pattern just for this album.
An error occurred while saving the comment Barry, there's no rule in bliss that checks album artist. When you say bliss is assessing the compliance of the album artist, what do you mean exactly? I would think something else for which you have a rule enabled is non-compliant, hence the current status.
-
2 votes
An error occurred while saving the comment Oh yeah - compliance would appear on all such screens. Ultimately, that's what bliss is about.
An error occurred while saving the comment A powerful way of doing this would be to add a tables view of albums (rather than the grid view), having a 'added' timestamp column and then ordering by any of the columns. That way you could also order by artist name, art size and whatever other columns existed.
I suppose an order by... option on the grid view is also possible, although you might not see the actual data you are ordering by.
It depends how important it is to retain the grid view when viewing latest additions.
BTW, you could also look at the activity view, although this would be mixed in with other activity. Adding a 'New album' activity and allowing the activity view to be filtered would be (yet) another way of achieving this.
-
4 votes
An error occurred while saving the comment But was the 'album' split into several albums by artist? I think this could be the only way this would happen.
bliss should group files with the same album name but different track artist if they are in the same folder.
The reason I'm concentrating on the identification of the album is because this forms the basis of the lookup for cover art. If the album/artist name is wrong/inaccurate, you're much more likely to get a bad match.
An error occurred while saving the comment Can you tell me a little more about the albums... what was the album and artist name? Was it the same album split by artist?
-
2 votes
An error occurred while saving the comment That's a nice idea. The list of ID3 genre mappings are here: http://www.multimediasoft.com/amp3dj/help/index.html?amp3dj_00003e.htm
The rule could be 'enforce textual genres' or 'enforce numeric genres'.
-
3 votes
An error occurred while saving the comment Yeah, agree this needs doing. Adding arbitrary tag columns. Right now the workaround is to copy a file with the required tag into that folder!
Sure, that makes sense. By 'music player' I just mean whatever is displaying those ratings. The reason I ask is because there are multiple ways of storing rating - some write to tags (like you are suggesting) and some store the ratings themselves.
But if this is about tagging rating in the music file, then that's all good.