Audio cutting last 10-20 seconds of each song

Audio cutting out approx 17 seconds from the end of every track streamed from my local library.  I noticed if I pause during the silence, volume is restored for another couple of seconds and then cuts out again.

This is on simple playback of something on a strong local network.  That is BASIC functionality and now I can’t just sit back and listen to my extensive collection.  And in the meantime I complained to Amazon that my mp3 purchase is corrupted.

C’mon… this is embarrassing.

Here’s an anecdotal update: but ALL my Amazon mp3s from the last few months (since June) have this issue, and none of the mp3s I’ve converted directly from CD do.  I have at least 4 examples of each.

Later I am going to convert a CD I bought from Amazon and for which I downloaded the autorip version and that has the end-of-track blip, and see if the converted mp3 doesn’t...

I think there could be something to this. My observations this evening show that my Roam continues to play a silence at the end of (most/certain) local library files, but behaves fine with YouTube Music streams.

I have found some local library songs that play correctly, so it's not a blanket problem for me. Interestingly, within an album I have found an example where most tracks are fine but one consistently fails. 

I was wondering whether perhaps I had used some odd encoding settings in lame when first ripping these songs years ago - like, maybe it doesn't like VBR...? The trouble is, within an album I would not have changed such settings so I can't quite make that theory add up.

To add to the confusion, I've found that a stereo pair of Play:1 speakers can flawlessly play the local library files that glitch on the Roam. 

Definitely feels a bit buggy. At least this phenomenon does seem repeatable in my system so it ought to be fixable... eventually...? 

This happens to me with YTM songs as well

I may be lucky but I’ve not found an issue with YTM or Spotify - I’ve tried the same material that has the end silence issue in my local collection and those tracks play fine.

I looked into other differences between my recent Amazon MP3 and CD converted tracks and the Amazon ones are VBR, so I took a local Amazon-sourced track with the issue and re-sampled it to another VBR mp3 with the same metadata (but minus the copyright field). 

The new copy DOES NOT HAVE THE ISSUE and plays fine.

This track shows as 239mbps compared to Amazon’s 240mbps.  So this suggests it is not a problem with CBR vs VBR or sample rate.  It is limited to Amazon mp3s in my case.

Can confirm this is happening wired & wireless since the last update. Really makes me wonder what the heck the dev team is releasing. Like above, the S2 mess almost behind us, now this.

It must be something with the OS update since it also happens if i play my music via other software (like plexmediaserver, IOS app/windows) on my Sonos speakers.

Error log is empty and sending a diagnostic report as suggested by Stanley_4 should only be done upon request. So suggest the latest update is reversed asap till the root cause has been found and fixed. ( but that will be a request to deaf man's ears i am afraid)

Definately is not the music files itself since those play fine, issue arises if Sonos is part of the equasion.

Funny part here is that i keep getting emails to upgrade/extend my speakerset where i really am considering to swap platform.😂

A couple of months ago, I uploaded my library to I Broadcast. I loaded up a playlist and the same thing is happening, only not to all the tracks.  This year of updates has been a total disaster.

By the way, what other platforms are you looking at? I’m getting a little frustrated here as well.
 

HEOS is an option but it is still early days.

Dear sglickman,

thanks for reporting this problem, because I have a similar one. However, it appears only with my own music library which is properly linked to SONOS from a NAS device. It does not happen with all songs. But the audio signal stops exactly 10 to 11 seconds before the end of a song. The audio timer continues but the speakers a silent.

The problem occurs with ripped CDs in the library with older original issue dates. I am using SONOS for a couple of years as well. All ripping is done with the commercial available program dbpoweramp. I can solve the problem if I ripp the CD again with an actual Windows 11 media player. I have never recoginized the problem before, it occurs since the latest release of the SONOS APP or may be the latest speaker software 81.1-58074.

I would guess this is not a problem of the connectivity of your speakers. Since the response of the speakers to volume changes or some other commands gets better with the latest APP releases, may be the software buffers the audio signal in a certain way to let you thnik the response is faster and there are some strange effects with the MP3 coders… I am not an expert in those details. But I am quite confident it is still the software, which is driving us into madness since its first appearance May of this year. 

Hi,

I’m pleased to report that the update that came out this morning seems to have fixed the issue, on my local music library at least.

Please stop looking at the files or your network as a potential cause of this. The issue was caused by a Sonos software update and appears to be fixed by one also. Looking at other causes (even as directed by Sonos support) is a complete waste of time.

It’s so frustrating when a top end system can be made to fail so frequently with shoddy upgrades (I’m still lamenting the loss of a widget and lock screen info on Android). Hopefully things will work for a while  now.

Steve