Messages

you can grab the plugin either from my github repo (https://github.com/shimmerproject/gmusicbrowser/blob/master/plugins/artistinfo.pm) or directly from gmusicbrowser's git repo.

hm, i never thought much about this, but i think i agree with trasdahl on removing "space" from the songlist/tree as "play"-shortcut - i think having "enter" there is a) more common/logical/intuitive and b) sufficient.

Now this version has no more the layout SHIMMER BROWSER from 1.1.7 =( is there anyway to get it back?

i'm wondering how that can happen. the layouts should definitely be there, i just checked the package again right now.
could you check whether the file "shimmer.layout" exists in /usr/share/gmusicbrowser/layouts ?
thanks in advance!

 :)
quentin updated the artistinfo-plugin to the latest version (including the queue-mode) a few days ago, so feel free to grab it from there.
or if you're a ubuntu-user: i just recently uploaded a new version to the ppa which also has the new artistinfo-plugin (with the queue-mode) included.

clicking the "choose an album for me" context-menu entry crashes gmb with the following output:

Code Select Expand


Use of uninitialized value $Options{"PLUGIN_ALBUMRANDOM_update_automa"...} in numeric eq (==) at /home/ochosi/.config/gmusicbrowser/plugins/albumrandom.pm line 168.
Illegal division by zero at /home/ochosi/.config/gmusicbrowser/plugins/albumrandom.pm line 372.
(the first is only a warning that pops up when activating the plugin.)

if i try "generate multiple albums" gmb crashes with this error:

Code Select Expand

Can't call method "CalcScore" on an undefined value at /home/ochosi/.config/gmusicbrowser/plugins/albumrandom.pm line 600.


i'm using gmb 1.1.7 from shimmer-git and your plugin from your git.

k, found some screenshots now (something wasn't working well on the apple-website before).

do you know where the artist/album-related information/pictures come from? last.fm or some other service?

hey!
i looked at the page but to be honest it wasn't very descriptive and the screenshot basically showed a mosaic-mode (check out shimmerproject's party fullscreen-layout). what else is there? would you mind posting some screenshots or more detailed descriptions of what you want from that fullscreen-mode?

theoretically speaking, if you set up a filter and then start the shimmer party fullscreen-layout i don't see what would make that different from the app you described...

i adapted the code in the testing-branch to work with quentin's latest changes, so basically the queuemode in the artistinfo-plugin now works without changes to the core.

feel free to check it out. i'll upload new packages to the ppa in the upcoming days.

by request of laite i added an option to exclude the "seed"-artist from the queue. (meaning: if you want to listen to artists similar to "Bob Dylan" but not "Bob Dylan" himself.)

i looked into the api for the similar tags thing and to be honest i can't imagine how this could be useful.

in the example for artist.getTopTags you'll find extremely useless tags like "best mouth in rock" or various versions of the name "aleister crowley", also tags like "great voice" and "sexy". really not sure how this could be used to match anything else.

for album.getTopTags there are quite a few tags like "albums i own" (that's actually the top entry!) or "cd collection" etc.

i brought up these two examples now because i don't think that just using/probing the number 1 tag makes sense, i guess using more tags would give the whole thing more accuracy. if you just wanna use genres then it's probably best to just use your local genres (have fun tagging your lib with genres ;) ) and not rely on the very messy last.fm tags.

i don't see many alternatives at the moment, at least not via last.fm.

i think i'll display a warning in the artist biography's header if the artist-name on last.fm differs from the local artist name.

just added a small warning notice in the testing-branch. feel free to give it a spin (just use git pull if you're already using/testing it via git).


re: Note 1: yeah, i guess increasing the queue-limit in autofill helps greatly with this. good to hear it works for you!

re: Note 2: ok :) well it wasn't planned this way, but if it works ok then i guess i don't have to scratch my head too much about changing this.

re: Note 3: right, it sounds very do-able, just have to dig into the last.fm api a bit more and maybe invest yet another night... (not sure this will happen before next week.)


all in all i'll leave this in the testing-branch for maybe the rest of the week and if i can get more (positive) feedback until then i'll merge it into master and update the ppa with it.

I test the plugin with autofill number = 3. I'm not sure, but I guess the plugin do that : I've got a song playing (master) and 3 songs in the queue added by the plugin ; when the (master) song ends and the first song in the queue begin playing, I've got now only 2 songs in the queue, so the new song playing became the new master song for add a third song in queue. Do I understand well ? In this case, a hole could appear in the queue : an artist A can have the hole in his similar artist, but it's not reflexive (could be 50% of lastfm users listening A listening B too, but only 20% of lastfm users listening B, listening A too) so the hole could not have artist A in his similar artist.

k, i just started investigating this. it seems that the master artist is really affected by the queue. will let you know as soon as this is resolved.

For the hole (let down the bi-hole) it could be : if only one artist in local similar artist, then check the more frequent lastfm tag for this artist and choose song in the top artists ? For instance, Big K.R.I.T is a local hole here => the more frequent lastfm tag for Big K.R.I.T is Hip-hop => top artists for Hip-hop (http://www.last.fm/tag/hip-hop?setlang=en) are Kanye West, Beastie Boys, Eminem, OutKast, Jay-Z, A Tribe call quest, Black Eyes Peas, The Roots => I've got Kanye West, OutKast, Jay-Z, A Tribe call quest, Black Eyes Peas and The Roots in my local library !

not sure about it, but maybe. alternatively there could be a "similar-tag" autofill-mode for the queue, maybe that would even work better...

Same problem here : Angus And Julia Stone has Kings Of Convenience in similar artists, but Kings Of Convenience only has Angus & Julia Stone in similar artist (doesn't match with my local name).
Not solvable IMHO.

i think i'll display a warning in the artist biography's header if the artist-name on last.fm differs from the local artist name.

one more note: i'm not entirely sure how to solve this issue (maybe i even can't) but e.g. "Kings of Convenience" and "Kings Of Convenience" are seemingly not matched when they should similar to something else.
in the above example "the whitest boy alive" shows up as similar artist of the "kings of convenience", but the "kings of convenience" don't show up for the "whitest boy alive". in this example it's simple upper/lowercasing that creates the problem and i guess i can work around that, not sure about more difficult matching problems (that i'm sure will appear, e.g. "Surname, Firstname" vs. "Firstname Surname").

I think when a hole appear, the plugin must find a way to escape !

odd, that sounds a bit like the queue can "fall into a hole" while playing. but since the master artist is never changed while the queue is playing i'm not sure how this can happen for you.

if you mean that with some artists and settings there's a "hole" or even a "bi-hole" then yes, this obviously can happen. the question is whether the plugin should automatically e.g. decrease the similarity-level until there are more artists in the queue?
i'm really not sure what the appropriate course of action would be.

maybe one thing that would help is to make a few of the settings more easily accessible, so people don't have to navigate through the settings menu to e.g. change the similarity-limit. (i was actually thinking about implementing a good way to get to plugin settings directly from within the plugin-widget for a while now, still not sure what would be best.)

Yes : a "hole" is an artist not connected to any (local) other artist by lastfm similarity (if you fall in the hole, you can't escape) ; a "bi-hole" is, in my mind, when only two artists are connected (if you fall in one of them, you only switch between those two artists).

ok, makes sense. we can call it that from now on :)

I put the similarity-limit to 20%, but it's not less enough.

i tested the queuemode using 5% as limit, but i guess it could be raised a bit.

In my local library I've got a lot of artists with the same (local or lastfm) Radiohead genre, but they never appear. It seems genre doesn't affect the similarity drop (I mean : may be genre affect the choice in the similarity drop, but the drop is always taken in the similarity artist but it could be taken in the similarity genre).

hm, i think we should clarify what we're talking about when referring to genres in lastfm. as far as i can see there's only tags, which are very messy (not even sure they would be usable for creating "similar"-playlists).

with genre-stuff i mostly referred to local genre-settings.