noris
October 17, 2019, 5:51pm
23
Hi @ar9 ,
As I noted in my linked thread above, this has been a limitation that we are well aware of and have done what is possible to mitigate it as mentioned by our CTO and Product Manager in the following threads:
This made it all make sense to me. I know what’s happening.
Roon knows that it can’t trust NAS’s to report on filesystem events in all cases–and there’s no way for us to detect whether events are coming or not. NAS’s just silently report a subset of events, or none at all. So “real time watching” isn’t real time all the time.
We did some research and found that just about every piece of software that attempts to do “real time watching” on NAS’s eventually runs into this limitation, and supple…
Hey @Semaxx @Gabriel @Patatorz – as a general rule, Windows picks up changes more reliably than Linux or Mac, but all of this really comes down to the NAS consistently reporting changes back to the machine running the Core. For the most part, we’ve found that most NAS drives do not do this reliably, particularly when the changes don’t involve creating or modifying folders.
We’ve recently added the option to customize how often Roon manually rescans your NAS for changes, which is a workaround, o…
This is a symptom of how real-time file watching works on Windows, vs on Linux or OSX.
Remember that SMB is a Microsoft technology–it’s a first class part of the Windows ecosystem in a way that it isn’t on Linux and OS X. One result is that Windows tends to be a bit better at picking up changes on SMB shares in real time.
We’ve made some improvements to Roon’s filesystem watching behavior over the years, many of which were released with Roon 1.3 a couple of months ago, but ultimately when the …
I wish I had better news for you here but at the end of the day Roon relies on the NAS share to report file changes reliably and if the NAS is not performing this function as expected, Roon won’t be able to automatically see the new content.