Arc TV sound cuts in and out.

I would guess this patch uses some code spaghetti behind the scenes to compensate via a hard fix for issues with the Samsung interpretation of eArc - so this probably isn't the next software version that everyone will eventually get - as by then Samsung should have fixed the issue at source and this patch would become redundant.

there is also a small chance this patch would interfere with a samsung fix - so I appreciate Sonos taking this approach!

I will have to give them a call and try the Samsung patch because mine is still doing it and the only way to fix mine as of now is to unplug it and that usually fixes it for a week or so. Very frustrating after spending all that money on the 5.1 system. 

HDMI Arc is just a ‘soft’ industry standard. Making it work depends on good implementation on both sides. If Sonos can “patch” around something Samsung does, then that’s something they should do. Also, if Samsung is doing something that leads the interface to fail, well they should work on it, too.

Samsung and Sonos are both selling a capability. It’s the consumers view of what’s a working product that should matter -- not the companies’ view, especially when an industry standard feature they are selling that should work is not working at a reasonable standard of performance.

Having to unplug and replug a device frequently is just plain nuts. And, by the way, it’s not my TV that’s having to be power-cycled each time, it’s my Sonos Arc. Funny that I just “reset” the Arc and things work.

Presumably Sonos knows about all of its users that have put in reports through its tech support and this forum about the problem. They could try proactively communicating with us.

Meanwhile, there has been some chatter out there about a Samsung software update. Like one exists. My last couple of conversations with Samsung have resulting in them saying that the pushed software already on my TV is as current as what’s downloadable. I’m still waiting to see if Samsung pushes an update on its side. If Sonos is so convinced Samsung is not upholding the standard, maybe they want to sue them or something, to show they are serious and that Samsung’s misrepresentation is damaging them.

Also, if Sonos can prove Samsung is the problem, whey not empower the consumers with the evidence they need to take the steps available to them to be more persuasive with Samsung?

In looking at this message thread I sometimes feel like I’m reading a Dilbert cartoon.

I know most of us are hanging in, because we are otherwise impressed by our Sonos products. 

Sony can’t out with an update that resolved this issue with the Arc. It resolved my issue. Samsung should do the same. I used to think it was a Sonos issue, but I don’t believe that now. 

This might help those with a Samsung tv, taken from another Samsung topic.. 

I think my point is that Sonos is the more powerful advocate with Samsung to get this fixed, or if they are in a position to empower Sonos users with what they need to know to be more persuasive with Samsung, they control that information, too.

There is no reason we should just accept supposition. Just because one TV vendor had a problem they fixed, doesn’t mean all TV vendors are at fault, and Sonos is just a victim. I guess Sonos would know that, though, or at least have a point of view somewhere in their engineering or e-suite.

I will add the point that the problem doesn’t just occur “spontaneously” when the Samsung TV and Arc are already communicating successfully. It happens most often when the TV has been in a sleep or “art” or screensaver mode or after the TV has been turned off, and then is ‘turned back on’. And it only happens sometimes.

I spent more than enough time with both Sonos and Samsung tech support for them to know where to start looking to fix the problem. I bet others have, too.

We don’t even know if the problem can just be “fixed” in software. What if it’s hardware? 

However, maybe the tech support (seems to be more the case with Samsung) spends too much time recommending ideas that  have the effect of “blaming the user” (even if that’s not the intent) rather than really exploring the facts and getting things over into software and hardware engineering. For sure, prolonged support conversations leading nowhere do not help the users.

None of the hardware/software companies seem to get to the point of problems nearly fast enough these days, even the ones that try hard. More investment needs to be spent on better diagnostic tools that make tech support go faster.

Can’t just blame the hard working people who interface with us all. I found the Sonos people quite nice and concerned. Just helpless.

The PCM configuration suggestion is well-intended speculation, in my case. Neither Sonos or Samsung tech support saw that as a solution. I know I’m set up as directed by both manufacturers.

This might help those with a Samsung tv, taken from another Samsung topic.. 

 

This post is saying that pass-through fixed the audio lag (a separate, but frustrating, issue).  It doesn’t fix the audio cutting in and out.

Not in my case. Been there, done that. And that is not Samsung’s advised setting, in any event, based on my interaction with their tech support.

I wish I would have know this earlier. Just got my Arc System plus Samsung 85“ Q95T and I have the same drop out issues as everyone else here...and there is still no final solution/answer from Sonos. Unbelievable! After more than 4 months!