· Hello, I am experiencing an issue with scrobbling to Last.fm from the Roon desktop application. When I start playing a track and then pause it, and later resume playback using the pause/play button, the track is not recorded (scrobbled) in Last.fm. It seems to be skipped entirely. However, if I pause a track and then restart playback using the “Play Now” button instead of resuming, the track is correctly scrobbled. So the issue specifically occurs when resuming a paused track using the play/pause button — those tracks are not being scrobbled. Could you please look into this behavior? Thank you.
Tell us about your home network
· My home network is a simple setup using a single ISP-provided modem/router as the main router. There are no additional routers, mesh systems, managed switches, VLANs, or VPN/firewall customizations in use. My Roon Core runs on a dedicated server, sonic transporter, and is connected via Ethernet. Most of my Roon devices/endpoints are also connected by Ethernet rather than WiFi. All devices are on the same local network/subnet. The network is generally stable, and I am not experiencing broader connectivity issues apart from the Last.fm scrobbling behavior described.
A pause longer than ~5 seconds makes the zone auto-suspend and release the audio device, which fires OnPlayFeedback Stopped and tears down the scrobble session for that track. On resume the position is restored and a fresh “now playing” START is even re-sent, but the scrobble-completion accounting is not restored, so when the track finishes, no DONE/track.scrobble is submitted.
This is some we’ll need to escalate to our development team for further analysis, as it’s clearly repeatable.
We’ll be in touch with more information once our team takes a closer look. Thanks for your patience in the meantime!
We need a little more information to pin this report down.
Does this happen with every Zone in Roon, or is this specific to one Zone? The pathway @benjamin described above occurred with a Cambridge audio endpoint.
Does the endpoint itself disappear as an available Zone before you click Play again?
Are you seeking within the track at all or otherwise engaging with the playback bar when this issue reproduces?
If possible, record a short screen capture video that demonstrates the precise action sequence you’re taking within Roon. Roon has several fallbacks to prevent duplicate scrobbling, and we need to check whether you’re inadvertently triggering any of these anti-duplicate behaviors.
The issue is not specific to my Cambridge Audio endpoint. I can reproduce the same behavior on other Roon Zones as well.
I also tested using different controllers. The issue occurs regardless of whether I use the Roon desktop application or the Roon mobile app to start, pause and resume playback.
When reproducing the issue, I am not seeking within the track and I am not interacting with the playback position bar. The only action performed is pausing playback and later resuming playback using the play/pause control.
The endpoint remains visible in the Zone picker while paused and does not disappear before playback is resumed.310726 opname roon
I will also provide a short screen recording demonstrating the behavior.
· last.fm submission inconsistency. This happens when a track is paused and resumed again. Happens after the last update. Should be: scrobble track when played over 50%.
We’ll need a little more information to take action on this thread.
By “inconsistency,” are you referring to duplicate scrobbles appearing in your
history?
Does this happen in Roon or in ARC?
The only recent changes to scrobbling code in Roon were several releases ago in the late spring; we updated scrobbling logic specifically to prevent Roon from tracking a pause as a scrobble in Last.fm. Pressing Previous or seeking back to the beginning of the track are the only mechanisms by which Roon will scrobble a duplicate play count.
Please share the name of a track that exhibited the behavior you’re describing, or a screenshot of Play History/Last.fm history that demonstrates the problem. We’ll proceed there with next steps or a deeper explanation. Thank you!
When a song plays. let’s say 10%, and I pause it for some time and then resume it, it won’t scrobble. I DO see in lastfm “scrobbling now”.
This is happening in Roon, I don’t use ARC.
No double scrobbles, I don’t use crossfading in this zone.
When writing this message I can even reproduce this problem now. by starting a song, pause it after 10s, and resume it, wait to complete playing the track to the next starts and no submission is done to lastfm.
Could this happening by tightening the memory issue’s you had/have and losing the cache or something?
Please let me know if I can do anything from this side. At the current moment the memory usage is ok and stable.
I now need to replay the song again to make it appear in last.fm, or make sure I restart the track after a break…
The last 3 missing tracks to check this behavior when I wrote this reply:
To Destroy a City - March (Solar Fields)
To Destroy a City - Goodbye, Dear Friend (Dalot)
To Destroy a City - Metaphor (M. Szarejko)
Playing a track from the start and transport to the next after 50% play will scrobble!
I’ve been noticing the same thing lately, when using the Roon desktop app on my Mac: when a track is paused and then resumed, it doesn’t get scrobbled to Last.fm after the track is completed.
According to Last.fm official rules, a track is decided to be successfully scrobbled only when it is longer than 30 seconds and has been played for at least half its duration or for 4 minutes (whichever happens first). [1]
Core Scrobbling Rules
Minimum Length: The song must run for more than 30 seconds. Short intro tracks or hidden skits under half a minute will not count. [1, 2]
Playback Threshold: You must listen to 50% of the track’s total length, or reach 4 full minutes of continuous playback—whichever limit comes first. [1]
Submission Timing: Depending on the client or app plugin you use, the scrobble data is sent to your Last.fm profile either right when the 50% mark is hit or immediately after the track finishes playing completely. [1]
I pause them before hitting the 50% mark, and then resuming again. playing it to the end. at this point the submission fails. (the 2nd point, threshold is met, since it played 100%)
Thanks for the video and additional details. We’re having trouble enabling diagnostic mode for your Roon Server to take a closer look, could you please use the directions found here and send over a set of logs to our File Uploader? Once logs have been uploaded, please let us know so that we can check the server for your files, thanks!
We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.
You have our apologies for the trouble here, and we’ve greatly appreciated your patience as we continue investigating this tricky issue. We’ll be in touch as soon as we can.
