Closed RobFog closed 11 years ago
Hello. Thanks for pointing this out. I expect this is all down to having the scrobble point set to 100%. Unfortunately as I don't set it to that value myself it doesn't really get tested by anyone 'in house'. I'll have a look into this and make sure we're doing the right thing. I suspect there is a timing issue and we're accidentally scrobbling the next track that gets skipped to instead of the previous one, or something like that.
Thanks a lot for looking into this. :) Let me know if I can give more information.
I suppose https://github.com/lastfm/lastfm-desktop/commit/bfcae92faee395a0e1a6203e55b3f53c0ceaef0c (and perhaps the following commit: https://github.com/lastfm/lastfm-desktop/commit/a24abc23104f92a92aa3a0da3a677758b267b38e) addresses this issue? :)
Ah, yes. This is out as beta in version 2.1.34. Sorry, I forgot to ask you to check if it's fixed all your issues. Should be doing a full release very soon.
Not to worry, I would give a new release a try.
Good job. 2.1.35 seems to work well. :)
I recently updated to the newer app and I have been forced to revert to the ancient version because the new one fails pretty badly at its number one feature: scrobbling.
I've set Last.fm.app to only scrobble when a track has been played in its entirety (100%). The outcome is pretty erratic:
I've been unable to find any recurring pattern in the way the app scrobbles/misbehaves. Some thoughts:
I'm attaching a screenshot of iTunes with tracks sorted by "last played" (red boxes indicate tracks which haven't been scrobbled) and a screenshot from my online Last.fm profile for comparison - "erratic" is the word. The scrobbles are from iTunes unless otherwise specified.
Please let me know if there's more information I can contribute.