Logic Pro Latency: How to Reduce & Fix It (Mac)

Logic Pro on macOS has excellent low-latency potential because Core Audio (macOS’s audio engine) is built for it. But you need to know where the settings are and how they interact. Get I/O buffer size and Low Latency Mode right, and you’re tracking with sub-15ms latency easily.

Understanding Logic Pro’s Latency

Logic latency comes from:

I/O Buffer Size: How many samples Logic processes at once. Smaller = lower latency, higher CPU demand. This is your main control.

Core Audio Interface: Logic uses macOS’s Core Audio, which is optimized for low latency (no driver installation needed).

Plugin Latency: Some plugins add delay. Look-ahead compressors, reverbs, and mastering plugins are common culprits.

Low Latency Mode: A toggle that temporarily bypasses latency-inducing plugins when recording. Essential for low-latency tracking.

Processing Threads: How Logic distributes CPU work. More threads = better performance on multi-core Macs.

Step 1: Lower I/O Buffer Size

I/O buffer size is Logic’s equivalent to “block size” or “buffer length.” It’s measured in samples and affects how much time Logic has to process audio each cycle.

How to Access:

1. Logic Pro > Settings (or Preferences on older versions) > Audio.
2. Click “Devices” tab.
3. Look for “I/O Buffer Size” dropdown. You’ll see latency displayed next to it.

Recommended Sizes:

64 samples: Most responsive, high CPU demand. ~13ms roundtrip on a typical Mac with an audio interface.

128 samples: Good balance. ~26ms roundtrip reported by Logic, though actual is often lower with Core Audio.

256 samples: Stable, slightly more latency. Use for projects with lots of plugins.

512 samples: For mixing when you don’t need low latency, frees up CPU.

How to Test:

1. Set I/O to 128.
2. Open a project with a few tracks.
3. Play and listen. Any clicks or pops?
4. If clean, try 64 next.
5. If you hear glitches, increase back to 128 and test with more tracks.

Most modern Macs (M1/M2 and newer, or Intel i7+) handle 128 comfortably in typical sessions.

Step 2: Enable Low Latency Mode

This is the game-changer for recording. Low Latency Mode temporarily routes around latency-inducing plugins so you hear yourself with minimal delay while the rest of the playback stays locked.

How to Enable:

1. Record > “Low Latency Mode” (toggle on).

That’s it. You’ll see a “Low Latency Mode” indicator in the transport controls when it’s active.

What It Does:

Plugins with look-ahead functions (compressors with “lookahead,” reverbs, mastering plugins) add delay. Normally, Logic delays all tracks to compensate and keep timing. Low Latency Mode bypasses that compensation for your recording input, giving you real-time feedback.

Important: The toggle affects the recording track only. Your playback (drums, click, existing tracks) stays synced. You might feel a slight disconnect between your performance and the playback rhythm, but most musicians adjust instantly. This is the professional way to track in Logic.

When to Use:

Always enable it when recording audio or MIDI. Disable it when mixing or playback-only sessions.

Step 3: Set Plugin Latency Limit

If Low Latency Mode still feels sluggish, you can adjust how much latency it tolerates.

How:

Settings > Audio > General > “Plugin Latency Limit” slider.

Lower value = stricter low-latency mode, might affect some plugins. Default is fine for most sessions.

Step 4: Choose the Right Audio Device

Logic lets you select which Core Audio device to use. If you have multiple audio interfaces, pick the one with the best reported latency.

How:

Settings > Audio > Devices > “Audio Device” dropdown. Select your interface.

Logic shows the latency for that device at your current I/O buffer size.

Pro Tip: Some older USB interfaces have higher Core Audio latency than newer ones. If you have multiple interfaces, test each one and stick with the lowest-latency option.

Step 5: Freeze Tracks with CPU-Heavy Plugins

If your session has lots of reverb, convolution, or mastering plugins, they add latency that affects your entire mix. Freeze them to convert them to audio and remove the processing overhead.

How:

Right-click track > “Freeze Track.”

Logic renders the track to audio. The plugins are bypassed, saving CPU and removing their latency from real-time processing.

Before Freezing:

Make sure you have a good recording of the track with all plugins applied. Once frozen, you can’t adjust the plugins on that track until you unfreeze it.

When to Freeze:

After recording and arranging. Unfreeze if you need to adjust plugin settings during mixing.

Step 6: Adjust Processing Threads

Modern Macs have multiple CPU cores. Logic can distribute processing across them for better performance.

How:

Settings > Audio > General > “Processing Threads” slider.

Max it out. More threads = better handling of complex sessions.

On Apple Silicon Macs (M1/M2/M3):

There’s also “Process Buffer Range.” Set to “Small” for recording (lower latency), “Large” for mixing (more CPU headroom).

Using Direct Hardware Monitoring (Zero Latency)

If your audio interface has a hardware mix knob or software mixer, bypass Logic entirely for monitoring.

How:

1. Open your interface’s software (usually named something like “Interface Control Panel”).
2. Route your microphone or instrument input directly to the headphone output.
3. Adjust the mix knob so you hear yourself.

Now you’re hearing yourself through hardware (sub-1ms latency) instead of Logic. Record in Logic normally—the recording is placed in time correctly because Logic compensates for its reported interface latency.

This is the professional technique for vocal and guitar recording.

Real Logic Pro Latency Numbers

On a modern Mac with a quality interface:

M1/M2 Mac, 128 samples, 48kHz, Core Audio: 5–10ms actual round-trip (Logic reports ~13ms, but Core Audio is efficient)

M1/M2 Mac, 64 samples, 48kHz: ~3–5ms actual

Intel i7, 256 samples, 48kHz: ~10–15ms

Intel older Core i5, 512 samples: ~20–30ms

Anything under 15ms is professional. Under 10ms is excellent.

Checking Your Actual Latency

Logic reports latency, but it’s sometimes optimistic. Test actual latency using a <a href=”https://soundlatencytest.com/audio-latency-test/”>loopback audio test</a>.

Or use this quick method:

1. Generate a click track and record it back into a second track.
2. Measure the sample offset between the two.
3. Convert to milliseconds: (Sample Offset / Sample Rate) × 1000.

If reported latency is 13ms but actual is 25ms, your interface driver might be reporting inaccurately. Update it from the manufacturer.

Sample Rate (Minimal Impact)

Sample rate affects latency per buffer, but slightly:

44.1kHz vs 48kHz at 128 samples: Less than 1ms difference.

44.1kHz at 128 samples: 2.9ms buffer latency 48kHz at 128 samples: 2.67ms buffer latency

The difference is negligible. Use 48kHz for consistency with video/streaming work. Don’t change sample rate chasing latency.

Troubleshooting High Latency

Symptom: Latency is very high (30ms+) even at 64 samples.

1. Check Low Latency Mode is ON.
2. Confirm I/O buffer is actually set to 64 (not 512).
3. Check your audio device selection—wrong device might have higher latency.
4. Update your audio interface drivers from the manufacturer’s website.

Symptom: Clicking/popping at low buffer sizes.

Your Mac is CPU-bound. Increase I/O to 256, close background apps, freeze CPU-heavy tracks.

Symptom: Everything sounds ahead of or behind the click.

Logic’s reported latency might be off. Check if you need to adjust latency compensation in the track or use the I/O plugin (part of Logic’s built-in toolkit) to calibrate external hardware.

Quick Logic Pro Latency Checklist

• [ ] Set I/O Buffer Size to 128 samples (lower if your Mac is fast)
• [ ] Enable Low Latency Mode when recording
• [ ] Set Processing Threads to maximum
• [ ] Close unnecessary background applications
• [ ] Freeze tracks with heavy reverb or mastering plugins during recording
• [ ] Use direct hardware monitoring from your audio interface when possible
• [ ] Test actual latency with a loopback to verify reported numbers

When Low Latency Mode Isn’t Enough

If you’re still feeling lag with Low Latency Mode on and I/O at 64:

1. Use your interface’s direct hardware monitoring instead of Logic monitoring.
2. Record with monitoring OFF in Logic and listen through your interface’s mix knob.
3. Check if your interface itself has high latency (some older USB interfaces add 10ms+).

Direct hardware monitoring is zero-latency. That’s the ultimate solution for responsive recording.

---