I’m getting duplicates in my listening history. I just signed up for the trial yesterday and I am evaluating Roon.
Occasionally a track that I played once will show twice in the “History” section. This seems to happen if the track is paused. For example the track is logged with 40%, and then shortly after with 65%. It shows incorrectly as 2 plays in the album view as well. I scrobble to LastFM and also see the duplicates there.
This has happened 7 or 8 times for me already, even though I just started using Roon yesterday. It happens when listening via Arc and the standard Roon app.
Listening history is important to me as I like to build smart playlists around this. Let me know if you need any more details.
Describe your network setup
Synology Router 6600AX Router. No extenders.
I use Tailscale for connecting Arc when I’m away from home. Roon server is running on Mac Mini
Yes, it’s a known issue that I and other users had highlighted. It seems that there is an ongoing ticket, but there have been no updates for over a year. It’s one of the most annoying bugs for me as it directly distorts the track count and, indirectly, a whole series of statistics (e.g. “most played”, the top artist/top album section on the home page…)
You can read these 2 discussions
Thanks Menzies, enjoying Roon so far!
No, they are still there unfortunately. If I scroll back through my History I can see all the duplicates are still there
Oh, I see, thanks for sharing those threads. One thing I didn’t realise is you can delete from the History, so at least I can fix it up!
I wonder if anyone can write a script to delete the duplicates. Does Roon have an API?
It seems beyond ridiculous that this hasn’t been fixed yet
There is Roon API and it is used to create extensions but not for this kind of stuff. You can check it out here
Yes, this is very frustrating but I guess it is not easy to solve. There hasn’t been any more news about it, but maybe with this thread the Roon staff can give an update (if there is one…)
Yes, this behavior is something that the team is aware of and there’s an existing ticket in for it. I see that it’s been a while since the ticket was put in, so I’ll check with the team to see if there’s been any updates to this.
Please note that generally speaking, we are unable to provide timelines of when tickets will make their way through the queue, but I will note your interest in the ticket with the team. Thanks!
