-
Notifications
You must be signed in to change notification settings - Fork 19
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
bug: (YTM) Songs skipped 0-9 seconds after their scrobble cause following song to be discarded #226
Comments
The scrobble is being rejected because MS is sending the scrobble with the same timestamp as an existing scrobble in Maloja.
Maloja doesn't allow scrobbles with the same timestamps. This is due to defensive design in MS and (mostly) as expected -- MS sets the timestamp for a discovered scrobble as 1 second past the current minute. The assumption is that you aren't listening to many multiple songs per minute because tracks shouldn't be that short. If MS tries to scrobble multiple tracks in that minute then the scrobble client will reject all but the first one. It's not great design but it does help with preventing false positives a bit...definitely something I need to improve so MS just drops the play instead of trying to scrobble it. |
@xathon The newest
Please try it out and let me know how it works for you. Note that this is a newer image than then one from #228 so if you are already running it please re-pull for the newest changes. |
Fixed in v0.9.0 |
Please check existing knowledge before opening an issue
Describe the Bug
In the attached log example, using youtube music, I skipped the song "And Plague Flowers the Kaleidoscope" a few seconds after it got scrobbled. This caused the following song "Invincible" to be scrobbled, but then rejected by Maloja. I'm not entirely certain whether that's something that Multiscrobbler can (or should) control, but maybe someone here has some better insight.
(Note: the scrobble of Army of the Night at 23:50:29 is a different issue, I'm still collecting data on that, but will raise another issue)
Platform
Docker
Versions
Logs
Additional Context
No response
The text was updated successfully, but these errors were encountered: