Trending Lyricist I

Answered

I can no longer add full music library - only 20GB of 125GB

Forum|Forum|1 year ago
October 10, 2024
45 replies
1114 views

Before the new app, I was able to listen to my home music library which was kept on a usb hard drive that was attached to a D-Link router. The music library is about 125 GB and consists of around 25,000 files (a mix of mp3 song files, as well as a few jpg for album art, plus each song had an .info file associated with it). Everything played well. I mostly avoided the debacle of the new app rollout as I disabled all software/firmware updates, but unfortunately a firmware update made it through anyway, so I had to update to the new app, rendering my music library unreachable; I believe the issue was the smbv1 was no longer supported with my router. So, I recently updated my router to a TP-Link that also had a usb port so I could continue using the external hard drive I had my music on. Long story short - I can only add a total of 20GB of my original music library.

If I try to add the whole folder in one shot, it seems like it’s doing something for about 10 minutes, then I get an error saying: “[myfolder] is no longer available. The device where music files are stored may not be powered on, or the path may have changed.”

If I set up a folder with a just few artist/abums, Sonos will index it without the error, and they show up on the Sonos app and play fine. If I add more artists/albums to that folder and ask Sonos to update the library, they are added, but only up to 20GB of music. The second I add any additional music (either to the same folder, or a second folder) I almost immediately get the same error message. What is happening? Where is this limit coming from? It shouldn’t be the 65,000 song limit, since I have much less files than that, plus everything played great before all the changes.

Anyone have a similar issue that figured it out? Or is there someone with a similar recently added library set-up (usb drive to router, i.e. not a NAS), that has a library larger than 20GB that works? Then at least I’d know it’s not a purposeful Sonos imposed limitation.

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.

Best answer by Ken_Griffiths

I understand the 65,000 track limit you refer too is not a track limit, but what I will term as ‘memory slots’ and some tracks may take up more than one slot. There are also these limitations which I found in other threads here in the community…

Field Name Character Limits

Artists - 76
Album - 92
Track - 100
Genre - 22
File name - 100

So maybe you’re exceeding some limitation that’s causing you an issue, but maybe contact Sonos Support Staff via this LINK and see if they can perhaps assist you further.

Ken_GriffithsAnswer

I understand the 65,000 track limit you refer too is not a track limit, but what I will term as ‘memory slots’ and some tracks may take up more than one slot. There are also these limitations which I found in other threads here in the community…

Field Name Character Limits

Artists - 76
Album - 92
Track - 100
Genre - 22
File name - 100

So maybe you’re exceeding some limitation that’s causing you an issue, but maybe contact Sonos Support Staff via this LINK and see if they can perhaps assist you further.

MoPac

Headliner III

Ken:

What’s the difference between Track & File Name?

I

IzzybonesAuthor

Trending Lyricist I

Are those field and character limits new? I’m pretty sure none of my files exceed those as I like to keep my naming system simple. It’s the exact same library I’ve been using for years, so if they are not new, then I’m probably well within individual file character limit. Was hoping to see if I can glean any insights from the community before attempting support staff since they’re likely overrun these days…

Ken_Griffiths

Ken:

What’s the difference between Track & File Name?

Nothing probably. As stated I copied it from past threads (a long time ago) - unless it should read ‘path’, perhaps?

Ken_Griffiths

Are those field and character limits new? I’m pretty sure none of my files exceed those as I like to keep my naming system simple. It’s the exact same library I’ve been using for years, so if they are not new, then I’m probably well within individual file character limit. Was hoping to see if I can glean any insights from the community before attempting support staff since they’re likely overrun these days…

No they’re not new - they have been mentioned in the distant past - maybe as far back as 2016, or before.

Ken_Griffiths

I just searched the site and found this from 8 years ago …

There maybe older and newer mentions of the field limitations, if anyone perhaps wishes to search back through the community threads.

MoPac

Headliner III

Ken:

What’s the difference between Track & File Name?

Nothing probably. As stated I copied it from past threads (a long time ago) - unless it should read ‘path’, perhaps?

Thought about it. Maybe it’s the physical file name which could be different than the Track name in the tags. Not sure though.

MoPac

Headliner III

Wish there was an accessible log that would show you where the index stopped. I used that with other software a while back to fix boo boos I had in the library.

Ken_Griffiths

@Izzybones,
Not sure if this may help as a bit of a comparison … but note I’m using a NAS in this instance.

Anyhow, I just thought I would go check my own library size etc; which is setup on a Netgear NAS box and its folder size (see attached) is 230.57GB.

That caters for 25,697 tracks plus artwork images/folders etc. and that indexes okay in the Sonos App. I’ve attached an old screen-capture just showing the Sonos App loading all the library tracks to a room queue using an *.m3u playlist I created a couple of years ago - it just confirms the total number of tracks… it wouldn’t load the playlist if they were not in the library/index.

Is it possible your router might be limiting things in this case too, perhaps?

Ken_Griffiths

Wish there was an accessible log that would show you where the index stopped. I used that with other software a while back to fix boo boos I had in the library.

I think there might be something in the Windows controller that might assist with this - (not sure🤔?) - some kind of logging, others might chime-in here, perhaps? However I think the indexing happens so quick that it can only give a bit of guide as to the whereabouts of the track causing the failure.

Show more replies

Sign up

Login to the community