@xxx I stumbled over your posts when searching the forum for other users experiences with the „There was an issue loading you database“ message and problems with the Roon database.
An interesting read which unfortunately confirms my existing concerns. I have experienced several
problems with the database about a year ago but was eventually able to fix it by restoring an older
backup, which on the hand wiped out most of my tags and other metadata I had edited and curated
After a long period of stable performance and enjoyment (meanwhile managed to rebuild most of the metadata editions I lost before) I decided yesterday to update Roon to 1.8. and that inevitably led to the catastrophe because my database crashed again after a restart of the Core (maybe due to underlying and so far undiscovered problems in the database triggering a crash after being updated to 1.8.?)
However, all my carefully curated metadata is again at risk of being wiped out again because it - other than the library of digital albums - cannot be backed up and restored afterwards to a new and clean library. Moreover, I understand that there is also a fatal risk of corruption included in my backups already which also might cause a total loss if I would be required to start with a new database or at least would be forced to restore an very early version of the backups.
While many users may not care about this as long as they can quickly reimport their albums and start
again with a new clean database, I have a lot more to loose with all the effort I put in curating and
personalize my existing database, which for me is an integral part if not the essence of the Roon user
Against this background, I fully agree that raising user’s awareness of latent corruptions in the
database - and even more important - potential corruption spreading among the backup files is very
important and should be treated as one of the top priorities for the Roon team instead of considering
further Ul changes. Some users have spent plenty of time „working" with Roon’s abilities to curate thein
libraries and the musical works they love and adore, so Roon should indeed provide a proper solution for them to safe, export and/or import their personal settings and curated metadata (e.g. tags,
playlists, …) and develope effective safeguard against latent corruption of the program’s database. And of course, scheduling regularly and possibly automated checks of the database integrity and warnings to prevent user from spreading the corruption across all further backups would be very helpful and greatly appreciated.