You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reporting playback to my Subsonic (Navidrome) server randomly doesn’t work; oftentimes the songs at the beginning of a queue or album won’t scrobble, then most of those after will.
I feel like adding a check to see if the server has received the message and resending it if necessary would solve this. I tried diving into the code a while ago to fix scrobling logic (see here: #106 (comment)), but I didn’t end up finding the time to brush up on my skills to resolve this.
I do think that a fix for this would also solve the previous issue;
Try to scrobble a song
Check if it was received
If yes > good
If no > cache it with timestamp and retry the next time a scrobble goes through successfully
If I do find the time I’ll try to look at it again myself, but I don’t think that’ll happen tbh.
The text was updated successfully, but these errors were encountered:
Scribble cache is already implemented. When server is not reachable the scrobble gets saved. All cached scrobbles get uploaded when the server is reachable.
I reworked the scrobble behaviour in e4e864c and f427673.
This is fantastic! Are the scrobbles timestamped for the moment they were originally played as described here? That’s the last thing stopping me from using Amperfy full time. I’d test it out myself, but the update isn’t available yet on TestFlight.
Reporting playback to my Subsonic (Navidrome) server randomly doesn’t work; oftentimes the songs at the beginning of a queue or album won’t scrobble, then most of those after will.
I feel like adding a check to see if the server has received the message and resending it if necessary would solve this. I tried diving into the code a while ago to fix scrobling logic (see here: #106 (comment)), but I didn’t end up finding the time to brush up on my skills to resolve this.
I do think that a fix for this would also solve the previous issue;
If I do find the time I’ll try to look at it again myself, but I don’t think that’ll happen tbh.
The text was updated successfully, but these errors were encountered: