getmusicbee.com

Support => Questions => Topic started by: Steven on January 02, 2015, 05:57:49 PM

Title: Scrobbling issues with Last.fm
Post by: Steven on January 02, 2015, 05:57:49 PM
The status of the last.fm scrobbling service is located at: http://status.last.fm/

If you are experiencing problems scrobbling to last.fm there is little point in posting to the MusicBee forum and expecting help.

Its entirely up to last.fm whether it accepts a scobble or not. MusicBee simply reflects any error returned by last.fm. If there is an error where the last.fm guidance says to retry then MusicBee will defer and retry to scrobble on the next restart.
The status of whether a track is scrobbled or defered with any error code returned by last.fm is logged in Help/ Support/ View Scrobble Log. If its error code 16, a number of users have reported that the track will be scrobbled twice. However the last.fm guidance states the track should be rescrobbled so i wont change that.

I believe the reason some other applications work when MusicBee doesnt is because they are using the old version of the API. It can also be the case sometimes where MusicBee is sucessful and other applications are not so it works both ways.

I have approached last.fm to get a application id so MusicBee can use the old scrobbling API which seems many times more reliable the new API they replaced it with. Unfortunately they have not responded so there isnt much i can do about this


edit:
around Sep/Oct 2017 last.fm plan to stop support for an old version of the last.fm scrobbling API. That means that anyone using versions before MusicBee v2.3 will need to upgrade to a more recent MusicBee version which is available from the downloads page.