Contributor I

Answered

music library after latest app update

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

F

FozzyB

Lyricist III

It's simply too much hassle to work through 000s of tracks to make changes in the hope it indexes.

If you can identify the character(s), then maybe use a batch ‘replace’ action in MP3Tag and enter the special character to replace, or delete - just leave it run, if it’s a large library.

See this link:

https://community.mp3tag.de/t/actions-and-batch-operations/967/4

Thanks - please can somebody from Sonos tell me which characters are acceptable and which are not.

R

Rusty Hammer

Contributor I

I’m elderly and not tech savy. I spent years building playlists only to have sonos remove them with the update from hell. When I go to settings and try to detect my library all I get is a notice that says “music library was not found”. There are some albums in the Sonophone app but no playlists there either and I can only play some of the albums. Please find a fix this before this old man meets with the person who screwed this app when we meet in hell.

MoPac

Headliner III

I’m elderly and not tech savy. I spent years building playlists only to have sonos remove them with the update from hell. When I go to settings and try to detect my library all I get is a notice that says “music library was not found”. There are some albums in the Sonophone app but no playlists there either and I can only play some of the albums. Please find a fix this before this old man meets with the person who screwed this app when we meet in hell.

Where is your library? Where are your playlists and what format are they…. How were they created?

ninja2

Avid Contributor III

I’m elderly and not tech savy. I spent years building playlists only to have sonos remove them with the update from hell. When I go to settings ...

Hey “Rusty” :-) I’m elderly too, although unusually tech savvy due to my long career in computing. Honestly I suggest you call SONOS help line.

I had the same issues unilt recently when the App was automatically updated and then I was able re-connect my Music Library (I had removed it myself when the troubles began). There is hope at the end of the tunnel …

D

DaveCHAZ

Contributor I

I’m elderly and not tech savy. I spent years building playlists only to have sonos remove them with the update from hell. When I go to settings and try to detect my library all I get is a notice that says “music library was not found”. There are some albums in the Sonophone app but no playlists there either and I can only play some of the albums. Please find a fix this before this old man meets with the person who screwed this app when we meet in hell.

When my system crashed after the update I contacted Sonos for a live chat with their technical department. Probably had 2 conversations, one 90 minutes long and found them very helpful and I allowed them to come onto my computer and sort the problem. I now have system that is updated from iTunes and more or less working as before. All my music Library is the same as on iTunes music Library. I also now have radio stations back again and all my previous Sonos playlists. The iPhone app is still not fully working but I understand that will happen eventually. It has been a total nightmare and hopefully one day soon Sonos will sort out all their problems. I am also in my mid seventies but I had to persevere by contacting Sonos. My system is Apple based with iMacbook and desktop plus mobile

D

DBrock

Lyricist II

5 months after the May update, invested many fruitless hours with first tier Sonos techs, finally elevated to a level of expertise resulting in renewed access to my music library( Mac laptop) and playlists in their entirety. Happy finally regaining that which never should have been made inaccessible. Seemingly avoidable debacle.

Ken_Griffiths

5 months after the May update, invested many fruitless hours with first tier Sonos techs, finally elevated to a level of expertise resulting in renewed access to my music library( Mac laptop) and playlists in their entirety. Happy finally regaining that which never should have been made inaccessible. Seemingly avoidable debacle.

Seems to me that you didn’t perhaps understand the issue. Way back in 2019 Microsoft and others were suggesting that no one use the SMBv1 ‘sharing’ protocol, as security vulnerabilities had been discovered - the Sonos Desktop Apps catered for bypassing SMBv1 by using the HTTP protocol instead and that was introduced around the time of the S1/S2 split in late 2020.

The vulnerabilities of SMBv1 were widely discussed in this community and elsewhere online and many users (myself included) persisted with SMBv1 for a while, relying on the security of the local network - but it wasn’t ideal. A lot went for HTTP sharing and I eventually upgraded my NAS to support SMBv2 and v3.

HTTP was eventually found to be vulnerable too, so in the new Sonos App, launched in May this year, support was dropped for HTTP (and of course there was no support for SMBv1 either). That meant all of us users sharing local libraries needed to switch the library sharing protocol to use SMBv2, or higher.

There are several guides in this community and in the Sonos Support pages of what needs to be done to setup such a share. Sonos even warned us about these things prior to the May App update. See attached.

There’s only so much hand-holding Sonos can do with the switchover to SMBv2 etc. I’m surprised that people had so much difficulty with this, as a lot of other companies like Microsoft, Apple, Amazon, Google etc. stopped supporting SMBv1 long ago and certainly much earlier than Sonos dropped their support for it.

Anyhow, the advice to any Sonos user is, if you can’t figure out how to switch your local library share to use SMBv2 or higher, having read the information available online (including the YouTube videos etc.) then it’s perhaps best to contact Sonos Support. Here is the link to do that…

https://support.sonos.com/s/contact

Here’s some initial links too, if anyone wants to read more on this topic on how to setup an SMBv2 (or higher) share to use with Sonos…

J

Jim600

Enthusiast I

5 months after the May update, invested many fruitless hours with first tier Sonos techs, finally elevated to a level of expertise resulting in renewed access to my music library( Mac laptop) and playlists in their entirety. Happy finally regaining that which never should have been made inaccessible. Seemingly avoidable debacle.

Seems to me that you didn’t perhaps understand the issue. Way back in 2019 Microsoft and others were suggesting that no one use the SMBv1 ‘sharing’ protocol, as security vulnerabilities had been discovered - the Sonos Desktop Apps catered for bypassing SMBv1 by using the HTTP protocol instead and that was introduced around the time of the S1/S2 split in late 2020.

The vulnerabilities of SMBv1 were widely discussed in this community and elsewhere online and many users (myself included) persisted with SMBv1 for a while, relying on the security of the local network - but it wasn’t ideal. A lot went for HTTP sharing and I eventually upgraded my NAS to support SMBv2 and v3.

HTTP was eventually found to be vulnerable too, so in the new Sonos App, launched in May this year, support was dropped for HTTP (and of course there was no support for SMBv1 either). That meant all of us users sharing local libraries needed to switch the library sharing protocol to use SMBv2, or higher.

There are several guides in this community and in the Sonos Support pages of what needs to be done to setup such a share. Sonos even warned us about these things prior to the May App update. See attached.

There’s only so much hand-holding Sonos can do with the switchover to SMBv2 etc. I’m surprised that people had so much difficulty with this, as a lot of other companies like Microsoft, Apple, Amazon, Google etc. stopped supporting SMBv1 long ago and certainly much earlier than Sonos dropped their support for it.

Anyhow, the advice to any Sonos user is, if you can’t figure out how to switch your local library share to use SMBv2 or higher, having read the information available online (including the YouTube videos etc.) then it’s perhaps best to contact Sonos Support. Here is the link to do that…

https://support.sonos.com/s/contact

Here’s some initial links too, if anyone wants to read more on this topic on how to setup an SMBv2 (or higher) share to use with Sonos…

Well, how patronising is that …… especially the “there’s only so much hand-holding Sonos can do”. Maybe if Sonos hadn’t enforced a new half-baked app on everyone with its plethora of changes whereby it became impossible for anyone (not especially) tech savvy to discern what was happening and why, user wouldn’t need their ‘hands held’ to get their hundreds (thousands?) of pounds of audiotech back working again!?

I

Ianp

Collaborator II

5 months after the May update, invested many fruitless hours with first tier Sonos techs, finally elevated to a level of expertise resulting in renewed access to my music library( Mac laptop) and playlists in their entirety. Happy finally regaining that which never should have been made inaccessible. Seemingly avoidable debacle.

There’s only so much hand-holding Sonos can do with the switchover to SMBv2 etc. I’m surprised that people had so much difficulty with this, as a lot of other companies like Microsoft, Apple, Amazon, Google etc. stopped supporting SMBv1 long ago and certainly much earlier than Sonos dropped their support for it.

As I’ve said before Ken, that is not correct, SMB1 is supported but not enabled by default in Windows/MacOS. What Sonos should have done was by all means use SMB2/3 but also keep support for SMB1 for older NAS devices which cannot be upgraded to the new SMB version(s). They could have included a disclaimer and pointed to security issues if the user selects SMB1. But they didn’t. Instead many Sonos users with perfectly working NAS units until now have to buy a new one that supports SMB2/3 (if they can’t upgrade the software), which seems an excessive and unnecessary expense.

Ken_Griffiths

As I’ve said before Ken, that is not correct, SMB1 is supported but not enabled by default in Windows/MacOS. What Sonos should have done was by all means use SMB2/3 but also keep support for SMB1 for older NAS devices which cannot be upgraded to the new SMB version(s). They could have included a disclaimer and pointed to security issues if the user selects SMB1. But they didn’t. Instead many Sonos users with perfectly working NAS units until now have to buy a new one that supports SMB2/3 (if they can’t upgrade the software), which seems an excessive and unnecessary expense.

It’s a new App - there is no way that any company would deliberately incorporate a vulnerability in their new software, or hardware. I can’t even find an App in the Apple App Store that supports SMBv1 - most developers have updated their Apps to support SMBv2 or higher and manufacturers like Netgear no longer support their SMBv1 NAS boxes. Also SMBv1 is not available for Windows 11 users.

Show more replies

Sign up

Login to the community