Replies: 2 comments 8 replies
-
|
The reason for the change is that Maloja can additionally store the actual amount of time listened to the track alongside the scrobble. In order to get this data MS needs to wait until the track is changed (or finished) to know how long it was listened to. What is your usecase for wanting the it to scrobble as soon as the threshold is reached? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Interesting, I had seen that field in Maloja but always thought it was meant to store the total length of the track, not then time spent listening to it during that scrobble. With Multi-Scrobbler 0.4.8, I had a 99.99% success rate (= songs that I listened fully that ended up in Maloja). Since I moved to 0.8.8, I feel it's more of a 97%, and I kind of assumed that there was a link between the two, but maybe my intuition is wrong. One scenario that feels problematic is the following :
In this scenario, it feels that the scrobble is not sent to Maloja at all, in 0.8.8. (or at least, not each time) I will run more tests and give you a reproduction scenario. Thanks for Multi-Scrobbler, I love it! |
Beta Was this translation helpful? Give feedback.
8 replies
-
|
It just happened. I listened to the first part of a song this morning around 9:19, then I listened to the second half around 12:09. The song is 4:37 in total. It was never scrobbled to Maloja (name of the song : The song that came before ( Here are the logs in between : I have no clue what's happening, even after looking at the logs :-( |
Beta Was this translation helpful? Give feedback.
-
|
I see that you commited some improvements to logging. I'll deploy all these commits locally and come back to you next time this happens with even better logs. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for the radio silence : I was on holiday for three weeks. The problem happened numerous times (a good 30-40 times). I'm not entirely sure, but it seems to be each time that I take a "break" in the middle of a song. Here is an exemple of what one of those occurences look like : The song "Nightwish - The Pharaoh Sails To Orion - Live" was not scrobbled here --> Any clue what's going on ? Thanks in advance! |
Beta Was this translation helpful? Give feedback.
-
|
HI @Fratt , sorry for all the dropped tracks. Can you try the docker image |
Beta Was this translation helpful? Give feedback.
-
|
Please, don't be sorry! I'm super grateful for Multi-Scrobbler and all the hours you're spending maintaining it. I'll deploy |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I recently updated from Multi-Scrobbler 0.4.8 to 0.8.8.
A difference I noticed is that in version 0.4.8, it used to send the scrobbles to the clients as soon as the threshold was reached (with the default value, it was about 60 seconds after playback began).
I noticed that in version 0.8.8, it was waiting for the song to be entirely over to send the scrobbler to the client, even if the threshold was reached minutes before that.
Is there a setting to revert to the old behavior ? (and immediately send the scrobbler further as soon as the threshold is reached)
Thanks a lot!
PS : Here is my config:
config.json
maloja.json
spotify.json
Beta Was this translation helpful? Give feedback.
All reactions