Except it’s not. That is the mount point to my NAS (via the OS). If I use Roon to create the mount point I get drops during playback. This is not surprising as most software (eg. Kodi) works better when the mount point is created on the OS rather than in the software.
It’s locally attached as far as Roon is aware, because you’ve mounted it… And if you get dropouts when using it as network attached storage, then something else is going on - and it’s probably not in Roon…
If I mount the share at the Roon level I get dropouts. If I mount it at the OS level (which is how it should be done anyway especially on Linux) then I do NOT get dropouts so clearly the issue is Roon.
I updated to DSM 7 a month ago, but auto watched folders worked perfectly for a few weeks. It only broke since the latest ROON updates over the last week, which came 3 times since they had so many bugs. This is another one I am sure… Needs attention from the devs.
You should always mount directly at the OS level, fundamentally this is much smoother, faster and more stable.
The equivalent in windows would be making a share such as C:\Music and then mapping it as a network drive and adding it as an SMB share for a local application. You can see the stupidity in that easier.
I have the same problem since 933 update.
And also I am annoyed by the fact that local mounted folders are not automatically watched.
The mount process in Roon is not the best one.
At least, the possibility to insert additional parameters could be deployed.
I think this a change that must be made as soon as possible.
Update: Worked great for 6 weeks, now having issues again with scanning and adding local music. Seems temperamental. This really is extremely frustrating for NAS users. Perhaps ROON could code in an optional ‘auto scan’ feature u can schedule every 1 minute or something like that on the local file system folder itself. That would solve it for the loads of NAS customers with these issues.