Don’t know if this would make any difference as it sounds like you had this issue when all the speakers were connected via WiFi ( none connected via Ethernet ).  Question is… Did you turn OFF the wireless radio for the Play 3 after you connected it via Ethernet?  With the Play 3 radio ON did you try connecting all speakers to the SonosNet network?

hmmmm interesting… how can i tell if this is happening?

the Play:3 is set to Enable Wifi but how can I connect the other speakers to SonosNet?

@sglickman 

Are you playing songs from a local Sonos music library and the issue just occurs there?
Streaming doesn’t show this issue? 
If so, it might be a bug of the latest firmware update, because on DE community there were users reporting the same like you. One of them resolved the issue by resetting all Sonos products.

https://doitforme.solutions/blog/how-to-setup-sonos/#:~:text=Just%20plug%20exactly%20one%20Sonos,password%2C%20or%20set%20any%20options.

 I think if your wireless speakers are already connected to your home WiFi you have to reset the network then those speakers will automatically connect to SonosNet.  Not sure though because I’ve never used SonosNet.  You may need to investigate how to reset the network.  Don’t factory reset your speakers!

 Try what @Schlumpf suggested first.  

Unfortunately this is happening both for a local Sonos music library as well as streaming from YouTube Music.

Hi,

I’ve had exactly the same issue since updating Sonos last night. Not on Verizon and have decent and stable Internet connection.

I noticed the issue when playing music from my local library, but when I switched to Bandcamp the issue was occuring there also.

Switched to using Bluetooth to my Roam, but I now don’t seem to be able to to group this to anything else in the system, so even that work around doesn’t work.

Really frustrating that every time there is an update (which I apply in the desparate hope that it may bring Android widgets or now playing information in the phone status bar) it seems to cause problems rather than fixing them.

Hopefully there will be a fix release very, very, soon.

Steve

Any music I stream from my Library or any other source, cuts off the 10-15 seconds of every song. I’ve had Sonos for 10 years and have never had this particular problem  I tried all the Sonos fixes which, as usual, don’t work. This whole year of crappy software is really frustrating. I just want my Sonos to work right, like it did last year!

Same problem here with the last 10 or so seconds of every song played as silence. Tested on a Roam and a Play:1. Music files coming from local media library. Software version 80.10.06 on Android and speakers on 81.1-58074. Will do some more testing later with other services etc if there's time... 

Piling on… same issue.   Running system from NAS to Sonos Port to receiver/amp - hard wired.  Its an app issue.  Poking my eyes out

Speaking of app issues-I’ve had to keep my music library on a flash drive in order to add it to Sonos. I USED TO be able to add it from my hard drive on the PC. Happened last spring, has that been fixed?

https://en.community.sonos.com/controllers-and-music-services-229131/error-code-913-fixed-6897914

 Thanks to @zombiedropper this is much simpler and worked for me.  Just make sure your PC is set up to allow sharing then follow the @zombiedropper instructions.  You’ll need to use your PC login as well.

 If you use the Sonos PC app only the 3rd option ( Network device…. ) will work.  Sonos should remove the first two options from the PC app.

Is everyone here who is affected on Android? Or also someone on iOS?

I’m using a desktop and a laptop. Windows 10 and 11

Re: 10 second cut off.  I’m on IOS

Does anyone with this issue have Crossfade on?

Listening to an album from local library. 3rd song cut off, it’s weird though the song kept playing, just silence about 10 or 15 seconds. 4th song played fine. 

Sent a diagnostic. Will attempt to contact through chat when I get a chance. 

I tried it with the crossfade on and off-same thing

This started happening on my Play-1 Sonos speaker in the last week. Worked ok up to now. I only use a local music library on a Pi, Both the Pi and the Sonos respond reliably to pings so it isn’t a network problem. It is only the last 10 sec of audio on some songs, so it is a new bug. Crossfade is off.

Any debug info available on Sonos?  

Pleased to report that the grouping issue turned out to be that the Roam didn’t receive the update at the same time as the rest of the system so didn’t play with its updated peers.

Audio cutting out ten seconds from the end now seems to be intermittent and not on every track. Still makes playing from music library or Bandcamp unlistenable. Back to Bluetooth...

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.