Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Ethernet Cable
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Naim ndx2 via ethernet roon transport protocol
Description Of Issue
I guess this happened after restoring roon from a roon-backup. The previous core was running on macOS. Now I switched to windows. The Music is stored on a synology NAS (there was also a change because the HDD was full, data was rsync’ed to a larger disk on another NAS).
Now I see some (not all) albums two times. When I try to play the same song from each occurrence, one will be played. The other is skipped with the short notice “playback was interrupted because the track failed to load”. I checked for differences and can spot that there are different play counts and the ‘added’ date differs. And the ‘Like’ can only be seen on one of them. Looks like there are now two albums pointing to the same files. I wouldn’t care so much when both would be played. But I can never be sure if I choose the right tracks from the playable album.
To illustrate that these are in fact the same files which are accessed I add screen shots from the file info of one affected song.
Anything I can do to clean this up without loosing the stats ?
Is this a known problem ? (havn’t found exactly my problem)
Probably used Time Machine to backup? As Roon has warned many times in this forum, only Roon backups are safe…
If you can go back to your macOs machine (temporarily) and run a Roon backup and then restore on your new machine, using Roon restore, then you problems will probably be straightened out.
Of course I used a roon backup to restore the roon setup.
No TimeMachine was in use on that system and not sure how to restore a timemachine backup on windows
It sure sounds like your database has been corrupted somehow. Did you happen to move the music to a new location on 18May? If Roon is running when a watched folder is being changed, files can get corrupted.
Do you have an idea of how many files have this problem?
Have to tried to identify any of these files using Focus? For example, in Tracks View, Select Focus>Inspector>Corrupt.
If you use Album view there are more selections, to look for duplicates, corrupt files, etc.
Short of finding a corrupt aspect of the database, removing the offending file(s), and then adding them back, I’m out of ideas.
Another user, or Roon Support may have better solutions.
Scott, you are likely right. There were moments when I moved files while Roon was running and ‘watching’ for new files.
Yes, there are a lot of duplicates (2400 from 25000 Albums). Many of them are expected. Different formats etc… The funny thing is that my example I have given above does not show up as duplicate. But there are other duplicated albums which show up and have the same problem as explained. As this is a large library it is not so easy to handle. I am not able to identify the real problematic albums… yet. And there are only 4 corrupted albums, unrelated.
this is a kind request for feedback.
I would like to know how I do get out of my problem without loosing my playlists and statistics.
Even when I try to remove such a problematic album completely from the NAS/Disks, it still shows up twice after multipple forced rescans, roon restarts, system restarts.
will there be any feedback to my support request?
I am still in the unfortunate situation that some albums are shown twice but only one of them will get played by roon.
A way to repair the roon databes would be great. Or at least a way to reread my Music from the NAS without losing the metadata and my playlists.
In case you won’t try to fix this please let me know.
Sorry for the delay, @Axel_Klatt. It looks like this made it’s way out of my normal queue, but your tag put it back in. Apologies here! I’m following up with the QA team and will get back to you ASAP on this. Apologies again.
The QA team has been trying to reproduce this in our QA labs but so far we’ve not been able to reproduce successfully. We are hoping you can do the following for this album:
Make a copy of this album outside of your watched folder
In Roon, delete this album and any duplicates
Restart Roon
Move the copy that you made into the watched folder so it imports newly
Do you see the same duplicates issue occur on this re-import?
Okay. I followed your plan.
But the zombie album stays while the working-one goes.
The details:
In Roon, delete this album and any duplicates
I deleted it from the NAS. Roon recognized this quite fast. In settings → library → ‘clean up library’ twenty deleted files are showing up.
Restart Roon
After the restart the playable album has gone but the unplayable album is still there.
Move the copy that you made into the watched folder so it imports newly
Now the album appears again twice: One working version (the one I just added in the Music folder on the RoonCore System) and the non-working pointing to the old NAS location stays.
Looks like there is dead data in the database which will not get deleted.
Even when I put the album back to the former location, the location where the file info of the non-working album is pointing to, the zombie album does not go away.
In my imagination editing the database by hand would be something to do. But as I see this is in a roon proprietary format… You may know better. I can offer a teamviewer session to my roon core windows machine if this would help to diagnose it better.
What happens if you try to delete the ghost album in Roon? Can you give this a try and, assuming it fails, let me know the time that you try to do this? I’ll have the team take a look at the diagnostics report during this time.
Before doing this, you might want to make an extra copy of the files outside of your watched folder, just to be safe.
All library counts are zero now.
