Logic Pro keeps losing your audio interface on a Mac — what's happening, and how to stop it
The pattern is familiar to anyone who tracks on a Mac. The interface blips — a bumped cable, a dock renegotiating, the machine waking — and Logic Pro reacts badly. Maybe input meters go dead while everything still looks connected. Maybe the I/O Assignments tab is suddenly empty. Maybe Logic insists the device is missing until you physically unplug the interface and plug it back in.
It reads like a Logic bug. It mostly isn't. Here's the actual mechanism, the fixes worth trying, and the one change that makes the whole class of problem go away.
What's actually happening
Every audio device on macOS lives behind Core Audio, and every device has an identity that apps bind to. When you choose your interface in Logic Pro → Settings → Audio, Logic binds to that specific device and builds its whole I/O picture on top of it: which physical inputs feed which channel strips, what the outputs map to, what the monitoring path is.
When the interface disconnects, Core Audio removes the device. Not "marks it offline" — removes it. Every channel strip's input reference now points at something that no longer exists.
When the hardware comes back, Core Audio re-adds it. Depending on how the interface enumerates over USB and how quickly it settles, it can come back with a different internal identity, a different stream arrangement, or a different channel count than the one Logic memorised. Logic is then holding references to a device that, as far as the system is concerned, is not the device it had. So it does the only honest thing available: it drops the assignments rather than silently routing your vocal mic to something else.
This is why the problem clusters exactly where it hurts — long sessions, hubs and docks, stage rigs where cables get knocked, machines that have been running for hours.
The fixes worth trying (and where they stop)
1. Re-select the device. Settings → Audio, switch the output device to something else, apply, then switch back. This forces Logic to rebuild its device binding and often restores inputs without a restart. It's the fastest recovery, but it is a recovery, not a prevention.
2. Check I/O Assignments after any drop. Under Settings → Audio → I/O Assignments, confirm your output and monitoring assignments survived. They often haven't, and the failure is quiet — you find out when nothing comes out of the monitors.
3. Enable the advanced options. Some engineers find input choices missing entirely until the full set of advanced features is enabled in Logic's settings. Worth ruling out once.
4. Fix the physical layer. Direct USB port instead of a hub, a powered interface, a secured cable, current firmware, and no sleep during sessions. This genuinely reduces how often drops happen — do it regardless.
5. Keep a recovery template. A saved template you can re-import after a drop. It works. It's also a fire drill you're running while people wait.
Every one of these either reduces how often the interface drops, or shortens the cleanup afterwards. None of them changes the thing that actually causes the pain: Logic is bound directly to a device that is allowed to vanish.
The durable fix: give Logic a device that can't disappear
Point Logic at a stable virtual device that mirrors your interface, rather than at the interface itself.
The mirror is always present in Core Audio. When the hardware drops, the mirror is still there — Logic's device is still there, its channel strips still reference something real, and nothing gets unmapped. When the hardware returns, audio simply resumes through the same device Logic has been pointed at the whole time. There's no re-selection, no empty I/O Assignments, no template re-import, because from Logic's point of view nothing ever left.
This is what Keel Audio does. It creates a transparent, bit-for-bit mirror of your interface — no processing applied, running on the interface's own clock — and keeps it stable across disconnects and re-enumeration. You point Logic at the Keel device once and stop thinking about USB. It's a one-time purchase with a full 14-day trial, so you can prove it on your own rig: arm some tracks, pull the interface out mid-take, and watch the session stay exactly where it was.
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 reliable tracking on a Mac
- Direct USB port; avoid unpowered hubs and shared docks.
- Powered interface, secured cable, current firmware.
- Point Logic at a stable device rather than the raw interface.
- Disable sleep and aggressive USB power saving for session machines.
- Check I/O Assignments as part of your pre-session check, not after.
- Do a dry run that includes deliberately unplugging the interface.
Bottom line
Logic losing your interface isn't a preference you can hunt down — it's what happens when the device a DAW is bound to disappears and returns as something subtly different. Reduce the drops by all means. But the reliable fix is to give Logic a device that can't disappear in the first place, and let the hardware come and go behind it.
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 →