Skip to main content

I am now begining to have doubts over my investment in Sonos

Having suffered at the hands of appgate since the last update I now have the following issues which I beileve are linked

 

On my Windows Desktop I get

stream.mp3

The song is not encoded properly

 

On my iPhone

When I select an album and hit play nothing happens

the play button disappears and is replaced by a spinning symbol

Then the play button comes back and if I hit this enough times, after a delay in plays

 

My frustration with growing. It seems to go from one issue to another.

 

Sonos Controller for PC

v16.4.2

Sonos OS S2

Build 81158074

Iphone

v16.4.4

Build 81.1.58210

 

No changes to my system or network apart from the recent updates

Did not have the problem before the update

Previously I totally reconfigured my home network and have no issues with it

 

Steve

 

 

What are you actually playing? One of the 100 music services, or local library, or line-in, or something else?

Hi ​@Steve251, 

Like ​@controlav asked, how are you playing to your Sonos system? Troubleshooting each method would generally be different, so knowing where it’s going wrong will help us provide the correct troubleshooting steps.

So I don’t leave you with nothing, it’s previously been noted that the “not encoded correctly” message can be caused by packet loss errors on your network. The following thread has helpful information and advice on how to resolve this: 

I hope this information helps!

What are you actually playing? One of the 100 music services, or local library, or line-in, or something else?

Sorry  I have been away

 

It happens when I stream Apple music but having said that since I got back yesterday it seems to be behaving

 

So I will monitor it

 

Steve

Hi ​@Steve251, 

Like ​@controlav asked, how are you playing to your Sonos system? Troubleshooting each method would generally be different, so knowing where it’s going wrong will help us provide the correct troubleshooting steps.

So I don’t leave you with nothing, it’s previously been noted that the “not encoded correctly” message can be caused by packet loss errors on your network. The following thread has helpful information and advice on how to resolve this: 

I hope this information helps!

I ran a packet test and no loss but of course that is a snapshot in time

I have been away and it seems better now and has stopped doingit

It only started after the last update

 

I shall monitor and see but I am away again from tomorrow until Wednesday

 

Appreciate your answer

 

Steve

Hi ​@Steve251, 

Like ​@controlav asked, how are you playing to your Sonos system? Troubleshooting each method would generally be different, so knowing where it’s going wrong will help us provide the correct troubleshooting steps.

So I don’t leave you with nothing, it’s previously been noted that the “not encoded correctly” message can be caused by packet loss errors on your network. The following thread has helpful information and advice on how to resolve this: 

I hope this information helps!

 If it’s a network error (packet loss) why doesn’t the error state that rather than Not Encoded Correctly.

 I can picture some poor person converting files trying to get them to play because surely they have the wrong codec.

I ran a packet test and no loss but of course that is a snapshot in time

I have been away and it seems better now and has stopped doingit

It only started after the last update

 

I shall monitor and see but I am away again from tomorrow until Wednesday

Hi ​@Steve251, thanks for reaching back out.

Since it’s with Apple Music, I can see that we are aware of an issue where uploaded tracks give that error message. The message only seems to occur when you Browse for a track (when you go into the service under Your Services) and not when you use the search bar to find the track.

I suggest you keep monitoring for now but to contact our support team for further troubleshooting and assistance if the issue returns.

 

 If it’s a network error (packet loss) why doesn’t the error state that rather than Not Encoded Correctly.

 I can picture some poor person converting files trying to get them to play because surely they have the wrong codec.

It’s a generic error message, and not a great one at that. It can show up when a track has DRM, when the file is corrupted, but also when the decoder fails to decode an incorrectly encoded stream. When it does this, it is noticed that the data is corrupted and the ‘Not Encoded Correctly’ error shows.

I know our team are working on better error reports and messages so hopefully we see this one gone or at least changed in the future with something like "corrupted audio data due to lost packets" or similar in place of it.

Reply


Terms & ConditionsCookie settings