Skip to main content
September 11, 2024
Answered

My 20 year functional SONOS system is now throwing "incorrect encoding" error messages.

  • September 11, 2024
  • 16 replies
  • 409 views

After a long period of not frequently using my Sonos Play 5 Gen 1 based system I turned it on this morning to find that while I can DNLA MP3 encoded files. My 22,000 FLAC and AIFF encoded files are returning a “file not correctly encoded” error. For the last 20 years or so the system has worked absolutely fine. The last time I used it was Dec 2023. So I guess a recent firmware update is to blame.

All my music is stored locally I do not stream or own music purchased online.

Is there any common wisdom which I am missing on this matter which may guide me out of this situation ?

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 Anthony_531

Thanks Corry. I am scrambling around a bit here and I need to get through a few more bits of deduction to start to understand where my problem might be. This has all come as a bit of a shock as this has “just worked” for over 15 years,

OK SOLVED !!

The DNLA protocol relies on SSDP find the DNLA renderer SONOS devices. However the renderer requires that the DNLA server serves it in the correct format - this was my problem, some how the DNLA server which I use for SONOS had changed from:

Output Format → “Original” 

To

Output Format → “MP3 High Bandwidth when necessary” 

That was screwing it up.

I can’t get the Sonos S1 app to even see the music share at all. Weird.

Anyway back to Jriver Media Centre 20 and Jremote for me.

Cheers all.

16 replies

Anthony_531AuthorAnswer
September 11, 2024

Thanks Corry. I am scrambling around a bit here and I need to get through a few more bits of deduction to start to understand where my problem might be. This has all come as a bit of a shock as this has “just worked” for over 15 years,

OK SOLVED !!

The DNLA protocol relies on SSDP find the DNLA renderer SONOS devices. However the renderer requires that the DNLA server serves it in the correct format - this was my problem, some how the DNLA server which I use for SONOS had changed from:

Output Format → “Original” 

To

Output Format → “MP3 High Bandwidth when necessary” 

That was screwing it up.

I can’t get the Sonos S1 app to even see the music share at all. Weird.

Anyway back to Jriver Media Centre 20 and Jremote for me.

Cheers all.

Corry P
Sonos Staff
September 11, 2024

Hi @Anthony_531 

Good to hear you found the answer! Thanks for updating the thread!

Sonos S1 systems require SMBv1 to be available - perhaps that is why you cannot see your Music Library? On what kind of device is it stored?

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein
September 11, 2024

Yeah - that will be it - I removed it [SMBv1] - it’s a 2019 Datacentre edition box. Still works fine as a renderer - when fed via a DLNA server though.

Corry P
Sonos Staff
September 11, 2024

Hi @Anthony_531 

Can it run Plex? There is a Plex music service for Sonos - that would allow browsing from the Sonos app while bypassing the need for SMBv1. Or, if you have another device on the network that can run Plex and access the NAS, that would work too.

I hope this helps.

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein
September 11, 2024

Thanks Corry, that’s above a beyond and a rare thing in this day and age. 

I don’t have a requirement to access my music / or video outside my existing solution as the interface on that is perfect for what I need.

Thanks again.

Regards

Anthony.

MoPac
Headliner III
September 11, 2024

 This is a bit off subject, but then again not really.  It does have to do with tracks that will not play.  You don’t get the Encoding error instead the track has no album art and, if I remember correctly, the track name is displayed with the track number included In the name.
 

 The reason for this is some forms of the apostrophe are not accepted as a legal character.  It’s very hard to tell that it is different than the legal apostrophe, but if you look very closely you can see a slight difference in the angle.  I have had some downloaded tracks and ripped files that would not play because of this illegal apostrophe.  The solution is to replace it with the apostrophe on your keyboard at which point it will play.

 By the way… No other music playing software I have ever used rejected those tracks that were rejected by Sonos.