Foxis wrote:
You do not even appear to be experiencing the issue by your own description? Do you just hang around other threads defending Sonos for free? Hardly.
No, I’m not experiencing this issue, but it doesn’t mean that I would not try to help others here try a few things to perhaps try to resolve the issue. Oh and ‘yes’, it was all for ‘free’.
Ken, this one might be above your pay grade.
@Foxis may I ask what Sony TV you have?
A KD-55XE8505. I have toyed around with the various settings on the TV itself and on the Apple TV. Currently I have the TV set to not touching the audio format or compression and setting the Apple TV to change the format to Dolby 5.1 plus.
That has worked flawlessly before and been the best experience I could get out of the setup (as I can’t get Atmos to work through the TV since it lacks eArc).
Since the problem I have tried setting the Apple TV to not change the audio format (which just gives me PCM from the TV to the Arc) and fiddling with the Sony TV settings, none of which has helped.
If someone has any idea regarding settings on the TV or Apple TV 4K I would be happy to try them out, but as it stands I don’t think it will make a difference to the sound or the problem.
do you have any other sources or is it just Apple TV?
The TV itself and a PS4 and a PS5. When the problem occurs it remains on all of them, and even with music playback started with the Sonos app.
The system has to be manually hard restarted (powering down/up the Arc) or be asleep for a while (hours) for the problem to go away. After which it will return as soon as I pause, change media from the source (ie. switch content on the Apple TV) or switch source. The symptom can be:
- Total cutout
- Delay from the rears and sub
- Random short dropouts, to be followed by one of the above
Setup worked well before 14.6.
As others I link the problem to codec switches. For example, when playing a movie on the Apple TV I can see that the system receives Dolby 5.1, whereas moving back to the netflix menu (for example) will drop the system back to PCM and then up to Dolby 5.1 again once Netflix plays a trailer or a new series/movie. That switch (and any action that triggers a codec switch) will trigger the problem 90% of the time.
interesting. with my workaround on my TV I have “digital audio output” set to Auto 1 which in fact takes Stereo PCM and outputs it as Dolby Digital Plus 2.0 so with this current setup I’m always seeing Dolby Digital Plus 2.0/5.1 or Dolby Atmos (still DD+). I wonder if because its never switching to PCM in my case that's why it avoids the issue
I have the same setting. Auto 1 on the TV, and the Apple TV 4K set to change audio to Dolby Digital. I get 5.1 indicated in the Sonos App and all seems to be well. However, after some switching of content I can get the problem to appear.
On thing that never fails is to play a Spatial playlist via the Apple Music App on the Apple TV. Sounds awesome until I switch tracks or pause/resume. Instant trigger of the problem.
(And this is something I have been doing a lot prior to the 14.6 update, as Spatial Audio sounds awesome on the system. I really recommend it. Well, when the Sonos system works again...)
I’ve also emailed Chris Welch at The Verge (welch@theverge.com) to hopefully increase the visibility of this issue. I encourage others on this thread to do the same.
Hi Chris,
I am hoping to bring to your attention an issue that is affecting Sonos home theater users since the introduction of the 14.6 firmware on April 19th. This issue is a serious audio desync/dropout issue resulting in echoing of Subs and Surrounds attached to the Arc, as well as full drop outs. I and many others have suffered with this issue for over a month — an issue which makes my home theater system completely unusable given the only way to stop the echoing is to unplug my devices roughly every 10-15 minutes when attempting to watch a movie. There's a 20+ page thread on this issue here:
A Sonos engineer (Corry P) acknowledged the issue on May 2nd, only to walk that statement back 2 days later:
Edit, May 4th: Hi all, I was a bit premature with posting the original best answer message in this topic. While we have been investigating Topilouf’s issue, we have not seen an increase in surround audio errors and do not see anything that suggests that you all will experience the same issue following the recent update. If you do experience issues while listening to your Sonos system, we always encourage you to contact us and we will do our utmost to support you.
Hi All
Just to let you all know, we have now identified an issue whereby some Sonos Home Theatre satellites will experience audio interruptions after the latest 14.6 update.
We are investigating the situation and hope to resolve it soon. At present, we have no further information to share.
I hope this helps.
Since then, the only statement from Sonos has been that audio dropouts can occur and to contact support (James L. on May 23rd):
https://en.community.sonos.com/home-theater-228993/lost-surround-and-sub-after-update-6868561/index19.html?postid=16594139#post16594139
Hi all,
We understand the frustration any customer feels when your experience isn’t what it should be.
We equally understand the frustrations around and apologise for the recent communications that have led to confusion about the 14.6 update.
Please be assured that your listening experience, the sound quality, and the performance of our products is and will remain our absolute priority.
If you experience a dropout or any other issue on your system, please contact support with your diagnostic report from within 10 minutes of the drop-out occurring and we will look into it right away.
There are different reasons why drop outs may occur, and we want to make sure that we can help you.
Seeing as this topic is not resolved for those commenting, I have removed the ‘best answer’ until further notice.
Sonos customers have been struggling with this issue that has effectively made our home theater systems useless since the firmware update was released last month. We've spent countless hours talking to L1, L2, and L3 support staff and submitted countless diagnostic reports to no avail. Without direct acknowledgement of this issue, introduced in 14.6, there can be no certainty that it will *ever* be addressed. Since you've covered Sonos in the past at The Verge, I'm hoping you'd be willing to report on this issue as escalation through Sonos' normal customer support path appears to lead to a dead end. As for myself, I've moved on, making the painful decision to replace all of my Sonos hardware with Bluesound, but I still want to see this issue addressed for everyone else out there, especially those who may not even notice when their subwoofer drops out randomly.
Cheers.
just an update to my current workaround. for the time being I’ve been setting my Apple TV to “change format: dolby digital 5.1” and had eARC off on my TV in and this has avoided the issue thus far. for atmos content I would manually change the apple tv audio back to “auto”
yesterday I was tinkering around with my TV settings (sony a9g) and I discovered if I leave eARC off and turn passthrough mode OFF I can leave my Apple TV audio on auto and now get the source DD5.1 plus signal is correctly sent to sonos and atmos will play automatically as well. this is actually my ideal set up now as I didn’t really like how Sonos handles LPCM especially the lower volume. so while this bug is still not fixed it has actually lead me to a better set up for my preferences in my living room system. Obviously this only works for me because I exclusively use Apple TV in this room and now have no need for eARC
crossing my fingers I continue to not encounter the issue in my game room system
Thanks for posting this. I haven’t had a dropout in a few days but had this idea in the meantime. When I tried it though, atmos appeared blocked which didn’t seem correct to me. I probably just needed to do something to force an HDMI re-handshake. I’m going to put this idea back in the toolbox for next time
just an update to my current workaround. for the time being I’ve been setting my Apple TV to “change format: dolby digital 5.1” and had eARC off on my TV and this has avoided the issue thus far. for atmos content I would manually change the apple tv audio back to “auto”
yesterday I was tinkering around with my TV settings (sony a9g) and I discovered if I leave eARC off and turn passthrough mode OFF I can leave my Apple TV audio on auto and now get the source DD5.1 plus signal is correctly sent to sonos and atmos will play automatically as well. this is actually my ideal set up now as I didn’t really like how Sonos handles LPCM especially the lower volume. so while this bug is still not fixed it has actually lead me to a better set up for my preferences in my living room system. Obviously this only works for me because I exclusively use Apple TV in this room and now have no need for eARC
crossing my fingers I continue to not encounter the issue in my game room system
What I think happens is the Apple TV still sends multichannel PCM but the tv prefers re-encode to Dolby and transmit to Sonos. I was initially not liking the idea of all the extra processing that was happening but if this works, I think it’s a pretty small compromise. Interestingly when I was talking to Sonos support they said they usually recommend leaving the tv in some kind of auto mode rather than pass-through
just an update to my current workaround. for the time being I’ve been setting my Apple TV to “change format: dolby digital 5.1” and had eARC off on my TV and this has avoided the issue thus far. for atmos content I would manually change the apple tv audio back to “auto”
yesterday I was tinkering around with my TV settings (sony a9g) and I discovered if I leave eARC off and turn passthrough mode OFF I can leave my Apple TV audio on auto and now get the source DD5.1 plus signal is correctly sent to sonos and atmos will play automatically as well. this is actually my ideal set up now as I didn’t really like how Sonos handles LPCM especially the lower volume. so while this bug is still not fixed it has actually lead me to a better set up for my preferences in my living room system. Obviously this only works for me because I exclusively use Apple TV in this room and now have no need for eARC
crossing my fingers I continue to not encounter the issue in my game room system
What I think happens is the Apple TV still sends multichannel PCM but the tv prefers re-encode to Dolby and transmit to Sonos. I was initially not liking the idea of all the extra processing that was happening but if this works, I think it’s a pretty small compromise. Interestingly when I was talking to Sonos support they said they usually recommend leaving the tv in some kind of auto mode rather than pass-through
Could that introduce lag though? Dependent on the tv and how fast they can process and re-encode?
Could that introduce lag though? Dependent on the tv and how fast they can process and re-encode?
Latency maybe which could be a problem for gamers but audio and video should probably still be in sync I think. Something to watch maybe
The system has to be manually hard restarted (powering down/up the Arc) or be asleep for a while (hours) for the problem to go away.
This is interesting to me and I noticed this myself. i.e you cannot get your rears and subs back but if you leave it overnight (or a very long time) then it suddenly start working again.
I wonder what the Sonos system does in standby that could ‘reset’ the issue.
The system has to be manually hard restarted (powering down/up the Arc) or be asleep for a while (hours) for the problem to go away.
This is interesting to me and I noticed this myself. i.e you cannot get your rears and subs back but if you leave it overnight (or a very long time) then it suddenly start working again.
I wonder what the Sonos system does in standby that could ‘reset’ the issue.
One possibility is a refresh of the HDMI edid info. Makes me wonder if unplugging and replugging the HDMI cable from the arc would be a quicker way to clear a dropout than power cycling. Probably lots of other things get reset too
Hi all,
We understand the frustration any customer feels when your experience isn’t what it should be.
We equally understand the frustrations around and apologise for the recent communications that have led to confusion about the 14.6 update.
Please be assured that your listening experience, the sound quality, and the performance of our products is and will remain our absolute priority.
If you experience a dropout or any other issue on your system, please contact support with your diagnostic report from within 10 minutes of the drop-out occurring and we will look into it right away.
There are different reasons why drop outs may occur, and we want to make sure that we can help you.
Seeing as this topic is not resolved for those commenting, I have removed the ‘best answer’ until further notice.
I had a pre-arranged SONOS - Ampac call with higher level support after spending hours with regular support. I have submitted over 10 diagnostics. I have all the diagnostic numbers still.
I was informed I would hear back from support on May 10th after the issue had been discussed internally. Never heard back from support. No email, No phone call. Nothing. Details below. Kindly, tell me exactly how much more time I should spend talking to support. How should I proceed?
Date and Time: | Saturday, May 07, 2022 - 4:00PM EDT |
Preferred Phone Number: | XXXXXX |
Alternate Phone Number: | |
Confirmation Number: | G196288M |
Case #: | 03872226 |
Usually when the issue is escalated, you get a link and need to select a time slot and then a Level 2 engineer will call you at the nominated number. I was tricked initially but then finally didn’t let go of support until the link was sent on my email.
Usually when the issue is escalated, you get a link and need to select a time slot and then a Level 2 engineer will call you at the nominated number. I was tricked initially but then finally didn’t let go of support until the link was sent on my email.
Yes, what I posted were details from the email confirmation after selecting the time slot. I spoke to the engineer who called me at the stated time. I never heard back even though I was advised I would. As for whether it is a L2 or L3 it’s meaningless to me. It was however my second escalation i.e. the 3rd person I spoke to on the escalation chain.
So there is no way to rollback the update?
So there is no way to rollback the update?
THIS! How can something like this go on for so long? Sonos? Anyone? Respect to all of you who have kept your cool and decided to troubleshoot for a company that releases a bug into there system rendering their product unusable, but that’s not what I signed up for. I purchased what I believed to be a functioning wireless sound system. It isn’t. Full stop. Wait, IT WAS until 14.6. That’s what even more maddening. If I botched something at work and just walk telling my clients to figure it out, I wouldn’t have that job. Who would? Let’s not forget censoring a previous post with one of many diagnostic numbers in it. I have a call tomorrow with Customer experience person… I would prefer Patrick Spence.
Hi All,
An update on progress so far.
After my 2 hours + yesterday investigating the issue, I was contacted by an engineer today who has taken over the case. I would like to say that both the 1st line and Engineer have been very helpful, supportive and forthcoming. And I don’t mind spending the time if it means we can move forward.
I have some tests to run tonight to help fault-find the issue further. The current investigation is based around an error observed with CEC when the issue is triggered – and this is where the engineer wants to investigate further to assess whether it’s the TV, AppleTV or Sonos etc.
Although I do not know a lot about CEC more than the very basics, I do know that each time I switch between sources within Apple TV (i.e. going from Disney, to Amazon Prime to AppleTV+) my Panasonic will look like it has changed source fully. i.e. it will come up ‘HDMI1 + Atmos’ or ‘HDMI1 + DD’ etc on the screen like you have gone from HDMI1 to HDMI2. This is because I have Apple TV set to change based on the source signal via Match Dynamic Range and Match Frame Rate settings. Enabling these settings is logical as different films have different video encoding and you want to match that as best as possible.
This is early in the investigation so lets not jump ahead of ourselves, but I did want to keep you updated. I also feel this line of investigation has some merit. Not just because the engineer can see a CEC error, but also the symptoms a lot of us are reporting are based on moving between formats and this type of source change issue is not exclusive to Apple TV. It certainly could occur going from your PlayStation to you favorite native TV App.
As always, Ill keep you posted.
Regards,
Brad
First, I'd like to ask if I should be supplying a diagnostics report in this thread also or do they have enough as of now?
Secondly, there was an Apple TV update around the same time. I know what I'm saying is not fact, but it seems literally every single last TVos update I have seen has brought more problems than it fixes. Is everyone that is having these issues using an Apple TV?
First I'd like to ask, if I should be supplying a diagnostics report in this thread also or do they have enough as of now?
Secondly, there was an Apple TV update around the same time. I know what I'm saying is not fact, but it seems literally every single last TVos update I have seen has brought more problems than it fixes. Is everyone that is having these issues using an Apple TV?
Yes, the Staff have asked for diagnostic reports, if practical, within 10 minutes of the issue occurring and post it’s reference here and to just outline what happened or contact Sonos Support, particularly if it persists and is easy to reproduce the issue.
I also understand about your reference to the Apple TV O/S updates, a few Samsung TV users here in the community, I noticed, seem to have had some HT audio interruptions and the ones I read recently all had an Apple TV 4K, but it might just be a coincidence, as it is quite a common device to have connected to a TV nowadays.
First, I'd like to ask if I should be supplying a diagnostics report in this thread also or do they have enough as of now?
Secondly, there was an Apple TV update around the same time. I know what I'm saying is not fact, but it seems literally every single last TVos update I have seen has brought more problems than it fixes. Is everyone that is having these issues using an Apple TV?
In essence, you should be submitting a diagnostics and then call Sonos Support to report (and fault find) the issue. Be warned, information collecting can take 2 hours.
On the second point, I am pretty sure there are people on this forum that do not own an AppleTV and still have the issue. So it does not seem exclusive to AppleTV owners.
there’s a new update out. I haven’t installed it yet. 14.8
So there is no way to rollback the update?
THIS! How can something like this go on for so long? Sonos? Anyone? Respect to all of you who have kept your cool and decided to troubleshoot for a company that releases a bug into there system rendering their product unusable, but that’s not what I signed up for. I purchased what I believed to be a functioning wireless sound system. It isn’t. Full stop. Wait, IT WAS until 14.6. That’s what even more maddening. If I botched something at work and just walk telling my clients to figure it out, I wouldn’t have that job. Who would? Let’s not forget censoring a previous post with one of many diagnostic numbers in it. I have a call tomorrow with Customer experience person… I would prefer Patrick Spence.
Please take it to social media. No other alternative I can think of to expedite the process. It’s shameful from Sonos as a brand and their reputation has taken a blow. 35 days since the issue, so many diagnostics and an ongoing case to no avail. I tweeted Sonos and Patrick spence so many times but they don’t bother responding! Not sure who to reach and what to do to expedite, my patience is growing thin. Stuck with a bricked system!
there’s a new update out. I haven’t installed it yet. 14.8
I don’t want to be a party-pooper, but I suspect there is nothing in that release related to fixing our issue. (I am basing that on the current fault-finding and what the Engineer is directing me to test).
there’s a new update out. I haven’t installed it yet. 14.8
Wow mate, how are you so updated on updates Sonos releases? Let us know how you go, personally I haven’t heard from L3 engineer at Sonos confirming the fix
there’s a new update out. I haven’t installed it yet. 14.8
I don’t want to be a party-pooper, but I suspect there is nothing in that release related to fixing our issue. (I am basing that on the current fault-finding and what the Engineer is directing me to test).
This would have been easy to diagnose provided the diagnostics we have provided but let’s be hopeful since I have lost all faith in Sonos development team and wishing for this to be fixed asap. It’s taking eternity to fix this problem and the pooper is that there is no rollback option available
@peterbault - are you going to take the plunge and install?
Hi All,
An update on progress so far.
Thanks, this is the most encouraging update I’ve heard. Please let us know how you continue to make out if you’re able. Makes me feel like Sonos is taking this seriously and at least looking in the right direction. Seems totally plausible based on my observations.
@peterbault - are you going to take the plunge and install?
I’ve installed it - S2 14.8 app version and system version. In the short time I’ve been running it everything seems OK, but I don’t have an Arc, just a Beam 2, 2 One’s, Sub and haven’t been experiencing the problem discussed in this thread.
Fingers crossed it helps those suffering with the problem.