Roon worked beautifully up until I added some more lossless/mp3 tracks to the library and moved the whole library to the NAS.
Now whenever the connection to the NAS is dropped (at night the wifi is scheduled to go down, tin foil hat and all) or maybe after the access to files is restored, ROON core is working normally and you can play files from there while it’s indexing but the clients don’t - either “looking for core” is displayed or all sound outputs are absent (so still cannot play).
In many cases I would start the music on core but it would stop after a couple of tracks.
P.S.
When in start indexing files it would display the number of tracks “scanned” that is much higher than “added”. Any clues?
I’m aware of general wifi instability issue but a)it used to work perfectly b) re-indexing would take a long time on ethernet too, is there a way to force roon not to update the catalogue so often? Maybe I should add another folder with smaller amount of files and add new to it, leaving the existing once w/out changes? would that help?
Bill_Janssen
(Wigwam wool socks now on asymmetrical isolation feet!)
2
Roon Core famously has trouble with external drives hosted on a NAS. Something to do with change detection? But this sounds like a problem with the MacBook Pro, to me. The NAS wouldn’t cause the Core to lose the audio endpoints. What version of macOS are you running on that MBP?
I will check the OS version when I get home thanks (never VPNed into my home network from outside and it’s not configured for outside access)
Yet the endpoints were never down before adding the bulk of the tracks on NAS (maybe a coincidence). Would I get fewer NAS problems if like described I would keep the “recent” folder on the machine where Core is running and the unchanging bulk of tracks would be on NAS?
Bill_Janssen
(Wigwam wool socks now on asymmetrical isolation feet!)
4
Sure, sounds like a plan. I think the real issue with the NAS is that it doesn’t necessarily notify external mounts when something changes on disk. So it can take a while for new or changed files to be noticed by Roon. Not a huge deal.
I imagine someone from Roon @support will drop in eventually to help you figure this out.