How to tell if your Mac's audio interface is really re-enumerating

2 September 2026 · 4 min read

Before you buy cables, swap hubs, or reinstall drivers, it's worth spending ten minutes proving what's actually wrong. "My interface keeps dropping" covers at least four different problems with four different fixes, and the logs will tell you which one you have.

This is the diagnostic pass we'd run first. No special tools — it's all built into macOS.

The four things it's usually not the same as

These get confused constantly, and they need opposite responses:

• USB re-enumeration. The device physically drops off the bus and comes back. A hardware/power/cable problem.
• Core Audio dropouts (xruns). The device stays connected, but the machine misses buffer deadlines. Clicks and glitches, not disappearances. A load or buffer-size problem.
• Clock or sync problems. Audio plays but drifts, or a device disagrees about sample rate. Common with aggregate setups.
• App-side device binding loss. The interface is fine, but your DAW or OBS lost its reference to it.

Fixing a cable won't help with an xrun problem, and lowering your buffer size won't help a device that's falling off the bus. So: find out.

Reading the log in Console.app

Open Console (Applications → Utilities → Console) and select your Mac in the sidebar. The log is extremely noisy, so the filter is the whole technique.

Useful things to filter on, one at a time:

• Your interface's name as it appears in Audio MIDI Setup — the most direct signal.
• AppleUSBAudio — the USB audio driver.
• IOUSBHostDevice — USB device attach and detach at the host level.
• coreaudiod — the Core Audio daemon, which logs devices being added and removed.

Then reproduce the problem, or wait for it, and look at what lands around that timestamp. Console's Start streaming button shows live activity; pausing right after a drop makes the relevant lines much easier to find.

What each pattern means

Repeated attach/detach lines around the moment of the drop — the device leaving and rejoining the USB bus — is a confirmed re-enumeration. That's a physical-layer problem: power, cable, hub, dock, or interface firmware. Cables and ports are now worth your money.

Core Audio adding and removing the device with no USB attach/detach around it points at the audio layer rather than the bus — a driver issue, a power-management state, or an OS-level bug. Check that you're on a current macOS point release and current interface firmware.

Nothing in the log at the moment your audio died is itself a strong finding. If the device never left, your problem is app-side: your DAW or OBS lost its binding, or you're hitting buffer under-runs. Look at the application, not the hardware.

A second opinion from system_profiler

To see how the interface is actually attached — and what it's sharing a bus with — run this in Terminal:

• system_profiler SPUSBDataType

Find your interface in the output and check two things. First, whether it's on a hub or connected directly. Second, what else is on the same controller — a display dock, a drive, and an audio interface competing on one bus is a classic recipe for exactly the drops you're chasing.

It's also worth confirming in Audio MIDI Setup that the device reports the channel count and sample rate you expect, and that it still does after a reconnect. A device that comes back at a different rate will cause problems that look nothing like a USB fault.

What to do with the answer

If you've confirmed re-enumeration: plug directly into the Mac, use a powered interface and a known-good cable, get off shared docks, disable USB power saving, keep the machine awake, and update the interface firmware. See the fuller write-up on reducing re-enumeration for the detail.

If you've confirmed the device is fine and your software lost it, the fix is at the application layer — that's the failure described for Logic Pro, Studio One and OBS.

And if you're on macOS 26, check your point release before anything else — see macOS Tahoe and USB audio.

Worth saying plainly

Diagnosis reduces how often the hardware drops. It doesn't stop drops from mattering. Those are two separate jobs, and on a live rig you want both: fix the physical layer so drops are rare, and put a stable device between the interface and your software so the rare drop doesn't reset your session. That second job is what Keel Audio is for — a bit-for-bit mirror of your interface that stays present in Core Audio no matter what the USB bus does.

Bottom line

Ten minutes in Console will tell you whether you're chasing a cable, a driver, or your own software — and stop you from spending a weekend fixing the wrong layer. Confirm the failure first, then fix it, then make it harmless.

Related: Why interfaces keep reconnecting macOS 26 and USB audio When Logic loses the interface