Starting Roon on my Core today (with the same problem being shown on my Remote), 27 from the first 28 albums in my “overview” view now have only 1 track. They’re being displayed as the “first” 27/28 albums as something’s - according to Roon - changed, which is actually not the case.
The only thing I’ve done recently is to add the very first album (Underworld) - which consists of 2 tracks.
These “single” tracks belong to albums - and have always (previously) belonged to albums - and have always previously been shown as belonging to albums.
The Metadata has not been changed - not touched at all.
The files have not been touched.
The file / album structure has not been touched.
The NAS that they’re stored on has not been touched.
See the first 2 screenshots below which show “overview” : the first album (Underworld) was added on Friday, the following 27 albums (up to & including “Engineers”) have not been touched at all.
What is interesting is that Roon “says” that the albums were added on the 17th September, which is most definitely not the case.
Using edit / grouping, I can fix the albums, but quite frankly, why should I have to fix something that wasn’t broken ?
The amount of recent issues, post v1.1/55, for me, is now getting beyond the joke. Robustness / stability / reliability seems to have gone completely out of the window. What is going on ?
I’ve run into simular problems. These kind of problems should be (and probably are) high on the prioritylist. Trusting the software to keep your files and library edits safe is most important for us to be able to truly enjoy Roon.
Yeah, again, sorry for all the trouble here @rolski – as you know the team spent multiple days last week trying to reproduce the issues you’ve described. Unfortunately, we are still gathering information and looking into what makes your setup unique, and why it’s been so much less stable than other users running Windows 10.
I understand how frustrating this is and we’ll continue working through this issues and the connection issues until we get this all resolved.
In this case, it seems like Roon is considering these files as “new” – Roon tracks your files on disk, and usually can recognize a file even if it’s moved. We are aware of causes where Roon can consider a file to be new if the file has been edited on disk in multiple ways at once, like changing the file name, tags, and path.
We have seen a handful of cases where this happens without user involvement, but most have been tracked to circumstances different than yours (such as a bug in Build 16 that was only exposed when updating directly to Build 51). Since you haven’t touched the files here, we’ll need to get some more information about what’s going on here, so I’ll follow up via PM.
Sorry again for the trouble @rolski – you’ve been extremely patient. We’ll be in touch with some info for tracking this library issue separately from the connection issues.
