Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AcceptedCount and Ignored always 0 even though some tracks failed to scrobble. #92

Open
SHOEGAZEssb opened this issue Sep 11, 2016 · 7 comments

Comments

@SHOEGAZEssb
Copy link
Contributor

I scrobble a lot of tracks at the same time.
Some tracks fail to scrobble, but in the response the AcceptedCount is always 0 aswell as the Ignored list. Is this a bug? I can't seem to find out why some tracks failed to scrobble.

@SHOEGAZEssb
Copy link
Contributor Author

Also I just got a "Success" response, but around 2000 tracks failed to scrobble (out of 50000)

@rikkit
Copy link
Member

rikkit commented Oct 3, 2016

Hi @coczero , very sorry for the slow reply. I am currently on holiday so haven't checked GitHub recently.

The Success and AcceptedCount properties are wired up to the JSON response that Last.fm sends. In the past the AcceptedCount property was available in the JSON. I know Last.fm has been changing its JSON output somewhat recently, so maybe this info isn't there anymore. Will need some investigation.

Can you tell me how frequently you tried to scrobble? Maybe you're hitting the upper threshold on scrobbles, documented here: https://github.com/inflatablefriends/lastfm/blob/master/doc/scrobbling.md#there-is-a-limit-on-how-many-scrobbles-may-be-sent-in-each-day .

There must be at least 30 seconds in between each scrobble. This means you may scrobble at most (24 * 60 * 60) / 30 = 2880 tracks in one day. If this limit is reached then the scrobbles will be cached if it's enabled.

It used to be that scrobbles that were ignored by this mechanism were reported as ignored, perhaps that has changed as well? 😕

@SHOEGAZEssb
Copy link
Contributor Author

Hi,

I am probably way over the upper threshold of the scrobbles, but that value seems to be unpredictable at best. I normally have no problem scrobbling around 10000 tracks within a minute. So maybe the threshold has changed too. The problem is just how can we tell if a scrobble has been rejected and what was the reason?

@rikkit
Copy link
Member

rikkit commented Oct 11, 2016

I haven't had a chance to investigate this yet.

Out of curiosity though why are you scrobbling 10,000 tracks? Stress testing?

@SHOEGAZEssb
Copy link
Contributor Author

Basically, I parse the iTunes library to allow people to import their database to a new last.fm account.

@rikkit
Copy link
Member

rikkit commented Aug 7, 2017

@coczero could it be this? https://github.com/inflatablefriends/lastfm/blob/master/doc/scrobbling.md#scrobbles-have-an-age-limit

There should be better reporting on this either way.

@SHOEGAZEssb
Copy link
Contributor Author

No, the scrobbles go through fine. Maybe the api doesnt really give info about this anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants