'Related performers' vs. 'minimum match score'

[Michael]

Turns out last.fm made an un-announced change in their API.

The 'match' score, which is used when dealing with related performers (using artist.getsimilar from the last.fm API), used to be a value between 0-100.
Now it - suddenly - turns out the match score apparently has changed so a value between 0 and 1 is returned from artist.getsimilar.

As mentioned, last.fm haven't really made any announcements in relation to this..

In AmpJuke the call to artist.getsimilar is used to retrieve and display a number of related performers within your music collection. For more info. about that, see this FAQ-entry: http://www.ampjuke.org/faq.php?q_id=41.

As you might have figured out already, configuring 'Minimum match score' of a value of f.ex. 40 in AmpJuke's related performers section (see previous link), won't be very good if the values returned from last.fm lies between 0 and 1...
...in real life this would have the impact that none of the performers within your music-collection would be related.

In order to deal with the (apparent) change in the 'match' score returned from the last.fm API, adjust the value for 'Minimum match score' in AmpJuke to a factor 100 lower compared to what you had before.
For example, if you have 'Minimum match score' set to a vlue of 55 now, change it to 0.55.
Please click on the link above for details about how to set/change 'Minimum match score' in AmpJuke.

Yes, a note has been made in the discussion forum over at the the last.fm website: http://www.last.fm/group/Last.fm+Web+Se ... 4/_/596304.

I'll update the FAQ in relation to this after releasing the next version of AmpJuke (0.8.2).
If everything goes well, it will happen within the next couple of weeks.

//Michael.