Key takeaways
- Most streaming audio dropouts trace back to Wi-Fi congestion between the streaming device and the router, not a fault inside the soundbar itself.
- A dropout that only affects bass or rear channels while dialogue keeps playing points at a wireless subwoofer or rear speaker link, not the streaming connection.
- eARC audio itself needs only around 37 Mbps of the HDMI 2.1 specification's much larger ceiling, so a physically solid basic cable usually beats an expensive one with a loose fit.
- If Wi-Fi, the wireless sub link, the HDMI handshake, the cable, and raw bandwidth all test clean, the fault sits in firmware or hardware, not in the stream.
The sound cuts for a beat, sometimes half a second, sometimes closer to two, and then resumes mid-word or mid-note. It is not the silence at the start of a scene. It is a specific, repeatable hole in otherwise normal playback, and it usually shows up on one streaming app more than the others.
Five things account for nearly every case of this, and they have a rough order of likelihood. Work through them in that order. The fix for a congested Wi-Fi channel does nothing for a loose HDMI cable, and a new cable does nothing for a wireless network that is simply overloaded at 8pm on a weeknight.
Wi-Fi congestion between the streaming device and the router
This is the most common cause by a wide margin, especially for a streaming stick or a smart TV app connected over Wi-Fi rather than ethernet. A 4K stream with Dolby Atmos or 5.1 audio typically needs somewhere between 15 and 25 Mbps depending on the service, and that number has to arrive steadily, not just on average.
The audio track itself is small, usually well under 1 Mbps for Dolby Digital Plus, so it is rarely the actual bandwidth ceiling that causes the drop. It is jitter: the router’s 2.4 GHz band getting briefly saturated by a phone, a smart plug, or a neighbor’s network, so the stream buffer under runs for a fraction of a second.
Test it directly. Most streaming apps, Netflix included, have a connection diagnostic in their settings menu showing recent throughput and drops. Run an ethernet cable to the streaming device for an evening if you can, and see whether the problem disappears entirely. If it does, the fix is ethernet permanently or moving the device to the 5 GHz band, which carries far less contention in most homes. The Wi-Fi Alliance’s own guidance on network planning explains why a crowded 2.4 GHz band saturates so easily once a few neighbors and a dozen smart home devices share it. For a wider look at what a stream actually has to carry, see how streaming audio formats differ from the discs they are based on.
A concrete case: in a two bedroom flat above a row of similar units, a Sonos Arc Ultra kept losing sound only on Friday and Saturday nights, right when neighboring Wi-Fi traffic peaked across the building. Moving the smart TV app onto the 5 GHz band and giving the wireless sub its own channel cleared the fault completely within one evening of testing, with no change made to the soundbar or the TV itself.
2.4 GHz interference hitting a wireless subwoofer or rear speakers
Plenty of soundbar systems, including the Samsung HW-Q990D and the Sonos Arc Ultra paired with a wireless sub, link the subwoofer or rear satellites back to the main bar over their own 2.4 GHz radio rather than a cable. That link shares spectrum with a lot of home Wi-Fi traffic.
The tell here is which part of the sound actually disappears. If dialogue and the front channels keep playing normally while the bass or the surround channels drop out on their own, the fault is unlikely to be your streaming connection at all. It is the sub or rear link losing sync for a moment.
Check by switching the router to a 5 GHz only band for a night, or by physically moving the soundbar’s wireless receiver a meter or two away from the router. How a soundbar actually uses Bluetooth versus Wi-Fi covers why these links behave differently under crowding, and it is worth reading before assuming a hardware fault.
HDMI ARC or eARC renegotiating mid-stream
Every so often the drop is not a network problem at all. HDMI carries a handshake between the TV and the soundbar over ARC or eARC, and certain firmware combinations renegotiate that handshake unprompted, muting audio for a second or two while everything resyncs.
This tends to happen more on some ports than others, and more with some source apps than others, because the handshake is tied to the audio format being requested at that moment. A useful test: does the picture also blink, or does the input briefly flash no signal at the same moment audio drops? If so, this is a handshake issue, not a network one.
HDMI handshake problems and how to clear them walks through the specific fixes, including forcing a fixed resolution or disabling HDMI-CEC on one device at a time to isolate which one is triggering the resync.
A loose, worn, or genuinely underspec HDMI cable
eARC audio needs only around 37 Mbps of the HDMI 2.1 specification’s much larger ceiling, so almost any certified cable carries the audio comfortably. The problem is rarely bandwidth. It is a connector that is not seated fully, or a cable that has been flexed and crimped behind a TV stand for three years.
A dropout caused by a physical connection tends to be irregular rather than rhythmic, and it often responds to nudging the cable at either end. Reseat both connectors fully, try the cable in a different eARC labeled port if the TV has more than one, and if you own a spare HDMI cable rated for 2.1, swap it in for an evening. A cable that measures fine on a bench tester can still fail intermittently once bent at the exact angle a TV stand forces on it, which is why swapping is a faster diagnostic than testing.
For the general pattern of periodic HDMI audio loss beyond the streaming context specifically, sound cuts out every few minutes covers cases that have nothing to do with an app at all.
An actual shortfall in internet bandwidth
This is different from local Wi-Fi congestion. Here the connection from your router out to the internet is dipping below what the service needs, not the local link between the router and the streaming device.
Because video and audio usually arrive as a single encoded stream, a dip in total throughput below roughly 15 to 25 Mbps for 4K, or around 5 Mbps for HD, stutters both together, and the audio hit is often what you notice first, since ears catch a break in sound faster than eyes catch a soft frame. How much internet speed Atmos actually needs lays out the numbers by service and quality tier.
Run a wired speed test at the router itself, not over Wi-Fi, to rule out your own network as the bottleneck. If the number sits consistently below what the app needs for its current quality setting, dropping to a lower quality tier is a fair short-term fix while the connection itself gets sorted with your provider.
- Run a wired connection test to isolate Wi-Fi congestion from everything else
- Note whether only bass or rear channels drop, pointing at a wireless sub link
- Watch for a picture blink at the same moment as an audio drop, pointing at an HDMI handshake
- Reseat, then if needed swap, the HDMI cable itself
- Check raw internet bandwidth at the router, not measured over Wi-Fi
Note the exact time a dropout happens for a few occurrences before calling support. A pattern, always at the same time of evening, always on one app, always during one kind of scene, narrows the cause far faster than a general complaint that the sound cuts out sometimes.
If none of these explain it
When Wi-Fi, the wireless sub link, the HDMI handshake, the cable, and the raw bandwidth all check out clean, the fault most likely sits in the soundbar or receiver itself, not anywhere in the delivery chain.
Try the same streaming app on a different device, a phone or tablet cast to the same soundbar, and try a different streaming app on the original device. If the problem follows the soundbar regardless of source, it is firmware or hardware, not streaming. Firmware updates: benefits and risks covers what to check before assuming the unit itself has failed, and when a factory reset is worth trying before a warranty call.
Questions readers ask about this
Different apps request different bitrates and buffering behaviour for the same content. An app streaming a heavier bitrate track can saturate a marginal Wi-Fi link that a lighter app never touches, so the same network can look fine on one service and unreliable on another.
In most cases, yes. Ethernet removes the 2.4 and 5 GHz contention responsible for a lot of the jitter behind short audio dropouts. A powerline adapter or a long cable run to the streaming device or smart TV is usually worth trying before replacing any hardware.
Yes. A wireless sub or rear speaker link runs on the same 2.4 GHz band as most home Wi-Fi, and losing sync briefly reads as a bass dropout while dialogue keeps playing normally, which gets misdiagnosed as an app or network fault far more often than it should.
Not for bandwidth. eARC audio needs only around 37 Mbps, well inside what any certified cable carries. What differs between a cheap and a well made cable is connector fit and shielding, and a loose fit causes exactly the kind of intermittent dropout that looks like a software problem.
No. Check the network, the wireless sub link, and the HDMI cable first, since those explain the large majority of cases. If all of that tests clean, a pending firmware update is the next step before assuming the soundbar or receiver itself has failed.
About the author
Rahul Gupta
Rahul Gupta has spent nearly a decade quietly wiring living rooms, testing soundbars in every awkward apartment layout imaginable, and untangling the kind of HDMI handshake problems that make people give up on Atmos altogether. He writes here about what actually works when you get the boxes home—not what the spec sheet promises. If a piece of gear on this site earns a recommendation, it earned it in a real room with real furniture, not a lab.
