Why sound from a Studio Display cuts out after a few seconds

Audio that plays for a few seconds through a Studio Display's speakers, then cuts out, sometimes worse once two displays are combined into one output, is a known, widely reported issue. It shows up repeatedly across Apple's own Support Communities, MacRumors forum threads, and enthusiast communities like Roon Labs', not just on one person's Mac.

If you have hit this, the first thing worth knowing is that nothing about your setup is unusual. It is documented on single Studio Displays as well as paired ones, across different Mac models and different macOS versions, in threads going back years. That does not make it any less annoying, but it does rule out the instinct to blame your own unit, your cable, or something you configured wrong.

Is this a known problem, or is my Studio Display faulty?

It is a known problem. Search Apple's Support Communities for Studio Display audio and you will find the same complaint repeated by different people: sound plays, sometimes with a brief crackle or scratch, then goes silent after a couple of seconds. The same pattern turns up on MacRumors forum threads and in the Roon Labs community, where members use Studio Displays as part of a wider audio setup and have compared notes on it for years. None of that amounts to an official diagnosis, but it is enough independent reporting, across enough different Macs, to say with confidence this is not one faulty display.

What none of these communities, or Apple, have published is a precise technical explanation of the underlying cause. That distinction matters for the rest of this guide: what follows is the general explanation people commonly point to, not a confirmed internal mechanism.

What's actually causing it?

Each Studio Display carries its audio over its own separate Thunderbolt or USB-C link, driven independently of any other display connected to the Mac. A single display on its own just has to keep that one link running. Combine two displays into one output, whether through a Multi-Output Device in Audio MIDI Setup or an app that builds the same kind of group, and macOS has to keep both of those independent links sample-locked together so the audio stays in sync between them.

The general explanation commonly given for this class of dropout is that this sample-lock between two separately driven links is more fragile than a single device running on its own, and that a small clock drift or renegotiation between the two can be enough to drop the audio path. That is a reasonable account of why pairing two displays seems to make the problem show up more often, but it is worth repeating: Apple has not published a detailed root-cause explanation for this specific symptom, so treat this as the widely cited general mechanism rather than a verified one.

How do I stop it from cutting out?

None of the following is an Apple-endorsed fix, since Apple has not published one. It is what people report as reducing how often the dropout happens, based on the same forum threads referenced above:

• Rebuild the Multi-Output or Aggregate Device from scratch. Delete the existing one in Audio MIDI Setup and create it again, rather than reusing one that has already dropped out once. A group that has been sitting since a previous session seems more prone to failing again than a freshly built one.
• Turn off automatic output switching. If "Automatically switch audio output device" or a similar auto-switch setting is on, macOS can renegotiate which device it is talking to while the group is playing. Turning it off stops that renegotiation from happening mid-playback.
• Use full-bandwidth ports for both displays. Connect each Studio Display directly to a Thunderbolt or USB-C port capable of full bandwidth, rather than through a shared hub or dock. A hub adds another point where the two independent audio links can contend with each other.
• Set an explicit clock source instead of the default. In Audio MIDI Setup, pick which display is the primary device and turn on drift correction on the other, rather than leaving macOS to decide. This is the same setting covered in our guide to combining two Studio Displays into one output.

These are mitigations people have found effective often enough to be worth trying, not a guarantee. If the dropout is severe or constant even on a single display with nothing else attached, that points away from the two-display sync explanation above and towards the display or cable itself.

What actually clears it once it's already stuck?

A full restart of the Mac, not an app relaunch or a change of output and back, is what people most consistently report as clearing the stuck state. Quitting the app that was playing audio and reopening it rarely helps, because the dropout is happening at the system audio level, not inside the app. Letting the display sleep and wake does not reliably reset it either. A restart is the blunt option, but it is the one that keeps coming up as actually working.

Does Chorus fix this?

No, and it is worth being direct about why. Chorus groups outputs using the same underlying macOS mechanism that Audio MIDI Setup's Multi-Output Device uses, no kernel extension and no audio driver of its own. That mechanism is exactly where this dropout happens, so an app built on top of it cannot fix a fault inside it, and Chorus does not claim to.

What Chorus does help with is the part you actually have to repeat: since the mitigation above means rebuilding or reselecting the output group, Chorus turns that into one click or a keyboard shortcut instead of a trip through Audio MIDI Setup every time it happens. It does not stop the cutout. It makes recovering from it faster.

For the step-by-step on building a Multi-Output Device, see Apple's own guide to Audio MIDI Setup.

Frequently asked questions