Contributor I

Answered

music library after latest app update

Forum|Forum|2 years ago
May 7, 2024
851 replies
51371 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!

Show previous replies

Ken_Griffiths

@jgatie @Ken_Griffiths

If that’s the reason it means the “my music folder” and “another folder or drive” options are no longer supported. Sonos should certainly do a lot more to communicate that. Whilst they have announced SMB1/HTTP support has been dropped, I doubt many know this has any relation to the above-mentioned options. I personally thought it only related to the option to add a network drive.

To reduce confusion, Sonos could disable the two non-network-drive options for adding music folder in the desktop app, and they could add a note to the following support article which doesn’t currently mention anything about dropped support: https://support.sonos.com/en-us/article/add-your-music-library-to-sonos

Absolutely any folder can be shared including ‘my music folder’, you just have to switch to use the SMB v2 (or higher) sharing protocol to use with that share as the ‘http’ and ‘SMBv1’ protocols are considered to be a security risk - it’s why Microsoft, Apple and Google (and now Sonos) are not supporting those sharing protocols - So, as an example, if using Windows to share your library you need to switch the share to use SMBv2, as detailed in this link…

https://en.community.sonos.com/controllers-and-music-services-229131/adding-a-windows-smb-share-step-by-step-6892060

O

osm

Absolutely any folder can be shared including ‘my music folder’, you just have to switch to use the SMB v2 (or higher) sharing protocol to use with that share as the ‘http’ and ‘SMBv1’ protocols are considered to be a security risk - it’s why Microsoft, Apple and Google (and now Sonos) are not supporting those sharing protocols - So, as an example, if using Windows to share your library you need to switch the share to use SMBv2, as detailed in this link…

https://en.community.sonos.com/controllers-and-music-services-229131/adding-a-windows-smb-share-step-by-step-6892060

I understand that any folder on a Windows or Mac can be shared on a network using SMB2 or higher. These can then be added to the Sonos system using the “network drive” option for adding a music folder. But the network drive option isn’t what I’m referring to. I’m referring to the first two options/pathways for adding a folder provided within the desktop app. These two options don’t ask the user to supply a network path, and as far as I’m aware Sonos hasn’t unambiguously announced that these options are no longer supported. They even make it seem like they are still supported since there is no reference to dropped support in the relevant support article (linked in my previous post). The announcement of dropped SMB1/HTTP isn’t really sufficient to inform users of dropped support for these first two options as that’s using terminology not actually seen in the app or in the support article.

press250

Prodigy III

I understand that any folder on a Windows or Mac can be shared on a network using SMB2 or higher. These can then be added to the Sonos system using the “network drive” option for adding a music folder. But the network drive option isn’t what I’m referring to. I’m referring to the first two options/pathways for adding a folder provided within the desktop app. These two options don’t ask the user to supply a network path, and as far as I’m aware Sonos hasn’t unambiguously announced that these options are no longer supported. They even make it seem like they are still supported since there is no reference to dropped support in the relevant support article (linked in my previous post). The announcement of dropped SMB1/HTTP isn’t really sufficient to inform users of dropped support for these first two options as that’s using terminology not actually seen in the app or in the support article.

Spot on @osm, leaving those choices for the ‘native’ Sonos music library mechanism in the desktop apps is fubar. While I recognize that the desktop apps are not long for this world, both the Mac and Windows apps have been updated in the past month. Removing the no-longer-functional native music library choices would certainly save bunches of people a grief.

Ken_Griffiths

I understand that any folder on a Windows or Mac can be shared on a network using SMB2 or higher. These can then be added to the Sonos system using the “network drive” option for adding a music folder. But the network drive option isn’t what I’m referring to. I’m referring to the first two options/pathways for adding a folder provided within the desktop app. These two options don’t ask the user to supply a network path, and as far as I’m aware Sonos hasn’t unambiguously announced that these options are no longer supported. They even make it seem like they are still supported since there is no reference to dropped support in the relevant support article (linked in my previous post). The announcement of dropped SMB1/HTTP isn’t really sufficient to inform users of dropped support for these first two options as that’s using terminology not actually seen in the app or in the support article.

Spot on @osm, leaving those choices for the ‘native’ Sonos music library mechanism in the desktop apps is fubar. While I recognize that the desktop apps are not long for this world, both the Mac and Windows apps have been updated in the past month. Removing the no-longer-functional native music library choices would certainly save bunches of people a grief.

The issue here though is the old desktop Apps still do support the old sharing protocols, but yes no doubt these will be obsoleted at some stage, but I can’t see that happening until at least the library setup and indexing features are added to the new Sonos App.

press250

Prodigy III

The issue here though is the old desktop Apps still do support the old sharing protocols, but yes no doubt these will be obsoleted at some stage, but I can’t see that happening until at least the library setup and indexing features are added to the new Sonos App.

Firmware v16.2 released last month is not compatible with the the old/native Sonos library sharing mechanism (aka http share), it generates the wonderfully descriptive Error 913. Leaving the appearance if “click-click” library sharing in the desktop apps when it doesn’t work on any Sonos gear is bad, full stop.

Ken_Griffiths

The issue here though is the old desktop Apps still do support the old sharing protocols, but yes no doubt these will be obsoleted at some stage, but I can’t see that happening until at least the library setup and indexing features are added to the new Sonos App.

Firmware v16.2 released last month is not compatible with the the old/native Sonos library sharing mechanism (aka http share), it generates the wonderfully descriptive Error 913. Leaving the appearance if “click-click” library sharing in the desktop apps when it doesn’t work on any Sonos gear is bad, full stop.

Well I haven’t tested this myself, but I thought this was resolved by setting up an ‘everyone’ share permission on the same library folder, or adding a specific user with credentials and ensuring those credentials were used alongside the folder path in the Sonos App… as mentioned here:

press250

Prodigy III

Well I haven’t tested this myself, but I thought this was resolved by setting up an ‘everyone’ share permission on the same library folder, or adding a specific user with credentials and ensuring those credentials were used alongside the folder path in the Sonos App… as mentioned here:

I have tested it myself: a few weeks back in an effort to help people on these forums* … and literally a few minutes ago to verify that it was still broken before chiming in above. And I was using this mechanism for years, so I am 100% positive it is setup correctly on my Windows machine wrt permissions and the like.

Good fortune was smiling upon me when I decided to bit the bullet and switch to an SMBv2 share just a few days before the new app dropped. At the time, word from Sonos (in emails sent to some customers and pop-up messages to some others) was that http and SMBv1 shares would go the way of the dodo bird “in a few months,” though for reasons unknown that turned out to be less than ten days.

* I also reported my findings to Sonos at that time

Ken_Griffiths

@press250,

Somewhat similar to you, I realised that the new Sonos App would only be supporting SMB v2 (or higher), but I have been using that newer version for some years with my NAS box, but I too thought it would be some months before the Windows/MacOS Desktop Apps would be obsoleted and that (for now at least), just those older unchanged Desktop Apps would continue to support the ‘http’ share using the SonosLibraryService and SMB v1 shares (at least on Windows 10) - I understand SMBv1 is no longer available on Windows 11… so I’m really surprised that these things have been removed already. That’s certainly sooner than I expected as I understood the old S2 desktop controller Apps have been in maintenance mode for a while and were unchanged and they have always supported all versions of SMB.

I can’t comment further on this though, as I haven’t tested these things myself, but like you I did think these things were not going away for some months, as mentioned in the Sonos App notification that was included in my earlier post in this thread.

Assuming what you say is correct, I’m really surprised by this, but I did think these older sharing services would only go (obviously) when the old Desktop controller Apps were eventually retired.

K

Kos

Enthusiast II

In mid-June, the library search is back. Not. Come on, I want the tires back on my car.

Kos

P

phoward999300

Enthusiast II

I am amazed at all the suggestions to fix Sonos incompetence. I seriously appreciate the time and effort of everyone trying to fix this.

But this is on Sonos - they either fix it or not. There are hardware and software alternatives and if necessary, goodbye Sonos. And good riddance.

The majority of people who lost their library is because Sonos no longer supports SMB v1 shares due to security reasons. Since Sonos has no control over what your OS or NAS is using to share, how are they supposed to “fix this” if it is using SMB v1?

I use SMB v2 but still have the same issue

Show more replies

Sign up

Login to the community