Figure out why lastfm/pylast drops now playing data too early #1

Closed
opened 2024-04-18 13:40:32 +00:00 by Firepup650 · 3 comments
Owner

I currently only have a band-aid on this fix, which ignores if the track is missing once. There are still false positives on the track not playing though.

I currently only have a band-aid on this fix, which ignores if the track is missing once. There are still false positives on the track not playing though.
Firepup650 added the
Kind/Bug
Priority
Medium
labels 2024-04-18 13:40:32 +00:00
Author
Owner
The band-aid: https://git.h.hackclub.app/Firepup650/FireBot/src/branch/master/timers.py#L96-L98
Author
Owner

Too lazy to deal with this, current solution is to just buffer if we know it's working, one notch per 10 seconds, 100s to max out the buffer, which is 10s long at max.

Too lazy to deal with this, current solution is to just buffer if we know it's working, one notch per 10 seconds, 100s to max out the buffer, which is 10s long at max.
Author
Owner

Also this might not be lastfm's fault, some stuff I've read suggests it might be Spotify's fault.

Also this might not be lastfm's fault, some stuff I've read suggests it might be Spotify's fault.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Firepup650/FireBot#1
No description provided.