Logic Pro Not Recording Audio: Fix Input, Mic and Interface Issues

I spent 47 minutes last year diagnosing a dead signal in a vocal session before finding the fix. Everything looked right: the Scarlett was lit, the track was armed, the record button was red. Nothing was capturing. Turned out Mic Mode had silently switched to Voice Isolation after a macOS update, and it was remapping all my interface inputs so every armed track received signal from Input 1 only. That session ate almost an hour for a two-second fix.

Logic Pro not recording audio is one of the most common complaints in the Apple Community forums and across r/logicpro. If Logic Pro is not picking up your mic, recording a flat line, or showing no input signal from an interface, the cause is usually one of four settings: macOS permissions, the wrong input device in Logic's audio settings, track-level recording setup, or a Mic Mode conflict introduced in Sonoma and later. This guide works through all of them in order.

Logic Pro Not Recording Audio: Quick Fix Checklist

If you need to diagnose fast, run through this order before going deeper. Most cases resolve at step 1, 2, or 3.

Logic Pro Not Recording Audio: Start with macOS Microphone Permission

After a macOS update, microphone permission is one of the first things to re-check. Sometimes macOS shows an alert; sometimes Logic simply receives no input, meters stay flat, and no waveform is recorded. The pattern started with Mojave and has repeated with every major macOS version since.

Quit Logic completely before doing this. Then:

1. Open System Settings (or System Preferences on older macOS).
2. Go to Privacy & Security > Microphone.
3. Find Logic Pro in the list and make sure the toggle is on.
4. Relaunch Logic.

If Logic Pro doesn't appear in that list at all, try opening it and immediately creating a new audio track. macOS needs Logic to request mic access before the app can appear in the privacy list. If the prompt never shows, try deleting Logic's preferences file (com.apple.logic10.plist from ~/Library/Preferences) and relaunching.

This permission check covers external audio interfaces too. macOS treats interface inputs as microphone inputs, so granting mic access covers both your built-in microphone and any connected USB mic or condenser microphone running through a Focusrite Scarlett, Apollo, or similar interface.

Logic Pro Audio Device Settings: Pick the Right Core Audio Input

Most tutorials make this step 1. It's actually step 2, because permissions block everything before it. With that cleared, check that Logic is pointed at the right device.

Go to Logic Pro > Settings > Audio > Devices. You need two things: the Core Audio Enabled checkbox must be ticked, and your interface (Scarlett, Apollo, MOTU, or whatever you're using) must be selected under Input Device. If it shows Built-in Microphone and you're running an external interface, nothing you do on the track will matter. Logic is listening to the wrong hardware input entirely.

After changing the input device, Logic sometimes needs a restart to recognize the new routing. Close the project, quit Logic, reopen. Takes 23 seconds and saves a lot of confusion.

One thing that trips people up constantly: the Input Device and Output Device can be set independently. You can output through your monitors while Logic still listens to Built-in Microphone. Set both explicitly.

Logic Pro Mic Mode: The Sonoma, Sequoia and Tahoe Issue That Breaks Interface Inputs

Starting with macOS Sonoma, Apple added Voice Isolation to audio inputs via a feature called Mic Mode. When Voice Isolation is active, multichannel interfaces can be remapped so every armed track receives signal from Input 1 only. If you're recording vocals or guitar to Input 2, Input 3, or any channel above the first, you get silence or a flat line recording. The meters on your Focusrite Scarlett or Apollo show signal. Logic's track meter stays flat. That's the tell.

Focusrite documented this in their Sonoma, Sequoia and Tahoe recording input issues guide. It's a macOS-level audio processing layer sitting between the interface and Core Audio, not a Logic bug.

The fix: while Logic is open and active, click the orange microphone icon in your Mac's menu bar (it appears because Logic is using the mic). Set Mic Mode to Standard. If you don't see the icon in the menu bar, open Control Center and look for the microphone section there.

This needs to be done with Logic running. Mic Mode is a per-app setting, so it applies to Logic in that session specifically. Worth checking after every macOS update.

Logic Pro Recording a Flat Line With No Waveform

You hit record, the transport runs, but the track shows a flat line and no waveform appears. Five things cause this, roughly in order of how often I see them.

1. Mic permission missing. No input signal reaches Logic at all. Meters stay flat everywhere. Fix: System Settings > Privacy & Security > Microphone, enable Logic Pro.

2. Input slot set to No Input. The track exists but isn't connected to any hardware input. Open the Inspector (press I), find the input slot on the channel strip, and set it to Input 1 (or whichever physical input you're using). This is also why the Input Monitoring "I" button sometimes disappears from the track header: when input is set to No Input, Logic hides it.

3. Track input routing to a Bus instead of hardware. A new audio track can default its input to Bus 1 instead of Input 1, especially in complex session templates. Check the input slot and confirm it reads a hardware input number, not a bus.

4. Voice Isolation / Mic Mode. Your interface's gain knob shows signal. The interface meters move. Logic's track shows nothing. This is Mic Mode Voice Isolation collapsing inputs to Input 1. Set Mic Mode to Standard in Control Center while Logic is active.

5. Wrong input device in Logic's audio settings. Logic is pointing at Built-in Microphone or a different device. Go to Settings > Audio > Devices and set the correct interface as Input Device.

Logic Pro Not Recording from Focusrite Scarlett, Apollo or USB Mic

The fixes above apply to all interfaces, but a few specifics are worth calling out.

Focusrite Scarlett: The most common cause of Logic Pro not recording from a Scarlett is Mic Mode set to Voice Isolation (see above). The second most common is phantom power (48V) not being enabled for condenser microphones. On the Scarlett itself, make sure the 48V button is lit if you're using a condenser mic. If you're running Focusrite Control software, check that gain levels are set correctly there before adjusting anything in Logic.

Universal Audio Apollo: Apollo interfaces require the UAD Console software to route inputs correctly. If Logic isn't receiving signal from an Apollo, check that Console is running, that the correct hardware input is assigned in Console's routing, and that the Apollo is selected as the Input Device in Logic's Settings > Audio > Devices. Logic won't pick up Apollo signal without Console handling the underlying routing.

USB microphone not working in Logic Pro: USB mics bypass the need for an audio interface entirely but still require macOS microphone permission. Grant permission in System Settings > Privacy & Security > Microphone. Then in Logic, go to Settings > Audio > Devices and confirm the USB mic is selected as the Input Device. USB mics appear as standalone devices, not as Input 1 of an interface.

Logic Pro Track Input Setup: Record Enable, Input Slot, and the "I" Button

Even with the device set correctly at the global level, Logic won't record to a track unless that track is configured right at the channel strip level. Three things to check, in this order.

Record Enable (the red R button): The track header has a small red circle. Click it so it lights up. This arms the track for recording. The main transport Record button enables recording globally, but if the individual track isn't record-armed, nothing lands on it. A common confusion: you can have the transport recording and see other tracks capturing audio, but a track that's not armed will only produce a flat line.

Input Slot: In the channel strip Inspector (press I), there's an input slot showing which physical hardware input the track is listening to. If it says No Input, the Input Monitoring button is hidden entirely. Set it to the correct input channel: Input 1 for the first channel of your interface, Input 2 for the second.

Input Monitoring (the "I" button): This button in the track header lets you hear the incoming signal during playback and recording. You need it on to confirm signal is reaching the track before committing to a take. Per the Apple documentation on input monitoring: when Input Monitoring is on, Auto Input Monitoring and Record Enable don't affect software monitoring. You'll always hear the incoming signal. If that causes doubled audio during playback, see the section below on Auto Input Monitoring.

Logic Pro Auto Input Monitoring: When You Can Hear Input But Not Playback

Logic Pro 11.1 changed how many users experienced Auto Input Monitoring, and Apple later addressed the behavior in 11.1.2. If playback suddenly feels silent while a record-armed track is active, this setting is worth checking.

Here's how it works:

• With Auto Input Monitoring on (under the Record menu): during playback, Logic plays the existing audio region on the track. During recording, it switches to monitoring the live input. You won't hear yourself during playback on a record-armed track, which confused a lot of people after the 11.1 update.
• With Auto Input Monitoring off: you hear the live input signal during both playback and recording, on top of any existing audio. Useful for setting levels but can cause doubled audio if not managed.

If you recorded something and can't hear it back while Input Monitoring is on, that's the issue. Either turn off Input Monitoring after the take, or go to Record > Auto Input Monitoring in the menu bar and adjust to match your workflow.

Also check Settings > Audio > General and confirm that Software Monitoring is enabled. Without Software Monitoring on, you won't hear any incoming signal through Logic regardless of any other setting. This is the one Logic-level switch that overrides everything else.

Logic Pro Interface Troubleshooting: USB Hubs, Drivers, and Audio MIDI Setup

If Logic's settings all look correct and you're still getting no input signal, the problem is upstream of Logic.

USB hubs: Several users in Apple Community threads traced silent recording to USB hubs becoming incompatible after a macOS update. If your interface is running through a hub, plug it directly into the Mac and test again. Worth doing before any deeper troubleshooting.

Interface drivers and software: Many simple USB interfaces are class-compliant on macOS and work without a separate driver. But some interfaces still require manufacturer software, control panels, firmware updates, or drivers, especially larger multichannel systems and DSP-based interfaces. If yours falls into that category, check the manufacturer's site for a driver release compatible with your current macOS version.

Audio MIDI Setup: Go to Applications > Utilities > Audio MIDI Setup. This is macOS's core audio routing tool. If your interface isn't showing up here, Logic won't see it either. If it appears but shows zero input channels, the interface may need a firmware update or a different USB connection. A sample rate mismatch between the interface and the Logic project (for example, interface set to 48kHz, project at 44.1kHz) can also cause silent recording or distorted audio. Match them in Audio MIDI Setup and in Logic's Settings > Audio > Devices.

One test that's always worth doing: open GarageBand and try the same input. GarageBand uses Core Audio, just like Logic. If it records fine in GarageBand but Logic Pro is not recording from your microphone, the issue is inside Logic's settings. If GarageBand also fails, the issue is at the macOS or hardware level.

Logic Pro Buffer Size and Low Latency Mode When Recording Audio

Buffer size doesn't cause recording failure on its own, but it creates problems that look like failure: input dropout, clipped waveforms, recordings that stop mid-take with a system overload error.

For recording, keep the I/O buffer at 128 samples or lower. Go to Settings > Audio > Devices and use the I/O Buffer Size menu. Logic shows the resulting roundtrip latency directly below the menu. On most Apple Silicon Macs, 64 or 128 samples runs without overloads for typical sessions with 20 to 30 tracks.

If you have CPU-heavy Audio Units plug-ins and can't drop the buffer without overloads, use Low Latency Mode: go to Record > Low Latency Mode. This bypasses latency-inducing plug-ins during recording and re-enables them on playback. It won't fix a signal routing problem, but it stops a buffer-caused dropout from looking like a recording failure.

For a full explanation of roundtrip latency, I/O buffer tradeoffs, and Low Latency Mode, see Apple's guide on managing input monitoring latency in Logic Pro.

Logic Pro Recording FAQ

Why is Logic Pro not detecting my audio interface?

Logic Pro won't detect an audio interface that isn't showing up in Audio MIDI Setup (Applications > Utilities). Start there. If the interface appears in Audio MIDI Setup but not in Logic, go to Settings > Audio > Devices and select it manually from the Input Device menu. Also confirm the Core Audio Enabled checkbox is ticked. A sample rate mismatch between Logic and the interface can also prevent detection in some configurations.

Why is Logic Pro recording a flat line with no waveform?

A flat line recording with no waveform means Logic received no input signal. The most common causes: mic permission missing in macOS Privacy & Security, input slot on the channel strip set to No Input, Mic Mode set to Voice Isolation (Sonoma and later), or the wrong input device selected in Logic's audio settings. Open the Inspector (press I), check the input slot, and confirm it's set to the hardware input your mic or instrument is plugged into.

Why can I hear input monitoring but nothing records?

Input monitoring and actual recording are separate. You can hear yourself through Logic without any audio being written to disk. For audio to be captured, the track needs to be record-enabled (red R button lit in the track header) and Logic's global record button in the transport must be active. If both are on and you still get a flat line, check that your recording file destination is writable and that the project sample rate matches your interface.

Why did Logic Pro stop recording after a macOS update?

macOS updates can reset microphone permissions. After updating, go to System Settings > Privacy & Security > Microphone and re-enable Logic Pro's access. If you updated to Sonoma, Sequoia, or Tahoe, also check Mic Mode in Control Center while Logic is active. Voice Isolation or Wide Spectrum can disrupt multi-channel interface routing. Set Mic Mode to Standard.

Does Logic Pro work with any USB audio interface?

Many simple USB interfaces are class-compliant on macOS and work without a separate driver. But some interfaces still require manufacturer software, control panels, or firmware updates, especially larger multichannel systems and DSP-based interfaces like the Apollo range. If yours requires software, check the manufacturer's site for a version compatible with your current macOS.

Why is my mic not working in Logic Pro but GarageBand works?

GarageBand and Logic Pro both use Core Audio, so if GarageBand records fine, the interface and macOS permissions are working. The issue is Logic-specific. Check the Input Device in Logic's Audio Settings, the input slot on the track's channel strip, and whether the track is actually record-enabled. Also confirm that Software Monitoring is turned on under Settings > Audio > General.

Why is Logic Pro not recording vocals or guitar but the interface shows signal?

When the interface gain knob shows signal but Logic Pro is not recording vocals or guitar to the track, the most common cause is Mic Mode set to Voice Isolation. This collapses multi-channel interfaces so all armed inputs receive signal from Input 1 only. If your mic is on Input 2 or higher, Logic gets nothing. Set Mic Mode to Standard in macOS Control Center while Logic is running. Also confirm the track's input slot matches the physical input channel your mic or instrument is on.

Why is Logic Pro not recording after a Sonoma, Sequoia or Tahoe update?

Two things happen after major macOS updates. First, microphone permission can be reset. Go to System Settings > Privacy & Security > Microphone and confirm Logic Pro is enabled. Second, Mic Mode can default to Voice Isolation, which remaps multichannel interface inputs and produces silent recordings or a flat line. Open macOS Control Center with Logic running and set Mic Mode to Standard. Both checks take under a minute and solve the majority of post-update recording failures.

For broader setup, see our Logic Pro beginner tutorial. If your recording chain works but monitoring feels delayed, read the guide on fixing latency in Logic Pro. If you're checking whether your Mac and macOS version are supported, see the Logic Pro system requirements guide.

Related guides: Why your mic is quiet in Logic Pro, Fix audio latency in Logic Pro, Logic Pro Stem Splitter

Sources: Logic Pro User Guide — Apple Support · Logic Pro — Apple