Multichannel PCM 5.1 dropping out since 14.10 update


Userlevel 1
Badge

Anyone else experiencing the same issue? Multichannel PCM 5.1 blanks out for a second every 1-2 minutes. I don’t think it’s a bandwidth issue as it works flawlessly with Multichannel PCM 7.1 (thorough test) and Dolby TrueHD Atmos (quick test). And it may have been caused by the Sonos 14.10 update. Setup is PS5→ LG C1→ Beam 2 (via earc).

 

2 weeks ago before the 14.10 update, I watched a bluray film wherein I had my PS5 transcode the DTS-HD MA 5.1 audio to Multichannel PCM 5.1 (as the C1 does not support DTS) and had no issues. Earlier today, I played a bluray film for the first time in 2 weeks and I encountered consistent audio dropouts every 1-2 minutes. It had the same setup where DTS-HD MA 5.1 → Multichannel PCM 5.1. I tested other bluray discs including the one I watched 2 weeks ago and they all now have the same issue.

 

Curiously, I’ve been gaming heavily on my PS5 the past two 2 weeks and haven’t had any audio issues. Then I realized that I’ve been using Multichannel PCM 7.1 when gaming on my PS5. So I made some changes under the PS5 sound settings to make it output Multichannel PCM 5.1 instead. Lo and behold, I am now getting the same consistent dropouts in games and even on the PS5 main menu.

 

I think it’s due to the Sonos 14.10 update as that’s the only firmware update I’ve done in the last 2 weeks. No PS5 update, no LG C1 update. Well actually while I was composing this post, I received and applied the latest LG C1 firmware update and I still have the same issue.

Corry P 9 months ago

Hi @throwawaybeam2 et al

We now recommend you reach out to the TV manufacturer (LG) as this behaviour is also occurring with different soundbar manufacturers (so it’s not a Sonos-specific issue).

Alternatively, please utilize different audio formats from McLPCM 5.1 (e.g., McLPCM 7.1, DD+, etc).

I hope this helps.

View original

458 replies

Userlevel 3
Badge +2

For me the problem has not returned since I solved it by turning off that LG feature I previously mentioned, even with multiple power cycles. But I’m not using an AVR.

Had several power outages for a few consecutive days and now the problem has returned after being gone for about a month.

This is so frustrating, and neither Sonos nor LG seem to care.

I’m on LG G2, so it’s definitely not limited to the C1.

Userlevel 3
Badge +2

Back again for me, this is becoming a complete deal breaker now.

 

Please, please Sonos can we get some kind of acknowledgement of this @Corry P, it’s been near the top of these forums for 6 months now with a wide variety of users reporting the exact same problem on the same hardware - surely an easy one to replicate?

Userlevel 3
Badge +2

For me the problem has not returned since I solved it by turning off that LG feature I previously mentioned, even with multiple power cycles. But I’m not using an AVR.

Had several power outages for a few consecutive days and now the problem has returned after being gone for about a month.

This is so frustrating, and neither Sonos nor LG seem to care.

I’m on LG G2, so it’s definitely not limited to the C1.

Ok so twice more I have been able to make it go away. I don’t know how but it definitely involves turning QuickStart+ on then turn off the tv, wait a few minutes, turn on tv wait a while, turn off QuickStart+ then start playing randomly with every setting related to sound (simplink, passthrough to pcm or auto, bitstream to pcm, turn on and off eARC repeatedly etc). Then turn off tv, wait a while, turn it back on and leave it on some screen playing music (for example Home Screen of ps5). Then this error just goes away after a while and doesn’t return unless there’s another power outage. I know it sounds like total voodoo and hand waving but it already worked 3 times for me. I’m even wondering if my actions actually have any effect or it’s simply time passing that fixes it but anyway that’s all I have for you so take it for what it is and I hope it helps. The method is a bit random but the results are consistent and stay fixed.

Userlevel 3
Badge +2

Seems odd that power cycling the Beam reverts to the dropouts, but does power cycling the TV? Is there some sort of HDMI negotiation that happens only when the Beam powers up versus pulling the HDMI cable?

It’s also odd that I can hot swap another eARC device but only the Beam has the dropouts, as if the the buggy state is in the Beam, or the LG is remembering devices that have previously negotiated on power up (or the two devices are just using somehow different flavours of PCM 5.1 on the wire, hard to tell just by trusting the status labels of the vendor’s apps).

I just noticed that there is a new firmware for LG C1 and a new Sonos update, I won’t be home for a while so I can’t test, did it solve the dropouts by any chance ?

Userlevel 3
Badge +2

I just noticed that there is a new firmware for LG C1 and a new Sonos update, I won’t be home for a while so I can’t test, did it solve the dropouts by any chance ?

I don’t see a new update, was it 14.2? 

Seems odd that power cycling the Beam reverts to the dropouts, but does power cycling the TV? Is there some sort of HDMI negotiation that happens only when the Beam powers up versus pulling the HDMI cable?

It’s also odd that I can hot swap another eARC device but only the Beam has the dropouts, as if the the buggy state is in the Beam, or the LG is remembering devices that have previously negotiated on power up (or the two devices are just using somehow different flavours of PCM 5.1 on the wire, hard to tell just by trusting the status labels of the vendor’s apps).

I’ve only noticed when power cycling the beam - basically whenever there is a software update. Power cycling the TV often fixes it actually. 

I just noticed that there is a new firmware for LG C1 and a new Sonos update, I won’t be home for a while so I can’t test, did it solve the dropouts by any chance ?

I don’t see a new update, was it 14.2? 

Sorry for my mistake, it was not a sonos update but just a new LG firmware (03.30.16).

Okay so I recently bought myself a Sonos Beam Gen 2 and have only had it for a little over a week. I bought it specifically for my LG CX TV and my PS5 and did a lot of research on how to set it up and what settings to enable etc.

TV settings enabled: SIMPLINK, HDMI ARC, eARC, Pass Through, Bitstream

For a while in the PS5 settings I was running on the ‘Soundbar’ setting thinking that was the “correct” one until I realised that it was reporting Multichannel 7.1 PCM in the Sonos app, so I did a little digging.

After my digging I landed these settings (supposedly they’re better): AV Amplifier, 5.1, Linear PCM. I noticed this cutout issue pretty much immediately considering up until then I never had the problem and initially fiddled with settings to isolate the problem. Everything with any combo of settings works except for when I’m on 5.1 and when the app reports Multichannel 5.1 PCM. This is what lead me down the rabbit hole on researching the issue to find this thread which has helped me in at least the fact that I’m not the only one. I read through the thread and tried some things people said alongside my own testing, which is what I’ll explain below.

What I did first was turn off QuickStart+ as someone suggested earlier in this thread, which unfortunately on its own didn’t fix the issue, so I’ve kept it off anyways from hereon (so I’m not sure if this contributed to my final result 100% but it’s worth noting). After a lot of testing and fiddling with a lot of potential solutions people have proposed in this thread (like the new LG firmware/WebOS update through software update in settings) I was about ready to give up when I remembered that I had never turned off my PS5 *in* 5.1, only in 7.1. Thinking that *maybe* with QuickStart+ off and turning everything off and on again and allowing it all to start in 5.1 instead of switching it whilst it was already on might work and funnily enough it did, with the app also reporting the correct Multichannel 5.1 PCM. For extra insurance for it possibly being a fluke I gamed for hours with no cutouts and over the cause of a week or so it has been okay.

For extra measure what I do now is turn the PS5 on and allow it to fully start (the light going from orange/blue to white) before turning on the TV as what I noticed during my testing is when turning them on in a different order or whilst one is turning on at the same time would reproduce the issue of the cutouts. I’m not too technical as to why this may be the case but maybe it’s the ARC/eARC connection/handshake between the devices getting confused or something? For context I have my PS5 connected directly to the TV through HDMI4 and the TV to the soundbar through the HDMI2 port (ARC/eARC) port.

Hopefully this helps someone but if not maybe my post can push forward this issue to Sonos to eventually fix this for good.

TL;DR for my post: what fixed it for me is turning off QuickStart+, enabling AV Amplifier 5.1ch in the PS5 menu and turning the PS5 and TV off. When wanting to use your PS5, allow it to fully turn on before turning on the TV.

Userlevel 3
Badge +2

 

TL;DR for my post: what fixed it for me is turning off QuickStart+, enabling AV Amplifier 5.1ch in the PS5 menu and turning the PS5 and TV off. When wanting to use your PS5, allow it to fully turn on before turning on the TV.

A lot of people have seen that this fixes it temporarily but it does eventually return, seemingly whenever the beam is restarted. You could maybe test this and confirm? 

Badge

LG C2, Beam Gen 2 and two play1s.

Getting same drop outs with PS5 set to amplifier and 5.1. App read smultichannel pcm 5.1.

No dropouts on any other format.

When setting PS5 to soundbar, App reads multichannel pcm 7.1, no dropouts. 

Should I just keep 7.1 Sounds OK to me?

Would be nice that after sending £1000,'s on a system it would work as intended.

Userlevel 1

I can also confirm this issue; LG C2 and Beam Gen 2, both with the latest firmware updates.

I experience this with my Nintendo Switch set to surround (reads as PCM 5.1) as well as the PS5 manually set to PCM 5.1 (same as the previous poster).

It’s not a huge problem for me personally yet as I am currently essentially stuck to stereo anyway (although I guess the Beam at least makes proper use of the center channel when downmixing 5.1). But I was planning to buy some One SL speakers later this year and set them up as surrounds, so it would be sad if this issue couldn’t be fixed.

Asides from the posts here, a quick search brings up many Reddit threads describing this bug with the LG TV + Beam combination and given how popular these choices are with consumers I am very surprised that neither LG nor Sonos seems to be looking into it properly on a larger scale (or if they do, they aren’t communicating it).

Same exact issue here, PS4 + LG C1 + Beam 2 with Symfonisk Bookshelf surrounds. I've been following this topic for 2 months now hoping for a solution, but since Sonos is showing no sign of solving it I guess I'll add a comment too. I just don't get how this isn't a bigger priority for them? Playing a large portion of Blu-rays on one of the most common TVs is not possible because of this.

I'm just wondering what the most effective way is to let Sonos know how common this issue is. Should I make a separate support ticket for myself?

I have the same issue. Experiencing audio dropouts repeatedly when playing back an LPCM 5.1 track. My setup consist of an LG C1 + Beam 2 with IKEA Symfonsik rear speakers. As a player I use an Nvidia Shield and a PS5. I’m affected when I play games or when watching a movie via Plex that has a DTS / DTS-HD MA soundtrack (which then gets transcoded to LPCM due to the C1s inability to pass through DTS).

 

The only thing that sometimes helps to resolve this is unplug the TV, wait for 2 minutes, and then start it again. It’s mind boggling to me that this issue has been reproduced by so many and is not getting fixed or at least acknowledged. 

Userlevel 3
Badge +2

It’s mind boggling to me that this issue has been reproduced by so many and is not getting fixed or at least acknowledged. 

I had a playbar and then a Gen 1 beam for many years of faultless performance. I upgraded to the gen 2 beam to get the benefit of eArc and Atmos but Ive spent more time on these forums and elsewhere since then than I have actually enjoying it.

If a TV flashed on and off every minute who would tolerate it? perhaps there are hardware flaws that can’t be fixed? I hope I’m wrong but my next audio purchase is unlikely to be Sonos, a stereo pair of the new HomePods is looking tempting now.

Userlevel 3
Badge +2

It’s mind boggling to me that this issue has been reproduced by so many and is not getting fixed or at least acknowledged. 

I had a playbar and then a Gen 1 beam for many years of faultless performance. I upgraded to the gen 2 beam to get the benefit of eArc and Atmos but Ive spent more time on these forums and elsewhere since then than I have actually enjoying it.

If a TV flashed on and off every minute who would tolerate it? perhaps there are hardware flaws that can’t be fixed? I hope I’m wrong but my next audio purchase is unlikely to be Sonos, a stereo pair of the new HomePods is looking tempting now.

I wholeheartedly agree. The silence on Sonos’ side is deafening.

Looks like this will be swept under a rug.

I have also been looking into this problem for a while and I just found this thread, knowing that I am not the only one experiencing this issue.

 

Let’s begin with my setup:

LG CX (eArc on, passthrough, bitstream)

HDMI 1: Intel NUC 11

HDMI 2: Sonos Beam (Gen 2)

HDMI 3: PS5

HDMI 4: Nintendo Switch

Sonos Beam (Gen 2) + Sonos Sub (Gen 3) + Sonos One x 2

 

I didn’t realize the problem when I was using PS5 as I made the setting in PS5 as “soundbar” rather than “AV Amplifier” at the beginning. I first noticed the problem when I was playing with Nintendo Swtich instead, when I change the sound output to “PCM 5.1” after my purchase of Sonos Sub (Gen 3) + Sonos One x 2. Then, I tried to figure out which part is going wrong by looking into whether my PS5 could have the same issue. And all of your should have expected that with Multichannel PCM 5.1, dropping out did occurred. But for me, it was fine as I could just leave the setting as 7.1 and I don’t really care about the sound effect of Nintendo Switch.

Here comes some extra things I would like to add. Recently I have plugged my Intel NUC 11 into my LG CX via a Type C to HDMI 2.1 cable to enjoy 4K 120Hz experience. I then noticed that the dropping out thing occurred as well. The strange thing is that it happens not only to video playback at PCM 5.1 but any sound output like the music from Spotify. I checked the Sonos App and it displayed as Stereo while dropping out kept occuring (in fact, no matter what format of sound it shows, dropping out persists). I then went to the sound output settings page in Windows 11 and found that there are a few options for me to choose from. The default setting was 16-bit 48000Hz, where dropping out occurred. I tried all options available and found that with with 16-bit 44100Hz and 24-bit 44100Hz, no more dropping out of sound. I am not an expert in this area, but I guess some of you may know more about these. I suspect that the dropping out is highly related to the Hz that by some reason, the combination of Sonos Beam (Gen 2) + LG OLED CX (or similar models) is not unable to process 48000Hz sound output, causing the dropping out of sound. Perhaps the Multichannel PCM 5.1 is using this 48000Hz, casuing the issue (I am totally not sure about this). But I guess this information would be useful for us to solve this issue.

Besides, one thing to add is that I would normally make use of the native “Photos and Videos” app in LG CX for 4K movies playback, but never experiencing any past experience of sound dropping out. Thus, I am not sure if this problem may be related to LG CX’s ability to passthrough?

 

Hope these can help tackling the problem.

Userlevel 3
Badge +2

The transfer through the CX definitely is 48Khz but I haven’t checked if other formats are different. 
 

Issue has returned for me again today, if the next software update doesn’t fix I will be trying to return to the retailer for a refund. Really disappointed that @Corry P has just stopped replying when it became clear that simple fixes weren’t solving the problem, what is the point of this forum

The point of this forum, as indicated by its title at the top of the page, is a ‘Community Forum’, and not a ‘Sonos Support’ Forum.

If you want to talk with Sonos Support directly, I would recommend that you call them, rather than relying on a forum moderator to act as a Support person.

If you’re to go to the bottom of this page, and click on ‘Contact us’, you’ll find instructions on how to do so,

Userlevel 3
Badge +2

The point of this forum, as indicated by its title at the top of the page, is a ‘Community Forum’, and not a ‘Sonos Support’ Forum.

If you want to talk with Sonos Support directly, I would recommend that you call them, rather than relying on a forum moderator to act as a Support person.

If you’re to go to the bottom of this page, and click on ‘Contact us’, you’ll find instructions on how to do so,

Already have, like many others on the thread

Userlevel 3
Badge +2

Updated to 15.1, audio dropouts immediately return on PCM 5.1 only, I watched the HDMI diagnostic screen in the CX but see no errors or changes that correspond to the drops.

Submitted diagnostic 2038434149 if it helps but I’m going to look at alternative systems now 

Userlevel 3
Badge +2

Updated to 15.1, audio dropouts immediately return on PCM 5.1 only, I watched the HDMI diagnostic screen in the CX but see no errors or changes that correspond to the drops.

Submitted diagnostic 2038434149 if it helps but I’m going to look at alternative systems now 

Same experience on 15.1 for me too.

Occurred to me whilst testing the other eARC device that I now have the start of a different multiroom ecosystem in the house, one with extra inputs in the soundbar that would be useful for my legacy analogue devices... 

There’s been zero indication anywhere that this software release was intended to fix this particular issue. 

Userlevel 3
Badge +2

There’s been zero indication anywhere that this software release was intended to fix this particular issue. 

So what? Wouldn't “Bug fixes and performance enhancements” cover it?

Possibly, sure, but you’d think an issue with a six page thread might get more attention than being lumped in with that generic of a statement. 

Reply