After downgrading from 2.0 to 1.8, due to speed problems following the guide previously posted within these walls and installed the server and the 1.8 Legacy on the core, I’ve found out the following and strangest of behaviours.
My Roon remote in my iPhone 14 and my Macbook Air work seamlessly… but the Roon app on the core displays the infamous message of database incompatibility … It means the remotes and my Node are communicating with my core, but the Roon app on the iMac will display the aforementioned message.
How is this possible? (I have no problem with losing the database and starting from scratch – I don’t have a 2.0 backup), so why is the program not giving me the option, as my iPhone and MacBook did, to start all over again? What am I doing wrong?
On the plus side… the downgrade really worked… I mean the speed problems of communication between the remotes and the core are solved, just this thing with the software…
i am afraid this is the expected behavior; starting with Roon 2.0.3, resulting backups are no longer compatible with 1.8 Legacy version (Roon 2.0.3 and ARC 1.0.4 are live!)
I am aware of the database issue and I’m okay with starting from scratch since all my music is stored in an external hard drive that will take the core three hours to index–no issues with this. I’m talking about being unable to open roon 1.8 core program so it can start indexing…
Can you give us a little more detail on what precisely you have done and what your setup is now? You said you have: “installed the server and the 1.8 Legacy on the core”.
Have you installed both the Roon Server and Roon packages on your iMac, or just installed the “all-in-one” Roon package for MacOS using the link in the 1.8 <-> 2.0 Migration FAQ?
Can you post a screenshot of the iMac Roon’s error message?