How to Stop Latency When Recording Guitar (Practical Fix Guide)

Nothing kills a recording session faster than hearing your guitar a half-second after you pick a note. That slapback delay between your pick attack and what comes through your headphones makes it impossible to play in time, and it’s the number one reason beginners abandon home recording before they even get started.

I’ve been tracking guitars through a home setup for over a decade, and I still occasionally run into latency problems when I change DAWs, update drivers, or try a new interface. The good news: once you understand what causes it, the fix usually takes under two minutes.

What Latency Actually Is (And Why It Happens)

Latency is the time gap between when you play a note and when you hear it back through your headphones or monitors. In a live room playing through a physical amp, this delay is essentially zero. But when you record through a computer, your signal has to make a round trip:

Guitar → Cable → Audio Interface (A/D conversion) → USB/Thunderbolt → Computer/DAW → Plugins → USB/Thunderbolt → Audio Interface (D/A conversion) → Headphones

Every single step in that chain adds time. The analog-to-digital and digital-to-analog conversions in your audio interface each take a fixed amount of time (usually around 1ms each). The USB transfer adds a bit more. But the biggest variable is the buffer size in your DAW, and that’s where most latency problems live.

Buffer Size: The One Setting That Matters Most

Your audio buffer is a chunk of audio data that your computer processes at once. Think of it like a bucket: a bigger bucket means your computer has more time to process the audio, but it also means you wait longer before hearing the result.

Buffer size is measured in samples, and the actual delay depends on your sample rate. Here’s the math:

Latency (ms) = Buffer Size (samples) ÷ Sample Rate (Hz) × 1000

At the standard 44.1kHz sample rate:

Buffer Size	One-Way Latency	Approximate Round-Trip	Playability
32 samples	~0.7ms	~3ms	Perfect, but most systems can’t handle it
64 samples	~1.5ms	~5ms	Excellent, works on modern machines
128 samples	~2.9ms	~6ms	Sweet spot for most setups
256 samples	~5.8ms	~12ms	Noticeable for fast players
512 samples	~11.6ms	~23ms	Uncomfortable for most guitarists
1024 samples	~23.2ms	~46ms	Unusable for live monitoring

The round-trip numbers include both input and output buffer passes plus a couple milliseconds for A/D and D/A conversion. At 128 samples and 44.1kHz, you’re looking at roughly 6ms total. For context, standing 6 feet away from your guitar amp introduces about 5ms of delay from the speed of sound alone. So 6ms is something your brain already handles without thinking.

My rule of thumb: Record at 128 samples. If you get crackles, bump to 256. If your system is solid, try 64. Never record at 1024; that’s for mixing only.

Audio Drivers: ASIO vs Core Audio vs WDM

Your audio driver is the software layer between your DAW and your audio interface. Pick the wrong one and no amount of buffer tweaking will save you.

Windows: Use ASIO, Period

Windows ships with two audio driver types: WDM (Windows Driver Model) and the older MME (Multimedia Extensions). Both route audio through the Windows audio stack, which adds significant latency, often 50ms or more, no matter what buffer size you set.

ASIO (Audio Stream Input/Output) bypasses the Windows audio stack entirely and talks directly to your interface hardware. The difference is night and day. If you’re recording guitar on Windows and haven’t switched to ASIO, this is almost certainly your problem.

Most audio interfaces ship with their own ASIO driver. The Focusrite Scarlett 2i2, for example, installs Focusrite ASIO automatically. If your interface doesn’t have a dedicated ASIO driver, download ASIO4ALL (free). It’s not as good as a manufacturer’s native driver, but it’s dramatically better than WDM.

Mac: Core Audio Just Works

macOS has Core Audio built into the operating system, and it’s already low-latency by design. There’s no separate driver to install. Open your DAW, select your interface as the audio device, set your buffer to 128, and you’re good. This is one of the genuine advantages of recording on a Mac.

Linux: JACK

If you’re on Linux, you’ll use JACK (JACK Audio Connection Kit). It provides professional-grade low-latency routing, but the setup is more involved. Most Linux musicians pair JACK with Ardour or Reaper.

Direct Monitoring: The Zero-Latency Workaround

Here’s a secret that solves latency for 90% of guitarists: you don’t have to monitor through your computer at all.

Most audio interfaces, including the Scarlett 2i2, Audient iD4, MOTU M2, and Universal Audio Volt series, have a Direct Monitor switch or knob. When you enable it, your guitar signal gets routed straight from the input to the headphone/monitor output at the hardware level. The signal never touches your computer, so the latency is effectively zero.

The trade-off: you hear your dry guitar signal, not the processed sound with amp sims and effects. If you’re recording guitar at home using amp simulation plugins, this means you’ll hear a thin, clean tone while playing, but the DAW still records the dry signal and applies your plugins on playback.

Some interfaces have a blend knob (like the Scarlett’s monitor mix) that lets you blend the direct signal with the DAW output. Set it mostly toward “direct” with just a touch of the DAW signal so you can hear the click track and other instruments.

When to use direct monitoring:

• You can’t get your buffer below 256 without crackling
• You’re tracking rhythm parts where the exact processed tone doesn’t affect your performance
• You’re doing quick scratch tracks or demos

When you need software monitoring:

• You’re recording with specific amp sim tones and need to hear them to play the right dynamics
• You’re using real-time effects like delay or reverb that change how you play
• You’re tracking lead lines where tone shapes your phrasing

DAW-Specific Settings for Low Latency

Every DAW handles audio settings differently. Here’s where to find the critical latency controls in the four most popular DAWs:

Reaper

Options → Preferences → Audio → Device. Select your ASIO driver, set the buffer to 128. Reaper also has a killer feature: anticipative FX processing, which pre-renders plugin output on tracks you’re not actively recording to. This frees up CPU for the track you’re monitoring in real time. Make sure it’s enabled under Preferences → Audio → Buffering.

Ableton Live

Options → Preferences → Audio tab. Choose your ASIO driver (Windows) or Core Audio (Mac). Set Buffer Size to 128. Ableton shows the actual input and output latency numbers right there on the audio preferences page, so you can see exactly what you’re working with. Also disable Reduced Latency When Monitoring if it causes issues with complex routing, or enable it when tracking a single guitar part.

Logic Pro

Logic Pro → Settings → Audio. Set I/O Buffer Size to 128. Logic has a built-in Low Latency Mode button in the toolbar (looks like a speedometer). Enabling it automatically bypasses any latency-inducing plugins on the monitoring path while you record, then re-enables them on playback. It’s one of the best low-latency implementations in any DAW.

FL Studio

Options → Audio Settings. Select your ASIO driver and set the buffer length. FL Studio also has a smart disable feature for plugins that aren’t actively processing audio. Enable it under General Settings to free up CPU. Note that FL Studio shows buffer length in milliseconds rather than samples, so aim for 5-6ms.

USB Bandwidth and Connection Issues

Your USB connection can introduce latency or instability even with perfect driver and buffer settings. A few things to watch:

Use a direct USB port on your computer, not a hub. USB hubs add a small amount of latency and can cause intermittent audio dropouts, especially under heavy USB traffic. If your keyboard, mouse, webcam, MIDI controller, and audio interface are all running through the same hub, you’re asking for trouble.

USB 2.0 vs USB 3.0 vs USB-C: For stereo guitar recording, USB 2.0 has more than enough bandwidth. The bottleneck is never the data transfer speed; it’s the driver and buffer processing. USB-C interfaces aren’t faster for audio, they just use a newer connector. Thunderbolt interfaces do have slightly lower latency (1-2ms less), but for home guitar recording, the difference is academic.

Use the cable that came with your interface. Cheap USB cables can cause intermittent disconnects and audio glitches that feel like latency but are actually dropout artifacts.

CPU Load and Plugin Latency

Even at a low buffer size, you can still experience latency if your CPU is struggling. Here’s what eats CPU during recording:

Plugin Delay Compensation (PDC)

Certain plugin types introduce their own processing delay, independent of your buffer size:

• Linear-phase EQs: 10-50ms of latency (they need to “look ahead” to process)
• Look-ahead compressors and limiters: 5-20ms
• Oversampled plugins (some amp sims): Variable, depends on oversampling rate
• Convolution reverbs: Typically 1-5ms

Your DAW compensates for this delay on playback so everything stays in time. But when you’re monitoring live input, that plugin latency stacks on top of your buffer latency. If you’re running an oversampled amp sim, a linear-phase EQ, and a look-ahead limiter on your guitar’s input channel, you might be adding 30-60ms of plugin latency on top of your 6ms buffer latency.

The fix: Only put essential plugins on your monitoring chain while recording. Save the fancy processing for mixing.

Background Processes

Your CPU has a fixed amount of processing power. Anything else competing with your DAW adds to the load:

• Close your browser. Chrome alone can use 2-4GB of RAM and significant CPU
• Disable Wi-Fi and Bluetooth during recording sessions
• Set your power plan to High Performance (Windows) or disable Power Nap (Mac)
• Close Dropbox, Google Drive, and other sync services that cause random disk access spikes

The Freeze/Bounce Workflow for Heavy Sessions

By the time you’re tracking your fifth or sixth guitar layer, your session might be loaded with virtual instruments, amp sims across multiple tracks, and a chain of mix plugins on every bus. Your CPU is sweating, and lowering the buffer to 128 causes an avalanche of crackles and pops.

The solution is freezing or bouncing tracks you’ve already finished recording:

1. Freeze: Temporarily renders a track to audio, bypassing its plugins. The track plays back as a simple audio file, freeing up CPU. You can unfreeze later to edit plugins. Available in Reaper, Logic, Ableton, and FL Studio.

2. Bounce/Render in Place: Permanently renders a track to audio. Destructive (you lose plugin editability unless you save the original), but frees up the most CPU.

My workflow: Once I’m happy with a guitar take, I freeze the track immediately. By the time I’m layering lead parts over dense rhythm sections, my CPU is barely working because every finished track is just playing back a frozen audio file. I can drop my buffer to 64 samples and monitor through my amp sim plugin with virtually no latency.

Quick Latency Troubleshooting Checklist

If you’re still hearing a delay after reading all of this, run through this list:

1. Check your audio driver. ASIO on Windows, Core Audio on Mac. If it says WDM, MME, or DirectSound, that’s your problem.
2. Set buffer to 128 samples (or 5-6ms if your DAW shows milliseconds).
3. Enable direct monitoring on your interface to rule out software issues.
4. Remove plugins from the input/monitoring channel. Add them back one at a time to find the culprit.
5. Check USB connection. Move to a direct port, try a different cable.
6. Freeze all finished tracks to free up CPU before recording new parts.
7. Close background apps. Browsers, cloud sync, chat apps.
8. Update your interface driver. Manufacturer websites usually have newer versions than what shipped on the CD.

If you’ve gone through every step and still have noticeable latency, your computer might simply be underpowered for real-time audio at low buffer sizes. A machine with at least an Intel i5 (or AMD Ryzen 5) and 16GB of RAM handles 128-sample buffers comfortably in any modern DAW.

Wrapping Up

Latency doesn’t have to be a mystery, and it definitely doesn’t have to ruin your guitar recordings. In most cases, the fix is switching to the right audio driver and setting your buffer to 128 samples. That gets you under 6ms of round-trip delay, which is fast enough that your brain can’t distinguish it from playing through a real amp in the same room.

For sessions where plugin load makes low buffers impossible, direct monitoring and track freezing keep you recording without compromise. The tools are already built into your audio interface and your DAW. You just need to know where to find them.

If you’re still building your recording setup, check out our complete guide to recording guitar at home and our Focusrite Scarlett 2i2 review for the interface I recommend to every guitarist who asks.