My Sonos Beam (Gen 2) frequently makes a loud pop sound and then loses audio and restarts when playing Atmos content. My connected equipment is an AppleTV 4K (2022) and an LG OLED C2. All equipment has the latest firmware updates. Disabling Atmos does not seam like a reasonable fix since Atmos sounds is an advertised purpose of the Beam (Gen 2) and why I upgraded. Are there any things to try to resolve the issue?
This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
Userlevel 7
+22
Start here, skip to near the end if you are short of time.
Page 1
Page 40
Sorry to hear you’re affected. Come on over to the main thread and share your experience.
Userlevel 7
+18
Hi
Good news! We are pleased to share that our team has identified a fix for the popping sound on Arc and it will be shipped to all customers as part of a software release today, Thursday Nov 16 at 09:30 ET, 14:30 GMT, 15:30 CET. Please note that some app stores may take an extra hour or two for it to become available.
During our investigation we uncovered a rare bug that impacts how Sonos Arc and Beam (Gen 2) in certain home theater configurations process Dolby MAT, a streaming technology which is used to deliver Dolby Atmos audio over HDMI. Occasionally a Sonos product will receive a corrupted audio segment from an external source and needs to filter out unwanted audio data. The bug we identified was allowing our Dolby decoder to play audible errors on certain home theater setups rather than concealing them. The solution we’ve built and tested improves our Dolby decoder so it better filters out corrupt audio data that can manifest as a popping sound. We’ll continue to monitor customer feedback closely after the fix has been released and ship additional updates if necessary.
We strive to deliver the best listening experience possible and work to address major issues that impact our customers. We apologize for the disruption this bug has caused and want to thank you for your patience while our team developed a fix.
We would also like to thank our community users for their detailed setup information and steps to reproduce the issue, which were helpful to us in uncovering the cause of the bug.
If you have any questions, please post them on the main related thread and I’ll do my best to answer them.
This thread will be closed to keep all queries in that one place.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.