I'm getting this two or three times a week (and not just after an update to Sonoma), I revert to a previous version of the library, and a few days later I get the same message again, and have to do the same thing, yet again - what's going on Apple?
MacBook Pro 14″, macOS 14.1
I think I've covered all the bases here, noting the instructions are largely focussed on Windows not MacOS, I've just had the same issues yet again.
Recovered using last library, renamed, start Music today and the same situation - could it be that I need to delete preference files (or similar), to stop the system regressing back to something that it is remembering?
Yes, using option-start music to select the library file that I've taken from the "previous libraries" folder, renamed "music library", and then copied back into the folder where the library file is stored. This only started when we were into the 2nd or 3rd update to Sonoma.
The library and media are stored on a NAS, I'm going to try creating another folder and perhaps copy the files across and see whether that helps make the system "forget" the problem
I've seen threads on here where is says that Music (and iTunes before that), preferred both the Library and Media to be located in the same place, and I've been running this setup for many years it would appear, based on timing to be linked to something that happened in Sonoma. I've added the .itl file extension to the Library to see what happens, and will try moving it to a new folder in the NAS, in case there's something weird happening
Yes, in general things work better, particularly when moving the library from one place to another, if everything is in the standard layout of a library folder that contains the database and the associated media folder. That said, iTunes does have some bad history with NAS. Nothing against it for storing backups, but it may not be the best location for an active library. That's not to say it shouldn't work, just that it isn't necessarily a situation Apple explicitly test out when they are making changes to the application.
tt2
Oops., wrong link. turingtest2 has the correct one.
Are you actively using the option-start-Music method to select your restored library file? If not Music may remain connected to a renamed or deleted library database.
tt2
It is possible Music doesn't like having the library stored on the NAS. You may find the library behaves better on local storage.
tt2
Apple Music - Your library cannot be read because it was created by a newer version of music
