Skip to main content
Contributor I
May 7, 2024
Answered

music library after latest app update

  • May 7, 2024
  • 851 replies
  • 51369 views

Just installed the new app. But I can’t find where the music library went. Also no option to add a folder to the library 

 

Moderator edit: We have an article with instruction on how to add a music library share on Windows and MacOS. Have a look.

 

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 aitchgf

Hi mvosloo

Thanks for the response tip, will try it our and see how I get on!

851 replies

press250
Prodigy III
July 20, 2024

When selecting Manage → Music Library Settings and clicking the add (+) button, there are three choices. The first, My Music Folder is what most Mac users select as this (used to) add the Music folder with all of the locally stored files. Presumably the Sonos app knows the proper path. The links you posted, and that I have worked through, presumably apply to the third option in the Setup window, Networked device (ex. NAS drive). As Press250 noted, you can select this option after following all of the hints to add the shared Music folder. This worked for me but only temporarily (maybe a few days).

Sorry if this is pedantic but some clarity and repetition can sometimes be helpful on these long threads.

Hi @yellowtail, those first two choices are nothing but trouble: despite being selectable in the desktop app, they are not supported. Your only option is “Networked device” pointing to a folder shared with SMBv2 or v3.

Ken_Griffiths
July 21, 2024

Yes,, @yellowtail always go for the last (NAS) share option, as mentioned - I’m pretty sure the other two options are HTTP shares using the SonosLibrary.exe ‘service’ - those shares cannot be seen in the new Sonos App, although I understand the old desktop controller App can see those shares (they’re now considered as being insecure) - so just select the last option and add the full network path, username and password for a user that has ‘read only’ access permission to the shared library folder. If all else fails you can use the ‘Everyone’ (guest) user share (but do that only as a last resort, as it’s less secure).

press250
Prodigy III
July 21, 2024

Yes,, @yellowtail always go for the last (NAS) share option, as mentioned - I’m pretty sure the other two options are HTTP shares using the SonosLibrary.exe ‘service’ - those shares cannot be seen in the new Sonos App, although I understand the old desktop controller App can see those shares

Hi @Ken_Griffiths you are spot that those first two options create http shares. The v16.2 firmware released on 10 May 2024 dropped support for http (and SMBv1) shares, so even the desktop controllers don’t work. It’s unfortunate that those first two options remain in the desktop apps as they cause nothing but confusion and frustration.

Ken_Griffiths
July 21, 2024

Hi @Ken_Griffiths you are spot that those first two options create http shares. The v16.2 firmware released on 10 May 2024 dropped support for http (and SMBv1) shares, so even the desktop controllers don’t work. It’s unfortunate that those first two options remain in the desktop apps as they cause nothing but confusion and frustration.

I didn’t realise the http/smbv1 shares were no longer viewable via the old S2 PC/MAC desktop Apps - They have been In ‘maintenance’ mode now for some years - very little gets changed in those Apps, but I agree removing the library options might have helped, but maybe they’ve left them there for any users who perhaps have not upgraded their devices firmware in more recent times. (…the index is held on the players). 

I do personally think once the local library features become available in the new Sonos App, (adding a library, indexing etc.) that the old controllers ‘might’ fall fairly rapidly towards obsolescence. That’s just my guess, of course.

Trending Lyricist I
July 21, 2024

Yes,, @yellowtail always go for the last (NAS) share option, as mentioned - I’m pretty sure the other two options are HTTP shares using the SonosLibrary.exe ‘service’ - those shares cannot be seen in the new Sonos App, although I understand the old desktop controller App can see those shares (they’re now considered as being insecure) - so just select the last option and add the full network path, username and password for a user that has ‘read only’ access permission to the shared library folder. If all else fails you can use the ‘Everyone’ (guest) user share (but do that only as a last resort, as it’s less secure).

I don’t quite understand that. MacOS Sonoma (and other recent OS versions) use smb for file sharing and I am pretty sure http is not used for any services. I don’t see any http services being advertised on my local network and port 80 is not open on my Mac mini. Are you saying the Sonos desktop app tries to share the local Music folder via http? If the Sonos iOS app can’t see that share then that does not make sense (on the part of Sonos). In any case, that first choice to select the Music folder generates the infamous “913” error.

To be clear, the NAS option only worked temporarily. When I say the library disappeared I mean it was gone from the desktop Sonos app (running on the Mac with the Music library) and, of course, was dropped from the Sonos iOS app.

Ken_Griffiths
July 21, 2024

I don’t quite understand that. MacOS Sonoma (and other recent OS versions) use smb for file sharing and I am pretty sure http is not used for any services. I don’t see any http services being advertised on my local network and port 80 is not open on my Mac mini. Are you saying the Sonos desktop app tries to share the local Music folder via http? If the Sonos iOS app can’t see that share then that does not make sense (on the part of Sonos). In any case, that first choice to select the Music folder generates the infamous “913” error.

To be clear, the NAS option only worked temporarily. When I say the library disappeared I mean it was gone from the desktop Sonos app (running on the Mac with the Music library) and, of course, was dropped from the Sonos iOS app.

Yes, it was indeed the case originally, that the Desktop controller App setup the read only share over http when using the first two available library options and it shared them by running a service when the PC started up - for Windows it was an executable file. These things now are not working with the latest device firmware according to @press250. So the suggestion is to setup the share manually, as explained in the links and videos posted earlier.

So goto the 3rd (NAS) library share option to setup the share and add the full UNC path — you can either use the IP address of the computer, or it’s Netbios name at the start of the path and then the name of the share. Example: //I92.168.0.230/Music or //MyPCName/Music …then add the ‘user credentials’ when prompted, that you’ve setup and are in place for ‘read only’ access (permission) on the shared Music folder  (you need to do that first of course)  and if all is entered correctly you can go onto run the Sonos library index and when it’s complete it should show in the new Sonos App.

I hope that assists. The YouTube video link posted earlier seems to explain it quite well,from my own perspective, but as I say I’m not a MAC user myself, but it seems reasonably straightforward… er hopefully.🤞

Ken_Griffiths
July 21, 2024

I just found this post too from Sonos Staff…

It just confirms what’s been mentioned here.

press250
Prodigy III
July 21, 2024

I just found this post too from Sonos Staff…

Hi @Ken_Griffiths I cannot see posts in the ‘lounge’ … how does one get access?

Ken_Griffiths
July 21, 2024

No idea why it’s not working now @press250, it was something I saw during a search on the subject. Anyhow I’ve just searched again and here’s an almost identical/similar post/discussion and this one involves yourself this time … it’s with controlav - so hope you (and @yellowtail) can see this link. Let me know if you can’t and I’ll perhaps screenshot it.

 

Trending Lyricist I
July 21, 2024

I don’t quite understand that. MacOS Sonoma (and other recent OS versions) use smb for file sharing and I am pretty sure http is not used for any services. I don’t see any http services being advertised on my local network and port 80 is not open on my Mac mini. Are you saying the Sonos desktop app tries to share the local Music folder via http? If the Sonos iOS app can’t see that share then that does not make sense (on the part of Sonos). In any case, that first choice to select the Music folder generates the infamous “913” error.

To be clear, the NAS option only worked temporarily. When I say the library disappeared I mean it was gone from the desktop Sonos app (running on the Mac with the Music library) and, of course, was dropped from the Sonos iOS app.

Yes, it was indeed the case originally, that the Desktop controller App setup the read only share over http when using the first two available library options and it shared them by running a service when the PC started up - for Windows it was an executable file. These things now are not working with the latest device firmware according to @press250. So the suggestion is to setup the share manually, as explained in the links and videos posted earlier.

So goto the 3rd (NAS) library share option to setup the share and add the full UNC path — you can either use the IP address of the computer, or it’s Netbios name at the start of the path and then the name of the share. Example: //I92.168.0.230/Music or //MyPCName/Music …then add the ‘user credentials’ when prompted, that you’ve setup and are in place for ‘read only’ access (permission) on the shared Music folder  (you need to do that first of course)  and if all is entered correctly you can go onto run the Sonos library index and when it’s complete it should show in the new Sonos App.

I hope that assists. The YouTube video link posted earlier seems to explain it quite well,from my own perspective, but as I say I’m not a MAC user myself, but it seems reasonably straightforward… er hopefully.🤞

Thanks.

As I said, I tried all those steps (followed links, viewed videos, etc.) but it does not work, for me at least.