Set Up an Audio Interface in Logic Pro
A no-drama setup path for audio interfaces, buffer size, monitoring, and first signal checks in Logic Pro.
Audio interface problems usually feel mysterious because sound can fail in several places: macOS, Logic's audio device, the track input, interface gain, monitoring, or the output path. The fix is to walk through the chain in order.
Do the boring setup before the musician is waiting. A ten-second test recording tells you more than twenty minutes of menu clicking.
Quick answer
If you are in Logic Pro right now, do not start by opening every menu. Connect the interface before opening Logic Pro. Plug headphones or monitors into the interface you selected. Then move through the four checks below in order.
The order matters because recording work usually breaks earlier than it looks. A wrong track, region, input, bus, or range can make the last setting look guilty when it is only receiving a bad setup.
Use this as the short version before reading the full guide.
- Pick the audio device intentionally: Use the same interface for input and output unless you have a specific reason to aggregate devices.
- Set buffer size for recording, not mixing: A small buffer feels tighter to the performer because the round-trip delay is lower.
- Match mono and stereo inputs: A single microphone is usually mono.
- Choose one monitoring path: Direct monitoring from the interface is often the safest way to avoid delay.
Before you start
- Connect the interface before opening Logic Pro.
- Plug headphones or monitors into the interface you selected.
- Turn phantom power on only for condenser microphones that need it.
- Record a short phrase before the real take.
A clean pass from start to finish
Run this as one clean pass, not as disconnected tricks. Begin with the first checkpoint: pick the audio device intentionally. Then move to the second: set buffer size for recording, not mixing. Those two checks make the project readable before you make detailed changes.
After that, use the next two checkpoints as the decision stage: match mono and stereo inputs, then choose one monitoring path. This is where you stop guessing and let the screen show whether the sound, timing, routing, or edit is behaving the way the song needs.
If you change more than one thing at once, write down what you changed or save a new version. Logic Pro is fast enough that a session can go from fixed to confusing in under a minute. Small, named moves are easier to trust later.
1. Pick the audio device intentionally
Use the same interface for input and output unless you have a specific reason to aggregate devices. One device keeps clocking, monitoring, and routing simpler.
If Logic still plays through the laptop, the session may be fine but the output device is wrong. Fix the output before touching the track.
2. Set buffer size for recording, not mixing
A small buffer feels tighter to the performer because the round-trip delay is lower. Try 64 or 128 samples while tracking. If the project crackles, go to 256 or bypass heavy plugins.
When recording is done, raise the buffer for mixing. A dense mix does not need the same low-latency setting as a live vocal take.
3. Match mono and stereo inputs
A single microphone is usually mono. Put it on a mono audio track and choose Input 1 or Input 2, not a stereo pair. Stereo tracks are for stereo keyboards, stereo guitar processors, or two-mic setups.
If the waveform appears on only one side, you probably recorded a mono source onto a stereo track.
4. Choose one monitoring path
Direct monitoring from the interface is often the safest way to avoid delay. Logic software monitoring is useful when the performer needs effects from the session. Using both can create a doubled vocal.
Ask the performer what they hear. If they hear a slapback echo, monitoring is wrong even if the recording itself is clean.
Decision table
| Symptom | First check | Likely fix |
|---|---|---|
| No input meter | Track input and interface gain | Choose the correct input and raise preamp gain |
| Delayed voice | Monitoring path | Use direct monitoring or lower buffer |
| Crackles | Buffer and plugins | Raise buffer or bypass heavy plugins |
| One-sided recording | Track format | Use a mono track for one mic |
Checkpoint table
| Checkpoint | What should be true | If it is not true |
|---|---|---|
| Pick the audio device intentionally | If Logic still plays through the laptop, the session may be fine but the output device is wrong. | Back up and fix the setup before continuing. |
| Set buffer size for recording, not mixing | When recording is done, raise the buffer for mixing. | Do the smaller edit instead of rebuilding the whole part. |
| Match mono and stereo inputs | If the waveform appears on only one side, you probably recorded a mono source onto a stereo track. | Check what is selected, then repeat the change deliberately. |
| Choose one monitoring path | Ask the performer what they hear. | Use the mixer or playback context as the final judge. |
Before and after check
Before the change, make one short playback pass and name the exact problem in plain words: late entrance, dull vocal, wrong input, harsh consonant, missing output, messy routing, clipped bounce, or whatever the session is actually doing. If you cannot name it, you are not ready to fix it yet.
After the change, play the same section at the same volume. Louder almost always sounds better for ten seconds, so level-match when you are judging recording decisions. The useful question is not whether the edit is impressive. It is whether the part sits better without pulling attention away from the song.
Check the edges of the fix. In Logic Pro, a repair can solve the center of a problem while damaging the bar before it, the breath after it, the bus return, or the export tail. A good before/after pass includes a little lead-in and a little space after the moment you changed.
If the after version only feels better while you are watching the screen, take a break and listen again without touching the mouse. Visual neatness is helpful for editing, but the final test is still playback. Keep the version that makes the project easier to finish.
What not to chase yet
Do not chase polish before the basic workflow is stable. For this topic, the first two checkpoints have to make sense before you worry about the smaller details: pick the audio device intentionally, then set buffer size for recording, not mixing. Fancy settings cannot rescue a confused source.
Do not copy numbers blindly from another session. Buffer sizes, EQ points, quantize strength, compression timing, send levels, and bounce choices all depend on the material. Use examples as starting points, then move the control until this project sounds and behaves correctly.
Do not keep editing because the tool is available. Logic Pro gives you enough control to over-fix almost anything. Stop when the problem is gone and the performance still feels like a performance.
What good looks like
The recording workflow is working when you can explain what changed without pointing at a random plugin window. If the fix depends on luck, the session is not stable yet.
After the main pass, close the editor you were using and play the section from a few bars before the change. A good edit survives context. A bad edit only sounds correct when the screen is zoomed into the problem.
Keep one version before the major change and one version after it. Logic Pro projects can move quickly, and a clean fallback saves more time than trying to reverse a dozen tiny edits later.
If it still feels wrong
If the result still feels wrong, return to the signal chain. Ask whether the source is clean, whether the region edit is correct, whether the track is routed where you think it is, and whether the mixer confirms what your ears are telling you.
Do not add another processor just because the current one did not solve the issue. In Logic Pro, many problems are earlier than the plugin slot: wrong input, messy region boundaries, doubled monitoring, over-quantized MIDI, or a bus that is louder than the dry track.
When you get stuck, simplify the project. Mute everything except the source and the one track or aux it depends on. If the problem disappears, bring the session back one group at a time until the conflict shows itself.
Common mistakes to avoid
- Recording a mono mic onto a stereo track. Fix it by returning to the first visible control in the chain and confirming it before you touch a plugin.
- Tracking through a heavy master chain. Fix it by listening to the section in context, then changing only the thing that fails the playback test.
- Leaving both direct monitoring and software monitoring active. Fix it by saving a version, making the edit smaller, and checking whether the song still feels natural.
- Changing random preferences before checking the cable, gain, and input number. Fix it by simplifying the session view until the routing, region, or setting is obvious again.
Practice pass
Make one test project named Interface Check. Record ten seconds of voice or guitar at 64, 128, and 256 samples. Write down which setting feels good and which setting is stable on your Mac.
When to move on
You are done when the change helps the song at normal listening volume. Not when the screen looks tidy, not when every meter behaves perfectly, and not when the analyzer is pretty.
Print or bounce a short reference after the fix. Listening outside the edit screen catches problems that are invisible while you are staring at regions, lanes, and meters.
Sources checked
This draft was checked against current Apple Logic Pro documentation and release notes before writing. Source links used for version-sensitive claims on May 16, 2026:
- Apple guide to recording audio
- Apple guide to input monitoring latency
- Apple guide to avoiding system overloads
FAQ
What buffer size should I use in Logic Pro?
Use 64 or 128 samples while recording if your Mac stays stable. Use higher values like 512 or 1024 while mixing.
Why is there a delay when I record in Logic Pro?
That delay is input monitoring latency. It can come from buffer size, sample rate, interface conversion, interface software, and plug-ins.
Should software monitoring be on or off?
Use software monitoring if you need Logic's effects in the headphones. Turn it off if your interface provides direct monitoring.
Why is Logic Pro recording silence?
Check the audio device, track input, record enable, input monitoring, interface gain, mute/solo state, and whether the mic needs phantom power.
