Discussed in #394
Originally posted by jacksaturn November 10, 2025
Is there a curl command that a user can send to MS telling it to clear whatever is currently "Now Playing"?
My scenario:
When the final track of a playlist or album ends, my script sends a "single" scrobble for that final track to MS, then my script shuts down until I manually start another song playing.
I noticed that the track is still hanging out as "Now Playing" on MS for a few minutes after the fact, so I timed it with a stopwatch and watched the logs. My best guess was that it would be the track's length — taken from the "duration" field in the scrobble — plus a 60-second cool-down. But the time worked out to 5:30 from the moment the track was scrobbled until it was completely cleared in the MS UI (and thus on Last.fm and Listenbrainz).
- MS displays Now Playing longer than tracks are played for, WRT sources that only display now playing (lz/lfm endpoint and sources)
- Downstream Now Playing, on LZ/LFM, is displaying for longer than a track is played for when the track end and another track does not begin immediately
@jacksaturn
Discussed in #394
Originally posted by jacksaturn November 10, 2025
Is there a curl command that a user can send to MS telling it to clear whatever is currently "Now Playing"?
My scenario:
When the final track of a playlist or album ends, my script sends a "single" scrobble for that final track to MS, then my script shuts down until I manually start another song playing.
I noticed that the track is still hanging out as "Now Playing" on MS for a few minutes after the fact, so I timed it with a stopwatch and watched the logs. My best guess was that it would be the track's length — taken from the "duration" field in the scrobble — plus a 60-second cool-down. But the time worked out to 5:30 from the moment the track was scrobbled until it was completely cleared in the MS UI (and thus on Last.fm and Listenbrainz).
@jacksaturn