Skip to main content

Okay, this is going to be long. Like many of you I have hit the wall on the NAS issue.  Don’t let them lie to you about SMB.  It is 100% about indexing.

  1. Normal folder structure of Artist/Album/Song craps out quickly.  The meta-data is just too large for the crappy app
  2. So I copied songs individually to folders.  First couple of folders could do about 1000 songs. Works perfect. Can index these songs.
  3. If you do more than that it fails.  So this is a VOLUME issue, not a SMB issue
  4. So I created a few more Folders with 1000 or so songs in them and was able to index those.  Fine
  5. By the time I was at 5 Folders, needed few and few songs per folder
  6. Stupid, terrible, unfriendly app craps out at 16 folders (hard max)
  7. I can’t prove it, but it seems like things loaded better if I cleaned up some special characters that were part of the song names.

So I can get roughly 9,000 of my 22,000 songs into SONOS.

In the mean time, the help chat continues to spread the lie that this is about SMB.  If that was true, I wouldn’t be able to get ANY songs into it.

I would never ever ever recommend Sonos to anyone.  This is an easy problem to fix.  Figure out the index limitations and build in self cleanup so you don’t run out of memory.

So my question is:

Why isn’t there a fix for this?

When is a fix expected?

How do I get that diagnostic?  I simply get an error. Where is the diagnostic stored?

 

 

You don’t get the diagnostic, you run the process and it gets sent to Sonos support.  Then you need to contact support with the reference number.  See this link:

https://support.sonos.com/en-us/article/submit-diagnostics

I got on a call where they took control. Sent diagnostic.  Guess what. Its an indexing problem. 

We all figured that out ourselves.

I have a L2 support call scheduled for 2 weeks from now.  I think they spend 100 times the effort in dealing with unhappy customers instead of just fixing the app.  When you have an app that hasn’t been released in 4 months, you know you have a dev team that has no clue what they are doing.

I got on a call where they took control. Sent diagnostic.  Guess what. Its an indexing problem. 

We all figured that out ourselves.

I have a L2 support call scheduled for 2 weeks from now.  I think they spend 100 times the effort in dealing with unhappy customers instead of just fixing the app.  When you have an app that hasn’t been released in 4 months, you know you have a dev team that has no clue what they are doing.

You might ask them to take a close look at the SMB Credits issue, which seems to be the root cause.

@Ianp I have researched and can not seem to find a fix for the SMB Credits issue.  I have added a regedit line as stated but that did nothing.

What exactly can I do to fix this?

@Ianp I have researched and can not seem to find a fix for the SMB Credits issue.  I have added a regedit line as stated but that did nothing.

What exactly can I do to fix this?

You cannot its a bug/problem on the Sonos end, they need to address it

I got on a call where they took control. Sent diagnostic.  Guess what. Its an indexing problem. 

We all figured that out ourselves.

I have a L2 support call scheduled for 2 weeks from now.  I think they spend 100 times the effort in dealing with unhappy customers instead of just fixing the app.  When you have an app that hasn’t been released in 4 months, you know you have a dev team that has no clue what they are doing.

 

They released a new app for iOS just last week, and a new Android version less than a month ago.  And I guarantee the people assigned to support calls are not being taken away from development, and vice versa.

So I can’t find anyone whose answer was buying a “newer” NAS.  So I’m not sure the age of the NAS matters.  Has anyone solved this problem with a NAS upgrade?

So I can’t find anyone whose answer was buying a “newer” NAS.  So I’m not sure the age of the NAS matters.  Has anyone solved this problem with a NAS upgrade?

The age doesn’t matter really. What matters is if you can change or update the nas to smbv2 or 3. 

Chances are newer nas do this no problem, older nas might be hit or miss. 

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…..

I have 25,697 tracks on a wired NAS, that happily index without any problems here. I can even load them all to a Sonos room queue using an .m3u playlist, as shown in the attached. 

Some rippers will throw the whole first stanza of an opera track into the file name. This is unnecessary. If you use simple track numbers as the file name, you’ll be able to deal with a larger library. I store each disc in its own folder and name the files as “Trk01.flac” (or whatever is appropriate for your format) I also avoid overly long artist and title names. Libraries of 60K+ are not a problem for me. Playlists are a bit funky at the moment, but in the past I’ve built 60K+ playlists. Many users claimed that this was impossible because they bombed out at a few hundred.

In the distant past we had access to more detailed diagnostic data that would give exact details of the index size. It was obvious if one had reached the limit due to excessive metadata.

Only scanned the thread but I have a synology with tens of thousands of tracks on it. It’s yet another casualty of the garbage Sonos garbage app garbage updates. These people are just lying to their customers. It’s a total ****ing disgrace. As soon as I can find the time (and money) I will be getting an alternative.

Only scanned the thread but I have a synology with tens of thousands of tracks on it. It’s yet another casualty of the garbage Sonos garbage app garbage updates. These people are just lying to their customers. It’s a total ****ing disgrace. As soon as I can find the time (and money) I will be getting an alternative.

I’d always thought of the Synology NAS solution as being solid for Sonos, even through the recent architecture change. Is there a specific problem you are experiencing?

You could also consider running Plex on your NAS and adding the Plex Sonos service to access your music.

Only scanned the thread but I have a synology with tens of thousands of tracks on it. It’s yet another casualty of the garbage Sonos garbage app garbage updates. These people are just lying to their customers. It’s a total ****ing disgrace. As soon as I can find the time (and money) I will be getting an alternative.

I use a Synology NAS for my local library and have had no issues with the app finding my files. Sure there is the functionality inconveniences, but I also have the Mac app that has always done what I needed.

What issues are you having?

Reply


Terms & ConditionsCookie settings