Ableton Live loses your audio interface when it disconnects on a Mac — why, and the durable fix

You're mid-set or mid-session, the interface drops for a moment, and Ableton Live does something unhelpful: it falls back to Built-in Output, or throws a driver error, or keeps the right device selected but quietly loses the input routing on your armed tracks. Either way the sound stops, and getting back takes more clicks than you have time for.

Here's what's happening underneath, what actually helps, and how to make a disconnect a non-event.

What's going on underneath

Live talks to your interface through Core Audio. When you pick the device in Preferences → Audio, Live binds to that device and builds its input and output routing on top of it — which hardware input feeds which track, which outputs the master goes to, what the channel configuration is.

A disconnect removes the device from Core Audio outright. Live is left holding a reference to something that no longer exists, so it does what it can: it reports a driver error, or it falls back to a device that does exist — usually Built-in Output — so that at least something is working.

When the interface comes back, it is re-added, potentially with a different internal identity or a different channel arrangement. Even if you re-select the correct device, the per-track input routing that referenced specific channels on the old device may not line up any more. That's the part people find maddening: the device name looks right, but the routing underneath has quietly moved.

The usual workarounds, and their limits

Re-select the device in Preferences → Audio. Switch away and back to force Live to rebuild the binding. Reliable as a recovery; does nothing to prevent the next one.

Check your Input Config after every drop. Confirm the input channel pairs you rely on are still enabled — they're a common casualty, and the failure is silent until you try to record.

Build an Aggregate Device. Genuinely useful when you need several interfaces to appear as one — but it does not survive a reconnect. In our own testing, replugging a member interface with the DAW running reset the outputs, and the inputs didn't recover reliably until the Mac was restarted. It also brings its own clocking and drift complications.

Harden the physical layer. Direct port instead of a hub, powered interface, good cable, current firmware, no sleep. This is worth doing on its own terms — it makes drops rare.

But rare isn't never, and none of these change the underlying situation: Live is bound to a device that the operating system is free to remove.

The durable fix

Point Live at a stable device that mirrors your interface instead of at the interface itself.

Because the mirror never leaves Core Audio, Live never sees a device disappear. There's no fallback to Built-in Output, no driver error, and no reshuffled input configuration, because the device Live is bound to hasn't changed. The hardware drops behind the mirror and comes back behind it, and your set keeps its routing throughout.

Keel Audio does exactly this on macOS: a transparent, bit-for-bit mirror of one interface, on that interface's own clock, with no processing applied, that stays present through disconnects and re-enumeration. Set Live's audio device to the Keel device once and leave it. There's a full 14-day trial — test it the honest way, by unplugging the interface while Live is running.

One clarification, because it comes up: this isn't a router, a virtual cable, or a mixer for moving sound between apps. It does a single job — keep one physical interface rock-stable for whatever depends on it.

A checklist for live use

Bottom line

Live falling back to Built-in Output isn't Live being fragile — it's a reasonable response to its audio device being deleted underneath it. Fix the physical layer so drops are rare, then give Live a device that can't be deleted, so the rare drop costs you nothing.

Keel Audio keeps one audio interface rock-stable on macOS, so a USB drop never resets your DAW or kills your stream.

Try it free for 14 days →