Metallic, tinny, resonant and distorted sound from the Sonos Beam gen 2 in voices / talking

No, I don’t. 
 

If it’s working in my two systems (Vizio and Samsung) without issue, along with the knowledge I have regarding networking, CEC, and other related technical issues, it’s fairly clear to me the problem isn’t with Sonos….generally speaking. In a large portion of my posts, however, I do caveat with a suggestion to submit a diagnostic, and a call to Sonos, the only way that I’m aware of to be certain it isn’t a hardware, or for that matter, software failure. When a grand majority of people are not posting that they’re experiencing the problem, but a handful are… logic dictates the issue is somewhere else.
 

What I’m not doing is denying that these folks are having an issue…that would be presumptuous. I am, however, trying to suggest that they may need to look further up the process line, rather than the Sonos, which is really pretty much a dumb device that does a little amount of processing. Nothing against the Sonos folks, but it’s just a speaker. If it works in 99% of cases, you do have to wonder what is different. 

That’s not correct. There is significant tech and processing that occurs on the Sonos and when there are dozens of threads with the same issue with the largest tv makers in the US (samsung, LG, TCL)  the issue points back to them. Also many have reported this started occurring AFTER a firmware update. I just wish Sonos would actually reply to these posts themselves with ticket numbers and issue updates instead of just ignoring these threads and leaving it up to the community to quibble amongst themselves without any actual data from the Sonos engineers. What’s the point of this community if Sonos never gets involved in the discussion. 

This is a community forum, user to user communication is the entire purpose. A few Sonos folks visit from time to time and we see some limited official support offered on a few topics.

Sonos support is handled by the Support department.

Has anyone had hope fixing this error? If this is a firmware update I’m not sure why Sonos does not roll it back it’s a shocking metallic sound it’s so obvious too. 
 

feels like they intentionally released it like this 

@Airgetlam it happens on Sony TVs, apple V boxes, virgin boxes, games consoles….the lot and there are many forums just like this speaking of the same issue. 
 

it’s a fundamental Sonos fault which they choose not to fix. 

I have the beam for almost a year now and had this issue start a couple of months ago. I spoke to Sonos support and they acknowledged this issue. Like someone else above said, they don’t have a fix or timeline for this.

They are sending me an optical adapter to see it still happens.

@fyrie its an issue with the left and right outmost speakers and optical adaptor/cable wont fix the issue. Also why spend 500 quid on something that does not utilise eArc capability?

Sonos I don't think will fix the issue. Its not in their best interests to do so…..they’ll give you a 30% voucher for your next purchase instead and leave you be….seems to be the sonos way 

@Jason.Ekwueme Unfortunately, I bought this beam over a year ago. The optical adapter came and the issue is still there.

Called support again and they told me there’s nothing they can do and that their engineers are looking into it with no timeline. Unfortunately, I have the whole surround sound with bass set up and would need to replace the whole system since I don’t feel confident in spending so much on Sonos again.

I wanna give an update. The issue seems to be resolved. I haven't noticed it in a week or so now.

I bought a pair of Eras to use as surrounds to sync with my beam. I had read online that this helps reduce the interference coming from the beam. This has helped improve things but has not solved the issue entirely. It definitely went against my better judgement to give Sonos more money to try solve for an issue they refuse to resolve themselves. Disappointed it hasn't been a 100% success. 

The one thing I find strange is that not all beam users are experiencing this issue, despite it being a result of a firmware update. Why the inconsistency?