I’ve noticed some strange behavior with this build. Some songs that have been played in their entirety show up as 0% in the history. These are songs that were played after the update: the first play showed the correct percentage, but all subsequent plays are always at 0%.
Yes, it’s new. I’m constantly monitoring the history section due to the ongoing issue of duplicate playbacks. I’m deleting all duplicate playbacks and ghosting those that don’t have the correct playback percentage.
This issue wasn’t there before and I believe it may be related to the change to avoid duplications on Lastfm.
Hi @Daniele_Piancastelli, thanks for flagging this! We’re investigating the issue.
I’m seeing the same, one odd thing is I have a large group all 0% which appear to be songs picked by roon radio after my album ended.
Were you playing the tracks over ARC? I’m not home at the moment, but my history from using ARC this morning looks fine (Just trying to help narrow down the relevant use cases)
Hope you get to the bottom of it
Same here, latest build…Happening intermittently, but, in one major case this morning, I played MD112, or track 2, on Radiohead’s MINIDISC [Hacked] collection.
Had to lock in for work, figured it was a good chance to bump Radiohead in my artist play stats, so, I threw it on and got to work.
The track is 1H 10M 27S.
It played all the way through, the play counter clocked it, but the percentage played said 0% and I got no “credit” for having listened. What the heck, Roon!
Speaking of the play counter, if you’re on the latest build, is anyone else noticing that pausing a song and coming back to it after a few minutes is registering double plays? Let me know, please…thanks!
Are you on Build 1660 from today? This was supposed to be fixed:
Latest build seems to have fixed the bug.
This is an old bug that has been reported for years and has had a ticket opened but is still unresolved:
Hi Daniele, thank you for the update!
EDIT: It’s funny, @Daniele_Piancastelli , I’ve been using Roon since 2019, but, I’d never really noticed that issue about pause affecting play count until about a week or so ago. How odd!
Hope it gets fixed soon.
This change to avoid duplicates on Last.fm appears to have improved the issue of duplicate play counts in the history section, especially for playbacks from ARC, where it frequently created more than one entry for the same song.
However, it hasn’t completely solved the problem because, whether a song being played is moved from one zone to another or if changes are made with MUSE, it creates a history entry (play count +1) with a partial play percentage. Unlike before, it doesn’t create additional entries with partial percentages if during the same playback period, the song is moved again or a further change is made in MUSE.
I hope this is a first step towards permanently fixing the bug