Skip to main content

while I have a well controlled environment with my music library on a Synology NAS that works fine, I would like to have some insight about the repository on SONOS - in particular I would like to know how SONOS stores the index and on which devices (if not all) - I have a mixture of SONOS devices (Move, Beam, One, Five, Port, Amp, etc.) and would like to know if there are any good practices to follow to make the Music library update work faster  - many thanks in advance 

I've never worried about the speed of the update so can't offer hard data.

I have my library on an SSD drive, on a Raspberry Pi SMB host, that might be helping.

I recall something from long-ago about the firmware selecting a faster Sonos over a slower Sonos when an update is requested, might help if you requested the update from your fastest Sonos with the most memory, might not.

You might edit your track tags to hold only essential information. Maybe minimize path lengths and file name lengths. Maybe make a copy of your music to test this.

 

The index, like all Sonos data, is stored on all devices in their replicated database.

thanks for the prompt replies - if the index is stored on all devices, I guess that means that devices are updated when they come back on-line, in case they were unavailable during a music library update 

That sounds likely, if it matters it should be easy to devise a test.

Reply


Terms & ConditionsCookie settings