There are lots of different NAS drives out there ... many of which support some sort of music serving service. I have my personal collection and Yate's extensive test collection on a QNAP NAS.

Yate has a batch processor. The processor is supplied an action and provided with one ore more root folders. Every folder in or under one of the roots which contains an audio file is processed. The batch processor also has an alternate mode where it is suppled a pre-existing track database. All data in the track database is then applied to the appropriate files.

A track database can be built by running a batch process with a simple one line action. Similarly, you could walk your entire collection and modify genres or correct artist names via the same method. Yate even has statements letting you accumulate all artist names used in any fields,

There will never be direct integration with any specific NAS index. As said, a track db can be constructed with a single statement. Further your standard workflow can be written to update the database whenever changes or additions are made in the UI. I've processed track DBs with over 100k rows. I also use the ability to query track databases in actions. The Artist database set of actions on the resource page makes extensive use of query db statement.

I use a Sonos system which has to be told when to reindex. My standard workflow action tells Sonos to update via calling an external script.

Pretty much anything can be done.

This would also kind of "ease" the creation of the YATE database other than "manually" open all music and manually add it to yate-database - if I am not wrong.

Hopefully I answered this 🙂