Having your music files on a local network-attached LAN is fine so long as you experience no issues. Meaning that there’s nothing wrong with it per se and many people operate fine with it.
If however you experience network-related issues (dropouts, inter-track pauses/gaps, etc) one of the things people will tell you to do is to get your music topologically closer to your core. On an internal SSD or USB-connected SSD is zero hops. On a NAS connected to the same switch that the core is on is one hop. If you’ve got more than one switch between your core and your NAS that’s 1 hop per switch. Fewer hops is better. Though I was fairly stable for a while with my music on a NAS connected to the same switch, I did have glitches on occasion. One of the things I did to address them was to get an inexpensive SSD enclosure and connect it to my core via USB.
Now my NAS is one layer of backup, and I have sneakernet to a quarterly-ish offsite backup. So I’m better off in a number of regards.
My playback glitches are far less common than previously but I don’t know how much was attributable to getting my files “truly local” or zero hops away from my core. But it was inexpensive in the grand scheme of things.
There are the two different uses. Local in the LAN vs internet streams is one meaning. A local disk attached to the Roon core vs Ethernet-connected storage is the other. Both are valid usage and meaning depends on the context
If you look at the OP’s first post he asked if his NAS was considered “local” and in that context, or really any context, the answer is ‘yes’. After all, he realizes the storage is not directly connected to his Core device.
You made a general statement, and I commented on that:
This is simply not so. In the context of NAS vs directly attached, “local” frequently is used to refer to the latter.
As for the OP, I don’t think so. He was asking in the context (first sentence) of “that the Music library should be “locally” (i.e. not over the LAN)” and asked if his setup is considered local. The answer is simply that it depends:
It is local if we consider the difference of storage on one’s own premises vs internet streaming.
It is not local if we consider the difference between network storage vs directly attached to Core.
Either usage is common on the forum, depending on context.
Sigh And where did the OP say that he is only interested in the usage in official documents? He didn’t link a specific KB either. If the OP is reading posts on the forum, he will find both usages of “local”. If the first random search hit is not enough to convince you, here is another:
There is absolutely nothing difficult about this, you have seen both usages as well.
@Suedkiez@xxx I am sorry to have cause such a confusion! Thank you both for chiming in. I meant local in the sense that the connection between the music provider (the Roon Core) and its music files (the “storage”) goes not via the LAN, but is inside one system.
I do run the Core on the same NAS (Synology) where I host the music files. But my worry is that the data still goes through the network, because I had to connect the Synology Core with the music files via the Roon Controller on my Mac. But maybe that’s just a UI thing and underneath it all happens in the NAS…
The controller app is just a view to what is happening on the core. So, if you tell it to play something to a DAC attached to the NAS, then nothing leaves the NAS in terms of the music production chain.