Why Studio One loses its inputs when your audio interface disconnects on a Mac (and how to stop it)
If you run Studio One on a Mac for live capture, you've probably hit this: the audio interface drops for a split second — a bumped USB cable, a power blip, a hub renegotiating — and suddenly your input assignments are gone. Tracks that were armed to channels 1–48 are now mapped to nothing, and you're rebuilding routing with a service or a stream about to start.
It feels like Studio One's fault. It usually isn't. Here's what's actually happening, and what you can do about it.
What's really going on
macOS audio devices live behind Core Audio. When your interface disconnects, Core Audio removes that device from the system. When it comes back, Core Audio re-adds it — and depending on timing and how the interface enumerates over USB, it can come back with a different internal device ID or a reordered set of streams.
Your DAW bound its input tracks to that specific device. When the device disappears and returns as "a new device," the DAW has nothing stable to hold onto, so it drops or scrambles the mapping. Studio One is just honestly reporting that the thing it was recording from went away.
This is why it's worse in exactly the situations where it hurts most — long sessions, USB hubs, stage rigs where cables get knocked, and machines that have been running for hours.
The usual workarounds (and their limits)
1. Lock down the physical connection. Direct USB port (no hub), a locking or taped cable, and a powered interface that won't brown out. This reduces the frequency of drops but doesn't fix what happens when one occurs.
2. Use an Aggregate Device. You can build an Aggregate Device in Audio MIDI Setup. It can help with multi-interface setups, but it doesn't make a single interface survive a disconnect — if a member device drops, the aggregate is affected too, and you're back to remapping. It also adds its own clocking complications.
3. Re-template your session. Some engineers keep a recovery template and re-import it after a drop. It works, but it's a fire drill, and it's the last thing you want to do 30 seconds before going live.
4. Don't touch anything during the service. Realistic advice, and worth following — but it's a hope, not a safeguard. Cables still get kicked.
These all attack the symptom (the interface dropping) rather than the cause of the pain (the DAW losing its stable device).
The real fix: give the DAW something that never disappears
The durable solution is to stop pointing your DAW at the hardware directly, and point it at a stable virtual device that mirrors the hardware instead. The virtual device stays present in Core Audio no matter what the physical interface does — so the DAW's mapping never has anything to lose.
When the interface drops, the virtual device is still there. When it comes back, audio resumes — and because the device your DAW is bound to never went away, your inputs are exactly where you left them. No remap, no reset, no template re-import.
This is the approach Keel Audio takes. Keel is a macOS app that creates a transparent, bit-for-bit mirror of your interface and keeps it rock-stable across disconnects and re-enumeration. You point Studio One at the Keel device once; from then on, USB hiccups and interface resets don't reach your session. (It's a one-time purchase with a free 14-day trial, so you can test it against your own rig under real conditions before trusting it on a Sunday.)
To be clear about what this is and isn't: it's not an audio router or a virtual cable for moving sound between apps. It does one job — keep a single physical interface stable for your DAW.
A sensible checklist for live capture on a Mac
Whether or not you use a virtual mirror, this list prevents most of the heartbreak:
- Plug the interface into a direct USB port; avoid unpowered hubs.
- Use a powered interface and a secured cable.
- Point your DAW at a stable device (a virtual mirror) rather than the raw interface.
- Build mirrors / templates before the event, and don't add/remove devices once you're set.
- Do a full dry run — including yanking and replugging the interface — so you know exactly how your rig recovers.
Bottom line
Studio One losing its inputs isn't a bug you can configure away — it's what happens when the device a DAW is bound to disappears and comes back as something new. Reduce the drops, sure, but the reliable fix is to give the DAW a device that can't disappear. Mirror the interface, point the DAW at the mirror, and the next time a cable gets kicked, the only thing that notices is you.
Keel Audio keeps one audio interface rock-stable for your DAW on macOS, so a disconnect never resets your inputs.
Try it free for 14 days →