NAS support

Let me guess . . . your filenames and pathnames are huge?  Very long file/pathnames can make a relatively small library take up many more slots than the actual number of tracks, quickly filling up the 65K limit.  If this is so, you are correct, it has nothing to do with SMB.  It also has nothing to do with the new software, because that limit has been there for decades.

Shorten up your pathnames, either by shortening the actual path, or sharing from closer to the folder(s) where the tracks reside. 

They are what gets created when you burn CDs.  Most of my 20,000 songs came from when I digitized my music collection.

I-Tunes handles it just fine.  Sonos should be able to handle it also.  

But, yes, it is the update.  It has nothing to do with the player.  Only the indexing software.

It is a NAS drive, index the file names BACK to the NAS drive. Not limit needed.  It is simply terrible software.  To do this all in memory is a terrible design.

I can’t imagine a single person out there with a large music library that could use this functionality. It is horrible.

I have a library of almost 30,000 songs and my indexing works fine. I added just under 200 songs last night that indexed without issues.

I have a Synology NAS on my network with just under half of my speakers hardwired.

Awesome. But that doesn’t stop the continuous error the rest of us are getting.  What app are you adding your file shares from?

@sambrosius Of course if there’s any indexing being done the SMB-version is not the problem. But lots of people do not get a connection to their library at all - and if that’s your problem it can most definitely be SMBv1 that Sonos stopped supporting early in May.

Your problem looks like it’s connected to the 65k limit. No one except Sonos can say if it is easy to fix or not. But it would be go to know if you also had this problem when the old app was still around, or if it developed more recently?

Why the attitude though? This is a user community where users are trying to help others. Nobody is knowingly providing wrong solutions as you seem to say.

I just bought the system.  Never used the old app, but from the other posts I can see that Sonos has been giving people the run around. Just like myself.  The tech support basically after lying to me about what the issue is had to admit, “we have a problem and we don’t know when it is going to be fixed”.

So I went and did my own research.  What is the 65K limit?  Because I couldn’t get even 2,000 songs (no directory, just the songs in a single directory) to load.  I finally narrowed it down to about 1,000 that worked for a while, but in the end I was down to 250 until I hit the 16 folder issue.  9,000 total songs is a drop in the bucket for most music libraries.  

My complaint is why isn’t Sonos doing the same debugging I am.

 I have a meticulously tagged library of 42,000 tracks.  They index OK.  I did have some Bluesound stuff some years ago.  On one occasion the index stalled.  As I remember you could send them a log and they would tell you at which point the index stalled.  Then you could troubleshoot the issue.  If I remember correctly the index stall was due to a special character Bluesound did not like.  Who knows now maybe that’s all changed and the index would have completed.  I’ve never had an incomplete Sonos index.

What app do you use to add your Shared Folders.  IOS doesn’t work at all.  Windows app is the one I have been using.

I have mostly used the app on my Mac to configure and edit my local library. I sometimes use the app for queues, but its mainly to access the files I want to play.

 I use the Windows app because there is no progress feedback when indexing using the Sonos app.