Skip to main content
Streuner
Contributor II
October 31, 2024
Answered

New update - still no fix?

  • October 31, 2024
  • 11 replies
  • 370 views

First of all: I am not a native speaker, so please excuse any strange or humble expression….

 

Some days ago an update to the MacOS Sonos controller app appeared. Guess what: Still no fix regarding “My own library” hosted on a local (Mac) server still using iTunes and not Apple music.

 

While → any ← network related app can connect via → any ← network protocol Sonos still refuses to add the music library (error 913, wrong password / user, stopping adding the library and else). Even network rendering from 3D apps and video compression still work flawless, not to mention several “smart home devices” that work like a charm, too.

 

I refuse to use a NAS because of being in need of that MacOS server hosted on an Intel Mac Mini.

None of the following (modified for security reasons) connection types works:

 

\\IP1.IP2.IP3.IP4\Media\iTunes

\\itunes-server.a.well.known.router.device\Media\iTunes

\\itunes-server\Media\iTunes

\\itunes-server.local\Media\iTunes

\\iTunes-Server._afpovertcp._tcp.local\Media\iTunes

\\itunes-serverethernet.a.well.known.router.device\Media\iTunes

 

//itunes-server.a.well.known.router.device/Mediathek/iTunes

//itunes-server/Media/iTunes

//itunes-server.local/Media/iTunes

//IP1.IP2.IP3.IP4/Media/iTunes

//iTunes-Server/iTunes-Media

//iTunes Server._afpovertcp._tcp.local/Media/iTunes/iTunes Media

 

Of course SMB does work within regular finder surroundings (though not sure which SMB version works under the hood of Sequoia). The server is NOT connected to the internet in any way, just to the local network.

I remember Sonos promising having a look into this with possible results within October this year. It is the last day of October. So, Sonos, when is the next declaration regarding this disastrous “issue” to be awaited by long-time Sonos users?

Christmas is standing round the corner and I am thinking about getting myself new audio streaming and network connected speakers as my Sonos system is resting in silence for months by now like a dead body in a coffin. And Sonos speakers are not as decorative as for example IKEA-stuff Sonos once dealt with, too…

 

Sorry, could not keep my fingers still anymore.

 

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 Airgetlam

Have you called Sonos Support directly to discuss it?

It sounds to me like you may need to reset your library, following the instructions as explained in this thread,  but that’s just a guess. Calling in would confirm that, I’d think. And at the least, set you back on the correct path.

11 replies

Show previous replies
StreunerAuthor
Contributor II
December 10, 2024

Although I do not understand what actually has changed it seems I have found some sort of solution - and maybe the cause for all troubles.

After copying all my music files to a completely new drive and adding that to Sonos - nearly - everything works as expected.

First of all the direct connection to the Mac still does not work, that 913 error is existant. But now the networked use of that new drive seems to work. Adding that drive to the regular Mac OS file sharing went like expected, Sonos accepted the permission credentials - for what reason ever.

There are possibly two aspects that might (...) have caused all troubles, but as mentioned already I am not sure about this.

First of all the location of the music folder resides on a new drive, not at the regular path iTunes used to fetch up. In my special case my library is spanned by the Mac OS App “TuneSpan”. This app makes it possible to some sort of “relocate” very large iTunes libraries over several drives, not just the standard Mac OS startup volume. Before Sonos tried to get the library information from a folder called “iTunes Library” - note the space between the words of the folder’s name. I am just guessing that Sonos seems to have problems how to deal with non standard NETBIOS or SMB named folders - no matter what SMB version actually is used on a Mac running in Mojave. As said: Just a guess.

What I additionally noticed:

For some unknown reason there was another “Music”-folder within the regular iTunes Music folder the Sonos Mac OS App fetched up before that update. To explain this in deep a bit better: The german version of iTunes in Mac OS used to create a folder named “Musik” (note the “k”) to store music files. For some unknown reason I found another folder like that one. Within “Musik” (german) was another folder named “Music” (english). I do not know how this folder got there, not even when. Although this english folder exactly has the same permissions and network shares like the german one Sonos seems to stop any indexing process when it notices that english folder. Again: It’s just a guess.

Right now any music is stored within a new “Music” folder on a new drive, no other “Musik”- or whatever like folder in that one. Besides the 913 error everything seems to work now. But I have to re-add the whole iTunes library.

And then I can add new files that gathered within more than half a year of not being able to make use of Sonos...

Terms & ConditionsAccessibility statement