Play count reset issue for a favorite track on Roon Server (ref#V1U0FU)

What’s happening?

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

Track play count reset from over 400 to 2. Where is this stored so I can restore it?

I know it’s not the end of the world but for some strange reason my absolute favorite track (based on times played) reset from over 400 plays to 2! Anyway can I get my play count back to where it was? I wanted to throw myself a party once it hit 500 but sadly I can’t now. I’ve tried to restore a few Roon backups but the count still remains at 2. Is there a database somewhere that I can restore from? Some hidden file(s)? I backup my machine pretty regularly so I can restore individual files or my entire Mac

Roon Server version 2.48(1517) running on Mac OS Catalina

Describe your network setup

Eero Mesh Network Cisco Switch

I use TimeMachine for backups along with Roon Backups. Perhaps if there is a specific file/folder that contains this info I could just restore that file?

Hey @Mark_Allen,

Thanks for sharing your report - sorry to hear about your issue!

Can you provide more details around this? Generall speaking, we advise against running TimeMachine or third party backup software along side Roons own backup system. Roon’s core database is constantly changing in the background — even when you’re not actively using it. Time Machine might try to back it up while it’s being written to, which can result in a corrupted or incomplete backup.

Overall, Time Machine backs up files. Roon backups need to handle a live database — so Time Machine might look like it’s backing things up, but you can’t rely on those to restore your library safely.

To confirm, have you reviewed the different versions available for the song in question? If you confirm it’s the right version, can you also review the 393 different recordings, to ensure Roon hasn’t accidentally mis-identified the track?

Perhaps you can also review your play history, and see if you can find the specific track prior to the 2 recent plays you have recorded - and double-check the specific track version there as well.

Certainly let us know the results!

Ok I’ll check this when I’m home. I primarily use the Roonbackup and time machine for everything else. I’m not following about the history. The album is a local album not from Qobuz etc. I normally just play the whole thing as you can tell by the number of plays. It’s just the first track that’s out of whack. Is there an easy way to filter the history search? Anyway I’ll try again when I’m at home.

I think I’ve figured it out or at least a workaround. The album/track is HiRes(Alac 192kHz). I moved this album to its own Folder called “HiRes” along with other HiRes albums. All I did is copy the files from the default “Music Folder” I then disabled the Music Folder and enabled the HiRes folder. All tracks looked fine except for the first track with it’s count of 2. When I disabled/removed the HiRes folder and enabled the Music Folder all track counts are back to normal.

It still makes no sense why this one track reset when I just copied them to a new folder.

Hi @Mark_Allen,
Great to hear you found a solution that works for you! Enabling the new folder likely prompted Roon to treat the files as entirely new, which might explain why things started working properly. Take a few days to test things out and make sure everything’s behaving as expected. If all looks good, feel free to mark the thread as solved — and of course, let us know if anything else comes up!

1 Like

Ok. I’ll play with it some. Still odd that only that one file is having an issue.

Hi @Mark_Allen,
I agree that it’s very odd that only one track seems to be affected. It’s not common to see such isolated behavior, which suggests there might be a unique issue with that specific file or how it’s being handled by Roon.

We’ll be on the lookout for your response on how everything is working.

1 Like

Let’s go ahead and close this support issue. I’ll just deal with the one odd track. It’ll just be a mystery…

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.