NAS support

Just FYI @sambrosius 

I have over 20k songs in my library stored on a Synology NAS.
Not sure what you mean by the “16 folder limit”. My music has a separate folder for each Artist and Album folders within that. I have 583 Artists (top level folders) and 1108 Albums (lower level folders).

Like you I used the Sonos Windows Desktop app to add the Synology music share to Sonos.
I generally use the Windows Desktop app to do the reindex and have never had a problem.

The only music library issues I currently have is the 16.3 Firmware issue to do with compilations making the album view useless and the lack of direct alphabetic positioning using the new IOS app (for both the artists and albums views) which is a pain for Sonos users with large local Music libraries.
e.g. Scrolling through 1108 Albums to get to the “Zombie” Album by Fila Keti is a painfully slow process.
I am currently tending to use SonoPhone/SonoPad for local library playback for that reason.

Ross. 

Fila Keti or Fela Kuti?

Ooops. Bad proofreading of post on my side...

I see your problem was misdiagnosed by the Sonos people? They expressly told you there was an SMB problem (for which, by the way, no solution will be provided)? And this qualifies as “lying” to you, not just a mistake, or insufficient training?

So what exactly did Sonos tell you? Can you show a typical filename for a song, so someone here can say if it is too long and would cause the 65k limit to be reached?

There is a limit of 65,000 items that Sonos can potentially index in a local music library. However, it’s not a guaranteed maximum, as there appears to be a fixed limit on how much space the index can consume as well. Unfortunately no-one knows what that is and also the app doesn’t tell you what % of available space your index has used. (Which would be really useful) 

Very long overall path plus file names can eat into that space quicker. 

When you say 16 folders, do you mean you've added 16 different folders into the main music library settings? 

Also, as others have asked, do you have a long overall path to your music like …

\\my-really-long-network-drive-name\another-really-long-path-to-my-music\which-starts-here ?

Thanks. Just gave it a listen. Good stuff.

Also, you just taught me that Afrobeats (which I already listen to at times) is different from Afrobeat.

Again, I have 9,000 files loaded.  Path is IP/Public/Sonos/Sonos01 .  I can not have more than a couple hundred songs in that directory or the directory fails to load. 

So I have 01 - 16.  (thus the 16 shared folder limit).

Total about 9,000 songs. 

How is anyone getting 20K songs to index.

If I press  Update Music Library Now, the index fails with the error:

The device where the music files is stored may not be powered on….

This is the error associated with the 65K rule (based on searching) but makes no sense since I only have 9K songs loaded.

@sambrosius I don’t have a solution for the issue you are reporting, and have experienced this myself.

We used to be able to see our total track number through the Sonos diagnostics, but that was removed partly because it’s not just the 65K tracks but also associated metadata than can exceed Sonos’ limit. I do believe that if you submit a diagnostic and contact Sonos Support they can tell you whether the limit is being exceeded, but of course you can be confident that with only 9K tracks you will be fine.

Under S2, I could index my NAS library fine using SMBv1. I can force my NAS to use whichever SMB protocol I choose. When SMBv1 support was removed for S2 users, I started seeing problems. This was years ago. I have my music split into 12 folders to try and reduce the track number per folder, and I don’t have long path names - an example being \\music\MNO\New Order\Brotherhood. You can’t get shorter than that.

Sometimes I am able to index everything with a single \\music entry in the desktop library settings. But then if I add a new album and re-index, it fails. I can be listening to music from my library, start the index, and it will say the location is no longer available! And the music keeps playing….

When I get errors, my router’s log reports a lack of SMB credits. But of course my NAS works fine for everything else. And many others on here have no issues, which suggests it is linked to certain routers and NAS combinations. I have an Asus mesh system.

I might investigate running OpenMediaVault on a Raspberry Pi, with my music on a USB stick, but I’ve not got round to it yet. Others get round the limit by using Plex, but that means you add Plex as a service to Sonos and you are then playing your local library via the cloud. I think. Could be wrong.

“When SMBv1 support was removed for S2 users, I started seeing problems. This was years ago.” To my knowledge SMBv1 was removed from S2 some time after May 8th.

 I don’t understand why the number of folders would cause an index to fail.  My folder structure is Genre-Artist-Album.  I have over 1, 500 classical composers and that’s just the genre Classical.  The index works fine.  My library is in a SonicTransporter i5 NAS.

 If the issue is tagging then that’s a different story.  I keep tags simple.  I only use Artist-Track Name-Album-Track Number-Date-Album Artist.  All other tags that might exist, when the source of the music is a download, are removed.  The Artist & Album Artist tags for Classical are the last name of the composer.  My tagging software is DbPoweramp.