Audio Interface Not Showing Up in Logic Pro: Detection and Driver Fixes

My Universal Audio Volt worked fine for two weeks, then one session it simply wasn't there. Not disconnected mid-take, not making noise, just absent from every device menu Logic Pro offered. An audio interface not showing up in Logic Pro usually points to one of two layers: macOS hasn't detected the device at all, or Logic Pro hasn't selected the available Core Audio device correctly. Start in Audio MIDI Setup to find out which layer is failing.

Tested with Logic Pro 12.3 on macOS 15.6 on an Apple silicon Mac. Menu paths and the Apple Support steps below were rechecked on July 19, 2026.

This guide covers detection: an interface missing from Audio MIDI Setup or Logic Pro's device menus, one that disconnects on launch, driver and class-compliance issues, and combining interfaces with an Aggregate Device. If your interface is already selected and working but nothing is recording, see Logic Pro not recording audio. If Logic Pro plays nothing at all through an interface it has already selected, see Logic Pro no sound. If Logic Pro itself won't finish opening, see Logic Pro plugins not showing up for the Audio Units side of that.

Logic Pro Audio Interface Not Showing Up: Quick Diagnostic Checklist

Confirm the Interface Shows Up in Audio MIDI Setup

Open Audio MIDI Setup, in Applications > Utilities, with Logic Pro closed. Logic Pro reads its available devices from here; if your interface isn't listed, no Logic Pro setting will make it appear, because the problem is below Logic Pro entirely.

If the interface is missing, the cause could be the connection, power, firmware, the driver, or hardware compatibility, not "Core Audio" as a single catch-all. Apple's own troubleshooting order for Logic Pro starts with a restart, then updating Logic Pro, then checking device and software compatibility, then disconnecting other external devices one at a time and testing built-in audio between each. Work through the physical checks below before assuming anything about drivers.

Check the Physical Connection: Cables, Ports, Hubs and Power

Plug the interface directly into a port on your Mac, not through a hub, dock, or daisy chain; Apple recommends a direct connection over a hub. Try a different cable if you have one, since a cable that carries power but not data can let an interface light up while staying invisible to macOS.

If the interface is bus-powered, a weak or overloaded port can drop it under load. If it takes external power, confirm the supply is seated and the power light is on before you open Logic Pro. None of this is specific to Logic Pro, which is why it comes before anything else.

Test Logic Pro With Built-In Audio First

Before troubleshooting drivers, disconnect the interface completely. In Logic Pro > Settings > Audio > Devices, set Output Device to Built-In Output and Input Device to Built-In Microphone (or Built-In Input), then open the same project and try to reproduce the problem.

If Logic Pro behaves normally on built-in audio, the fault narrows to the interface itself, its cable, its firmware, its driver or control software, or its compatibility with your current macOS version. If the problem continues with the interface disconnected and built-in audio selected, the interface isn't the only trigger. Continue by checking the project itself, Audio Units, Core Audio, and Logic Pro's preferences.

Select the Right Device in Logic Pro's Audio Settings

With the interface confirmed in Audio MIDI Setup, open Logic Pro > Settings > Audio > Devices. Confirm Core Audio Enabled is checked, then set the Output Device and Input Device pop-up menus to your interface by name.

Logic Pro can use separate devices for input and output directly; that doesn't require an Aggregate Device. Apple recommends using one interface for both when practical, mainly to avoid clock mismatches, but Logic Pro supports the split natively. You need an Aggregate Device only when you want the inputs or outputs of more than one physical device to appear as a single combined device, covered further down.

Logic Pro supports connecting an audio interface while the app is already open and should prompt you to select and confirm the new device and driver as soon as it's detected. If no prompt appears even though the device is visible in Audio MIDI Setup, quit and reopen Logic Pro as a fallback, then recheck the Output and Input Device menus.

Logic Pro Audio Interface Driver Problems: Class-Compliant vs. Manufacturer Drivers

Whether an interface needs a manufacturer driver depends on the specific model, not its size or channel count. Some interfaces are class-compliant and run on macOS's own built-in Core Audio support with no extra software; others need a manufacturer driver or control application installed and kept current, whether they're a simple two-input box or a larger multichannel unit. Check the exact model on the manufacturer's own compatibility page rather than guessing from its size.

Apple's current product and Creator Studio pages list macOS 15.6 or later and a Mac with Apple silicon as the requirement, though Apple's separate Tech Specs page hasn't always been updated to match. Check the exact Logic Pro edition and Apple's current requirements before updating; Logic Pro system requirements covers the full hardware breakdown, including where those two Apple pages disagree. Manufacturers publish their own macOS compatibility by version. Focusrite's compatibility page is one example of a vendor tracking support release by release, and it's worth checking before you update macOS or Logic Pro, since a driver that worked on the previous version isn't guaranteed to work on the next.

Logic Pro Audio and MIDI Sync Alerts With Your Interface

An "Error while trying to synchronize Audio and MIDI" alert most often means a sample-rate mismatch or fluctuation, but Apple's own article lists several other sources: an unstable digital clock between your interface and another connected device, an Aggregate Device where the combined interfaces aren't sharing a clock correctly, an external MIDI timecode or MIDI clock source syncing to or from Logic Pro, and certain plug-ins, including a Reaktor Ensemble with its LFO synced to song tempo.

Check the sample rate first: choose File > Project Settings > Audio and note the project's Sample Rate, then compare it to the interface's own hardware rate in its control software, if it has one, or in Audio MIDI Setup. If the two already match, temporarily pick a different sample rate from the pop-up menu and switch back; Apple lists this as a valid fix for a setting that's stuck rather than truly mismatched. If the rates already match, check digital clock settings between connected devices, your Aggregate Device configuration, any external sync source, and plug-ins that generate tempo-synced audio, before assuming the interface's driver is at fault.

Clicks and pops can come from an I/O buffer that's too small, but also from driver, sample-rate, or digital-clock problems. Use the exact alert text and the device's clock status to decide which path to test, rather than jumping straight to the buffer size menu. An interface disappearing from the device list entirely is a different symptom again, and points back to connection, power, firmware, driver, or Core Audio detection rather than to timing.

Use a Logic Pro Aggregate Device When One Interface Isn't Enough

An Aggregate Device combines two or more audio devices, such as two interfaces, or an interface plus your Mac's built-in microphone, into a single device Logic Pro can select. Build it in Audio MIDI Setup, not inside Logic Pro: click the plus button, choose Create Aggregate Device, then tick each device you want included.

Setting the clock source depends on your devices. If none of them are synchronized to each other through hardware, choose the one with the most reliable clock as Clock Source and enable Drift Correction on every other device in the group. If some devices share a hardware sync connection, choose that hardware sync's primary clock as Clock Source and enable Drift Correction only on the devices outside that sync. If every device in the group is already hardware-synced together, none of them need Drift Correction.

Back in Logic Pro's Audio Settings, select the Aggregate Device as your Output Device; the Input Device updates to match. Aggregate Device stability and latency depend on the specific devices, drivers, and clocking involved, and on whether Drift Correction is required, so test the combined setup at your intended sample rate and buffer size before relying on it for a session.

If the Problem Continues With Built-In Audio

If Logic Pro still has trouble after the interface is disconnected and built-in audio is selected, the external interface is not the only trigger. Hold Option to rule out the last project or an automatic startup action, then test Control > Don't Launch, then Control > Launch Without Audio Units. If Logic Pro opens cleanly with Core Audio disabled, Apple's guidance is that the external interface's software may need an update or service, though a conflicting Audio Unit involved in Core Audio startup can produce the same result, so treat a successful Don't Launch as a diagnostic lead rather than final proof. A clean launch without Audio Units points to a specific plugin instead.

Logic Pro keeps crashing covers startup hangs and instability in more depth than fits here. Logic Pro plugins not showing up is the better link once you've narrowed the cause to a specific plugin, since it walks through Plug-in Manager and Audio Unit validation directly. Logic Pro no sound covers the Core Audio toggle and Logic Pro's preferences reset, including the difference between the one-time purchase plist and the Apple Creator Studio subscription plist.

Logic Pro Audio Interface Detection FAQ

Why does my audio interface disconnect the moment I open Logic Pro?

This usually points to Core Audio, the interface's own driver or software, or a third-party Audio Unit involved during startup, not necessarily a bad interface. Test with built-in audio first: if Logic Pro behaves normally on Built-In Output and Built-In Microphone, the interface, its cable, or its driver is the more likely cause.

Why does my interface show up in Audio MIDI Setup but not in Logic Pro's Audio Settings?

Logic Pro supports plug-and-play and should prompt you to select the new device and driver as soon as you connect and power it on. If no prompt appears, quit and reopen Logic Pro as a fallback, then check that Core Audio Enabled is ticked in Logic Pro > Settings > Audio > Devices and select the interface manually from the Output and Input Device menus.

Do I need a driver for my audio interface in Logic Pro?

It depends on the specific model, not its size or channel count. Some interfaces are class-compliant and run on macOS's built-in Core Audio support with no extra software; others need a manufacturer driver or control application. Check your exact model on the manufacturer's compatibility page rather than assuming from how many inputs it has.

Can I use two audio interfaces at the same time in Logic Pro?

Yes, by combining them into an Aggregate Device in Audio MIDI Setup, which lets Logic Pro see them as a single device with combined inputs and outputs. How well it performs depends on the specific devices, their drivers, and their clocking, so test the pairing at your working sample rate and buffer size before a real session.

What does "Error while trying to synchronize Audio and MIDI" mean in Logic Pro?

Most often it's a sample-rate mismatch or fluctuation between your project and your interface. Check the project rate in File > Project Settings > Audio, then compare it to your interface's own hardware rate in its control software or Audio MIDI Setup. If the rates already match, Apple also lists an unstable digital clock, an Aggregate Device sync issue, an external MIDI sync source, and certain tempo-synced plug-ins as causes.

Does an Aggregate Device add extra latency in Logic Pro?

It can, but Apple doesn't publish a fixed figure for it. Latency and stability depend on the connected devices, their drivers, their clocking, and whether Drift Correction is needed for any of them. If low latency matters more than combined channel count, test the Aggregate Device at your working buffer size first, or consider a single interface with enough inputs instead.

Related guides: Logic Pro No Sound: Fixes · Logic Pro Not Recording Audio · How to Fix Latency in Logic Pro

Sources: Set aggregate device settings in Audio MIDI Setup on Mac — Apple Support · If Logic Pro for Mac isn't working — Apple Support