If you’ve ever played a guitar or sung into a microphone and heard your own voice arrive a fraction of a second late, you’ve experienced plugin latency. I ran into this problem constantly during my first year of recording, and it drove me crazy until I figured out what was actually happening inside my DAW.
This guide will walk you through exactly how to fix latency when monitoring through plugins. I’ll cover the technical reasons behind the delay, the practical settings you can change right now, and the workflow tips that professional producers use every day.
By the end, you’ll understand buffer size, sample rate, delay compensation, and low latency mode well enough to troubleshoot any monitoring delay in any major DAW.
Table of Contents
What Is Plugin Latency and Why It Matters
Plugin latency is the small delay that happens when your audio signal passes through software plugins in your DAW. Every plugin needs time to analyze and process your audio. That processing time creates a delay between when you play or sing and when you hear the processed sound back through your headphones or monitors.
Think of it like an echo, except the echo is fast enough that your brain registers it as “off” rather than as a separate sound. The longer the chain of plugins, the longer the total delay. Some plugins like linear phase EQs and advanced reverbs can add thousands of samples of latency on their own.
Latency matters because anything over about 10-15 milliseconds becomes musically disruptive. When I tracked vocals at 512 samples with three plugins in the chain, I could hear myself landing behind the beat. Singers feel it most acutely, but drummers, guitarists, and keyboardists all struggle with monitoring delay.
The good news is that you can almost always reduce monitoring latency to a workable level. The trick is balancing low latency against CPU load and audio quality, which is what the rest of this guide covers.
Quick Fixes for Plugin Latency
If you need a fix right now and don’t have time to read the full guide, here are the fastest ways to reduce plugin latency while monitoring.
Lower your audio interface buffer size to 128 samples (or 64 if your CPU can handle it).
Enable Low Latency Mode in your DAW if it has one (Logic, Pro Tools, Cubase, Studio One all do).
Bypass heavy plugins on the input monitoring channel while tracking.
Use your audio interface’s direct monitoring instead of DAW input monitoring.
Close other applications using CPU in the background.
Update your audio drivers (ASIO on Windows, Core Audio on Mac).
These six steps solve the problem for about 80% of people. The sections below explain each fix in detail and show you exactly where to find the settings in your DAW.
How to Fix Latency When Monitoring Through Plugins: Step-by-Step Methods
The most reliable way to fix latency when monitoring through plugins is to work through a layered approach. I usually start with the simplest fix, test the result, and only move to the next step if needed. Here’s the order I recommend.
Step 1: Set your recording buffer size between 64 and 256 samples. This is the single biggest factor in monitoring latency. Most audio interfaces let you change buffer size from their control panel or from inside your DAW preferences.
Step 2: Match your project’s sample rate to your interface’s sample rate. A mismatch creates extra conversion delay that stacks on top of plugin latency.
Step 3: Use Low Latency Mode for tracking, then disable it for mixing. Low Latency Mode automatically routes around plugins that exceed a certain sample delay.
Step 4: Free up CPU before recording. Buffer size changes only help if your CPU can deliver audio at the new buffer. Quit your browser, cloud sync tools, and other audio apps before you hit record.
Step 5: Consider direct monitoring for zero-latency tracking. When you don’t actually need effects in your headphones while recording, direct monitoring skips the entire plugin chain and gives you truly instant audio.
Following these steps in order fixes monitoring latency for nearly every session I run. If you still hear delay after applying all five, the issue is usually a single plugin with extreme latency, which I’ll cover in the delay compensation section.
Buffer Size Optimization for Recording
Buffer size is the number of audio samples your computer processes in a single chunk. Smaller buffers mean less latency, but more work for your CPU. Larger buffers give your CPU breathing room but add perceptible delay during monitoring.
The latency you actually hear equals your buffer size divided by your sample rate, multiplied by 1000 to get milliseconds. For example, 256 samples at 44.1kHz equals about 5.8ms of round-trip latency. That is the delay between playing a note and hearing it back through plugins.
Here is a buffer size to latency conversion table I use when planning sessions.
| Buffer Size | Latency at 44.1kHz | Latency at 96kHz | Best For |
|---|---|---|---|
| 64 samples | 1.5 ms | 0.7 ms | Live performance, fast monitoring |
| 128 samples | 2.9 ms | 1.3 ms | Standard recording sessions |
| 256 samples | 5.8 ms | 2.7 ms | Tracking with moderate plugin chains |
| 512 samples | 11.6 ms | 5.3 ms | Mixing, light plugin use |
| 1024 samples | 23.2 ms | 10.7 ms | Heavy mixing with many plugins |
For monitoring through plugins, 128 samples is my default. It gives 2.9ms of latency at 44.1kHz, which most musicians cannot perceive. If my CPU is struggling, I bump to 256 samples and use Low Latency Mode to keep plugins in the chain.
Remember that round-trip latency is roughly double the input/output figure. Add the latency from your plugins on top, and the total delay between playing and hearing can climb quickly. Always measure what you are actually hearing, not just what the settings show.
Sample Rate and Latency Trade-offs
Sample rate is the number of audio samples your system captures per second. Common rates are 44.1kHz, 48kHz, 88.2kHz, and 96kHz. Higher sample rates capture higher frequencies and give you more headroom for time-domain processing, but they also affect latency.
At the same buffer size, a higher sample rate produces lower latency because the buffer represents a shorter slice of time. A 256-sample buffer at 96kHz gives you 2.7ms of latency versus 5.8ms at 44.1kHz. The trade-off is that your CPU has to do more work per second.
For most home studios recording rock, pop, and voice work, 44.1kHz or 48kHz is plenty. I record at 48kHz because it lines up better with video projects, and I use 128 samples for tracking. That gives me 2.7ms of monitoring latency with plenty of CPU headroom for plugins.
If you record acoustic instruments or work on classical and jazz projects, 88.2kHz or 96kHz can capture more detail. Just make sure your interface, plugins, and computer can handle the extra load, or you’ll trade latency for clicks and dropouts.
How to Enable Low Latency Mode in Major DAWs
Low Latency Mode is a DAW feature that automatically bypasses plugins exceeding a sample threshold while you are monitoring. Each major DAW hides this setting in a slightly different place, so I put together a quick reference.
| DAW | Where to Find Low Latency Mode | Plugin Threshold |
|---|---|---|
| Logic Pro | Record button menu, or View > Low Latency Mode | No plugins bypassed automatically |
| Pro Tools | Options > Low Latency Monitoring (LLM) | Bypasses plugins above 4096 samples |
| Ableton Live | No built-in LLM, use Performance Monitor to track CPU | N/A |
| Cubase | Project menu > Constrain Delay Compensation | User-defined sample limit |
| Studio One | Mix > Pipeline Mode (per channel) | Bypasses entire channel plugins |
| Reaper | Toggle per track: right-click input FX > “Auto-bypass on record” | User-defined per track |
For Logic Pro, the keyboard shortcut Control+Shift+L toggles Low Latency Mode instantly. I keep that muscle memory from years of vocal sessions. In Pro Tools, leave Automatic Delay Compensation (ADC) on and toggle LLM from the Options menu.
Ableton Live does not have a true Low Latency Mode, but you can use its built-in freeze and flatten features for the heaviest tracks, then route the audio back into your session to free up CPU. Reaper gives you the most control because you can set per-track bypass rules for input monitoring.
Whichever DAW you use, the rule is the same. Enable Low Latency Mode before you hit record, and disable it when you are mixing so plugins come back online.
Delay Compensation and Plugin Management
Delay compensation is your DAW’s way of keeping every track time-aligned even when some plugins add latency. Most modern DAWs handle this automatically through Automatic Delay Compensation (ADC) or Plugin Delay Compensation (PDC). The catch is that compensation only kicks in during playback, not during live monitoring.
That’s why you sometimes hear perfectly aligned playback but laggy monitoring. The DAW is doing its job for the mix but cannot delay your real-time input to match. Plugins that introduce heavy latency, like convolution reverbs, look-ahead limiters, and some channel strips, can push monitoring past the point of comfort.
One real example comes from Waves’ Abbey Road Reel ADT plugin, which can add over 1881 samples of latency at 96kHz. That is roughly 20ms of delay, well past where it interferes with performance. The fix is to put plugins like this on a print track or aux send, not on the live input channel.
Another common issue is plugins getting deactivated automatically when you arm a track for recording. This is your DAW protecting you from the worst monitoring delays. If you want to keep a heavy plugin active during recording, you usually need to disable ADC, set a high buffer size, or split the chain into a print track.
For a clean workflow, I keep a template with three track types: input tracks (no plugins or only light ones), monitor sends (subtle reverbs and EQs that handle low latency), and print tracks (where heavy processing happens after the take).
Direct Monitoring vs DAW Monitoring
Direct monitoring routes your input signal through the audio interface itself, completely bypassing the DAW. DAW monitoring routes the signal through the computer, through your plugins, and back out to your headphones. Direct monitoring is instant. DAW monitoring gives you effects in your headphones but adds latency.
Use direct monitoring when you are tracking a clean signal and plan to add effects later, or when the dry signal is musically good enough on its own. Vocals, electric guitar, and acoustic guitar often sound great through direct monitoring with the right mic preamp and input gain.
Use DAW monitoring when the artist needs to hear effects to perform well. Singers who depend on reverb to feel confident, guitarists using amp sims, and podcasters using compression all need plugin monitoring. The latency tax is the trade-off, and you fix it with the buffer size and Low Latency Mode methods covered above.
Most modern audio interfaces, including the Universal Audio Apollo, Focusrite Scarlett, and PreSonus Studio series, have a hardware direct monitoring button on the front panel. Toggle it off when you want plugin monitoring, on when you need zero-latency tracking.
Hardware Solutions for Zero-Latency Monitoring
If software fixes aren’t enough, hardware can solve plugin latency at the source. Universal Audio’s Apollo interfaces include onboard SHARC DSP chips that run plugins like the UAD Neve and Lexicon emulations with effectively zero monitoring latency. RME’s TotalMix and Audient’s EVO also offer robust direct monitoring with flexible routing.
DSP-based plugins run on the interface, not your computer, so they add no buffer-based delay. The trade-off is cost and a smaller plugin library than native plugins. For producers tracking bands and serious vocalists, that trade-off is often worth it.
Another approach is a multi-output audio interface with built-in mixer software, like the MOTU 828 or the Behringer X32. These let you create zero-latency monitor mixes for each performer while the DAW handles the recording. Many professional studios rely on this setup for live tracking sessions.
If your computer struggles to keep up, a dedicated DSP interface removes the bottleneck entirely. Pair it with the buffer size and Low Latency Mode methods above, and you will have a tracking setup that feels instant.
FAQs
How do I get rid of plugin latency?
Lower your audio interface buffer size to 128 or 64 samples, enable Low Latency Mode in your DAW, and bypass heavy plugins on the input monitoring channel. For zero latency, switch to direct monitoring on your audio interface.
How do I fix latency on my monitor?
Open your audio interface control panel and reduce the buffer size to 128 samples or lower. Close background apps, update your ASIO or Core Audio drivers, and use direct monitoring if your interface supports it.
How do I fix latency delay when recording?
Start by lowering your buffer size, then enable Low Latency Mode in your DAW. If delay remains, switch to direct monitoring for instant audio, or move heavy plugins off the live input channel onto a print track.
Is 37 ms latency bad?
Yes, 37ms is well above the 10-15ms threshold most musicians can perceive. It will make it difficult to play in time or sing in tune. Use direct monitoring or lower your buffer size to bring it under 10ms.
Why does my DAW turn off plugins when recording?
Your DAW automatically deactivates plugins that add too much latency to protect your monitoring experience. Disable this only if you have a powerful computer and need the plugin in the live signal path.
Conclusion
Learning how to fix latency when monitoring through plugins comes down to understanding the relationship between buffer size, sample rate, and plugin processing time. Start with 128 samples at 48kHz, enable Low Latency Mode for tracking, and use direct monitoring whenever you can record without effects in your headphones.
For stubborn cases, split your processing between live input channels and print tracks so heavy plugins never touch the monitored signal. The result is a tracking session that feels responsive, even with a complex signal chain. Your performances will be tighter, your takes will be more confident, and mixing will go faster because you’ll be capturing the sound you actually want from the start.