Contributor I

Question

Error log: "Not enough Sonos player memory to complete index" - Why?

Forum|Forum|13 years ago
June 26, 2013
17 replies
1671 views

I just finished purchasing and setting up my Sonos amps and bridge (well, my installer did it, actually) and I am trying to load the music from my ReadyNasNV+ into the Sonos desktop software. My NAS has approximately 90,000 FLAC files, all properly tagged and in redbook resolution. Sonos is very slow to load, and ultimately only a few of my folders showed up in the library. I received the following error message in the log: Wednesday, June 26, 2013 - 11:11 AM Eastern Time Not enough Sonos player memory to complete index of '//NAS-01-3A-DA/media/Music'. A partial index has been stored. After some further reading on this site I noted that there is apparently a limit of 40,000 songs. Sonos claims it can handle large music libraries, so why is the limit only 40,000? Granted, most people don't have 1.6 TB of FLAC files, but I had absolutely no problem streaming all of them using my old Squeezebox system. I am incredibly disappointed and frustrated with Sonos. Why on earth is there a limit? I am going to have to return all of this gear to my installer for a refund, and then go back to using my old Squeezebox if there is no solution to my issue. Please offer any suggestions. Thanks. Wednesday, June 26, 2013 - 11:11 AM Eastern Time Not enough Sonos player memory to complete index of '//NAS-01-3A-DA/media/Music'. A partial index has been stored.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Show previous replies

A

Andy G

Trending Lyricist I

Hello

I have just hit the "memory barrier" with 31,343 mp3 files and 14,983 flac files making a total of 46,325. If the number of library files is variable depending on the existence and length of the metadata then I have a number of questions..
1) This is nowhere near the 65k tracks I was hoping for, is this because they are all well tagged?
2) How do I know how many files have been added to the library?
3) Which metata data/tags does Sonos cache, is it just the five; "Artist", "Albums", "Track", "Genre", Composer"?
4) My tracks have embedded artwork, does this affect the memory?
5) As this issue was raised over a year ago and is still "under consideration", is Sonos going to release a new product that doesn't have this limitation?
I was going to expand my Sonos system but now I am very reluctant to, given that I still haven't finished ripping the CD collection. I have another 300 to go which is at least another 3,000 tracks.

Hello Ryan

I can't seem to send a diagnostic report; I get an error message "Your diagnostic report could not be sent at this time". I have tried switching off the firewall and it still doesn't send.

I have been reading other forums and using the HTTP command to query the Sonos I can see the indexed track report.
http://Sonos-IP-Address/status/tracks_summary

It's also reported in these forums that filename length can affect the Sonos memory, so I have renamed a few hundred files and improved the COUNT from 41836 to 43408. I shall carry on renaming the rest of my files so that I can index the whole HDD of music, it should only take a week or so if I do an hour a day.. ahem!

One thought for a software change which could help a large proportion of Sonos system owners. would be to be able to switch off the caching of various tags, particularly the "Composer" tag. I only have a small collection of classical music and so I do not use the "Composer" option. I know it wouldn't help classical music fans, but at least it would make the system a little more flexible for some of your users.

I must say I'm pretty disappointed with this 65k limitation. When I first bought my Connect I thought it was the best toy I had bought in many years, but sadly it hasn't lived up to the promise of "All the music on earth" as it won't even play all the music in my house

J

Jean-François Dierckx

Lyricist I

Hello

I have just hit the "memory barrier" with 31,343 mp3 files and 14,983 flac files making a total of 46,325. If the number of library files is variable depending on the existence and length of the metadata then I have a number of questions..
1) This is nowhere near the 65k tracks I was hoping for, is this because they are all well tagged?
2) How do I know how many files have been added to the library?
3) Which metata data/tags does Sonos cache, is it just the five; "Artist", "Albums", "Track", "Genre", Composer"?
4) My tracks have embedded artwork, does this affect the memory?
5) As this issue was raised over a year ago and is still "under consideration", is Sonos going to release a new product that doesn't have this limitation?
I was going to expand my Sonos system but now I am very reluctant to, given that I still haven't finished ripping the CD collection. I have another 300 to go which is at least another 3,000 tracks.

I'm a bit concerned about this issue, as I've just decided to start a SONOS installation, and my system is currently indexing. Are there any updates on the situation and potential solution ?

A

Andy G

Trending Lyricist I

Hello

I have just hit the "memory barrier" with 31,343 mp3 files and 14,983 flac files making a total of 46,325. If the number of library files is variable depending on the existence and length of the metadata then I have a number of questions..
1) This is nowhere near the 65k tracks I was hoping for, is this because they are all well tagged?
2) How do I know how many files have been added to the library?
3) Which metata data/tags does Sonos cache, is it just the five; "Artist", "Albums", "Track", "Genre", Composer"?
4) My tracks have embedded artwork, does this affect the memory?
5) As this issue was raised over a year ago and is still "under consideration", is Sonos going to release a new product that doesn't have this limitation?
I was going to expand my Sonos system but now I am very reluctant to, given that I still haven't finished ripping the CD collection. I have another 300 to go which is at least another 3,000 tracks.

Hi, if you have fewer than 65,000 tracks then the best thing to do is to reduce tue length of the file names. I originally named mine 'artist-album-track-trackname' but I ran out of memory with only 36000 tracks. Once I renamed them to 'track-trackname' it almost halved the memory usage. The 65k limit is going to become a big issue soon for me though, as I still have half my collection to rip.....

A

Andy G

Trending Lyricist I

Hello

I have just hit the "memory barrier" with 31,343 mp3 files and 14,983 flac files making a total of 46,325. If the number of library files is variable depending on the existence and length of the metadata then I have a number of questions..
1) This is nowhere near the 65k tracks I was hoping for, is this because they are all well tagged?
2) How do I know how many files have been added to the library?
3) Which metata data/tags does Sonos cache, is it just the five; "Artist", "Albums", "Track", "Genre", Composer"?
4) My tracks have embedded artwork, does this affect the memory?
5) As this issue was raised over a year ago and is still "under consideration", is Sonos going to release a new product that doesn't have this limitation?
I was going to expand my Sonos system but now I am very reluctant to, given that I still haven't finished ripping the CD collection. I have another 300 to go which is at least another 3,000 tracks.

Hi, if you have fewer than 65,000 tracks then the best thing to do is to reduce tue length of the file names. I originally named mine 'artist-album-track-trackname' but I ran out of memory with only 36000 tracks. Once I renamed them to 'track-trackname' it almost halved the memory usage. The 65k limit is going to become a big issue soon for me though, as I still have half my collection to rip.....

G

Graham Price

Contributor II

Hello

I have just hit the "memory barrier" with 31,343 mp3 files and 14,983 flac files making a total of 46,325. If the number of library files is variable depending on the existence and length of the metadata then I have a number of questions..
1) This is nowhere near the 65k tracks I was hoping for, is this because they are all well tagged?
2) How do I know how many files have been added to the library?
3) Which metata data/tags does Sonos cache, is it just the five; "Artist", "Albums", "Track", "Genre", Composer"?
4) My tracks have embedded artwork, does this affect the memory?
5) As this issue was raised over a year ago and is still "under consideration", is Sonos going to release a new product that doesn't have this limitation?
I was going to expand my Sonos system but now I am very reluctant to, given that I still haven't finished ripping the CD collection. I have another 300 to go which is at least another 3,000 tracks.

I have invested several thousand pounds in my Sonos system over the past few years. It has been wonderful until this week when I hit the memory/indexing problem. What am I supposed to do now - scrap the whole system as it's not good if it doesn't work! I found something which suggested using Media Monkey provided a solution but I have downloaded it and it doesn't do anything, not that I understand what to do with it in any case. I loved the Sonos for its simplicity and now where am I - in a major mess. What gets me is that as time goes by more and more people are going to suffer from the same problem as they build up their collections!!!! About time Sonos got their act sorted.

J

Jgeish

Lyricist I

Only at 28k files and have reached my memory limit. Any advice on how to open up the remaining memory?

ratty

Only at 28k files and have reached my memory limit. Any advice on how to open up the remaining memory?

You must have large tag values and/or very long filenames. Generally the initial tactic is to reduce the filenames to a simply track number, e.g. 1.FLAC, 2.MP3, etc

First, though, go to http://x.x.x.x:1400/status/tracks_summary and post what you see there. The x.x.x.x IP address of a player can be obtained from About My Sonos System.

Sign up

Login to the community