Plugin latency compensation (also called plugin delay compensation, or PDC) is your DAW measuring how late each plugin delivers audio, then delaying every other track by the right amount so everything lines up again at the output. It works quietly most of the time. When it doesn't, you get smeared kicks, hollow phase and a mix that sounds worse the more you polish it. This guide explains what is going on under the hood, where compensation breaks, and how to check your own session.
TL;DR
- Every plugin adds some delay. Your DAW's PDC finds the slowest path and delays the rest to match, so playback stays phase-aligned.
- PDC helps mixing, but it can hurt tracking: the compensation adds lag you can feel when you record, so use low latency monitoring or constrain delay compensation while you play.
- Sidechain paths, return tracks and plugins that change their reported latency are the usual places where compensation slips.
- When something sounds off, freeze or print the offending track, then check the result against the original with a polarity flip.
- Latency problems often show up as phase and low-end issues, which is exactly what a mix analysis should catch.
Table of Contents
- What plugin latency actually is
- How delay compensation works
- Tracking versus mixing: two different jobs
- Where compensation breaks down
- How to test whether your session is aligned
- Latency and the plugins you actually use
- Our view: latency is a mix problem, not just a technical one
- A workflow you can copy
- Catch the symptoms before you release
- FAQ
- Sources
What plugin latency actually is
A plugin cannot always process audio instantly. A simple EQ may work sample by sample and add almost nothing. A look-ahead limiter, a linear-phase filter, a pitch corrector or a convolution reverb needs to see a chunk of audio before it can output anything, so the sound comes out late.
Apple's documentation puts it plainly: all plug-ins cause timing delays, and the more processor-intensive a plug-in is, the bigger its latency will be. Steinberg says the same about dynamics processors with look-ahead, which need a brief time to process the audio fed into them.
Latency is reported in samples, and the time it represents depends on your sample rate. A published plugin latency table shows one plugin, a de-esser, at 2675 samples at 44.1 kHz. Divide 2675 by 44,100 and you get about 61 ms. That is long enough to turn a snare into a flam if nothing compensates for it. At the other end, one hardware-plus-software mixing system lists a latency of only 4 samples at 44.1 and 48 kHz, which is far below anything you could hear.
A quick conversion worth memorising: milliseconds = samples ÷ sample rate × 1000. At 48 kHz, 48 samples is 1 ms.
How delay compensation works
The idea is simple. Your DAW asks each plugin how many samples of delay it adds, adds those up along each signal path, and finds the path with the most latency. It then delays every other path by the difference. Apple describes this as identifying the channel strip with the maximum latency and delaying the others to match. Ableton's version compensates audio, automation and modulation by offsetting all tracks by the required amount, which matters because automation that drifts from the audio is a quiet source of mix problems.
Think of it like a relay team. Everyone has to cross the line together, so the fastest runners wait for the slowest one. Nothing is wrong with the fast runners. The whole session simply plays back later than it would without the slow plugin.
That last point has a cost. Because the DAW is holding everything back to match the slowest path, you may notice a small gap between pressing play and hearing the tracks settle in. Apple notes that with PDC on, there can be a slight lag between hitting play and the tracks syncing, in proportion to the latency being compensated.
Where to find the setting
The name differs between DAWs, but the function doesn't:
- Logic Pro: plug-in latency settings sit in the project settings, with a choice between compensating all plug-ins or only some.
- Cubase: a dedicated plugin delay compensation system, with a constrain option for live playing.
- Ableton Live: a Delay Compensation toggle in the Options menu.
- Ardour: a status area shows the latency compensation it applies, and a Disable PDC button lets you switch it off.
If you have ever flipped it off to save CPU, remember to flip it back before you mix. A session that sounds fine while one plugin is bypassed can fall apart when you re-enable it.
Tracking versus mixing: two different jobs
This is the part that trips people up. Compensation is brilliant for mixing and awkward for recording.
When you mix, you don't care that playback starts a fraction late. You care that kick, bass and overheads arrive together. Leave PDC on and keep your latency-heavy plugins where you need them.
When you track, you care about the opposite. A vocalist hearing themselves 30 ms late will start to drag or rush. Most DAWs provide a Low Latency Monitoring or "constrain delay compensation" mode, which temporarily bypasses high-latency plugins on record-enabled tracks so the performer hears a quick, dry signal.
The latency a performer feels isn't only about plugins either. It is the sum of buffer size, converter time and plugin processing. Ardour's manual notes that analogue-to-digital-to-analogue conversion alone takes roughly 1.5 to 2 ms. Another manual gives a similar figure, about 1 ms for analogue I/O against around 0.02 ms for digital I/O. So even a session full of zero-latency plugins has a floor.
That is why many engineers monitor outside the computer when timing is critical. If you record podcasts or two-person sessions, this practical guide to a two-person podcast setup is a useful read on keeping monitoring comfortable for the people on the mics.
A tracking routine that works
- Set your buffer as low as your computer can handle without crackles. Lower buffers raise the load on your system.
- Turn on low latency monitoring or constrain delay compensation.
- Put the limiter, the pitch corrector and the big reverbs on hold until after the take.
- If the performer still feels lag, switch to direct hardware monitoring from your interface.
- Before mixing, switch the constraint off and let full compensation back in.
A common rule of thumb from engineers is to keep total round-trip latency around 5 ms or less for critical tracking. It is a guideline rather than a law, and some players are fussier than others.
Where compensation breaks down
PDC is not a set-and-forget switch. These are the situations I would check first.
Sidechain and return paths
Ableton's own FAQ says that some routing, such as return tracks and sidechain paths, may not receive the same compensation as ordinary audio tracks, and that you may need to adjust or disable particular sends to restore sync. Other DAWs have their own quirks, so read your manual.
A practical symptom: you sidechain a bass compressor from the kick, and the ducking feels late or early compared to the kick itself. The compressor is working perfectly. The trigger signal is simply not where you think it is in time.
Plugins with variable latency
Some plugins change their latency when you switch a mode, such as linear-phase versus minimum-phase, or a higher oversampling setting. If the plugin changes its reported latency during playback and the DAW doesn't re-read it, compensation goes stale. A familiar forum complaint is exactly this: Logic doesn't update the latency figure until you stop and restart.
The fix is boring and reliable. After changing a mode that affects latency, stop playback, restart it, and if needed save and reopen the session.
Parallel processing
Parallel compression, parallel saturation and any "duplicate the track and blend" trick depend entirely on the two copies being aligned. If one copy goes through a plugin that reports its latency wrongly, you get comb filtering instead of thickness. Roughly speaking, a shift of just a few samples is enough to thin out the high end, and a larger shift hollows out the low mids.
If your parallel bus sounds thinner when you raise it, that is the signature of misalignment. Our phase issues fix guide walks through how to hear and repair it.
Hardware inserts and external gear
Sending a track out to an outboard compressor and back adds the converter round trip plus any interface buffer. Most DAWs have a ping or manual offset for this. Measure it once, enter the value, and your hardware inserts behave like plugins.
How to test whether your session is aligned
You don't need to trust anything. Test it.
- Make a click track. Put a single sample impulse or a short click on one audio track.
- Duplicate it. Put the second copy on another track.
- Insert the suspect plugin on one copy only. Set it to do as little as possible, so it is effectively transparent.
- Flip polarity on one track. If both are aligned, the two copies cancel to silence. If you hear or see a residual click, they are out of time.
- Zoom in on the waveform to measure the gap in samples, then compare it to what the plugin reports.
This takes two minutes per plugin. Do it once for the plugins you use all the time, and write the results down.
When in doubt, print it
If a plugin consistently misreports, stop fighting it. Freezing or bouncing the track renders the effect into audio, so the DAW now deals with plain audio at a known position. Plugin makers themselves point this way: variable latency is a common source of confusion for compensation engines. Rendering the track removes the uncertainty completely.
Latency and the plugins you actually use
Not every plugin deserves a worry. Here is a rough way to think about it by type:
| Plugin type | Typical latency behaviour | What to watch |
|---|---|---|
| Analogue-style EQ and compressors | Usually zero or near zero | Rarely an issue |
| Linear-phase EQ | Noticeable, often grows with low frequency resolution | Parallel buses, low-end layering |
| Look-ahead limiters and compressors | Fixed look-ahead time | Sidechain triggers, automation timing |
| Pitch correction and vocal tools | Often high | Tracking, parallel vocal stacks |
| Convolution reverbs | Can add delay depending on settings | Pre-delay you set by hand |
| Oversampled saturators | Rises with oversampling setting | Variable latency, restart after change |
The categories above are general patterns, not a promise about any particular product. Check each plugin's documentation, or use the test above.
Multiband compression on drums
Since many producers ask about multiband compression on drums, it is worth saying how latency fits in. Multiband compressors split the signal into bands with crossover filters, and some designs use linear-phase crossovers that report extra latency. On a drum bus, that matters in two ways.
First, if you process the bus in parallel, for example crushing the low band of the kick and snare and blending it back, the two paths must stay aligned or the low end will phase-cancel. Second, the crossover itself can smear transients if you set the bands too close together. Start with a gentle two-band split, compress the low band lightly to control the boom, and leave the highs alone. If the attack of the snare softens after you add the plugin, check for latency mismatch before you blame your settings.
We also cover how the gain going into those plugins changes their behaviour in our guide to gain staging in mixing.
Our view: latency is a mix problem, not just a technical one
We look at a lot of mixes, and timing and phase trouble is rarely announced by an error message. It arrives as a kick that doesn't hit as hard as the reference, a bass that feels thin in mono, or a parallel bus that gets worse when you turn it up. By the time a producer calls it a "phase issue", the root cause is often a compensation slip made hours earlier.
Our view is that you should treat latency like gain staging: set the discipline once and keep it. Know which plugins in your template are heavy. Print or freeze when a plugin misbehaves. Test new plugins with the polarity trick before they go on a parallel bus. And never trust your ears alone when a session has fifty tracks and several buses, because your ears adapt quickly to a slightly hollow sound.
This is also why we built our analysis to look at more than loudness. A report that checks phase, stereo width, frequency masking and device translation together will usually point at the symptom that latency causes, even when you can't see the cause yourself. For a deeper look at how we handle this in a working session, read our post on fixing plugin latency in mix sessions.
— AubioMix
A workflow you can copy
Here is a routine that keeps latency under control without slowing you down.
- Build a template with known plugins. Keep a short list of the heavy ones, and note their latency in samples.
- Track light. Record with minimal processing, using low latency monitoring.
- Switch compensation fully on before mixing. Restart playback after the change.
- Check sidechains and returns. Confirm that the trigger signal lines up with the audio it controls.
- Run the polarity test on any parallel bus.
- Print problem tracks. If a plugin reports inconsistently, render it and move on.
- Listen in mono once the structure is done. Timing errors appear fast when the sides collapse.
- Run an analysis on a bounce before you call it finished.
If your mixing process feels slow, our workflow speed-up guide has more on templates and checks that save time. For delay effects you set by hand, such as pre-delay and tempo-synced echoes, which are a different thing from latency, see the role of delay in mixing.
Catch the symptoms before you release
If you have worked through the checks and still feel something is off, a second pair of ears helps. You can upload a bounce to AubioMix and get a written and visual report covering phase, stereo width, frequency masking, compression, loudness and translation, with specific steps to fix what it finds. A single mix review costs £4.99, and the Professional plan is £19.99 per month if you mix regularly. You can read how each area is judged on our evaluation framework page.
FAQ
Should I leave plugin delay compensation on all the time?
For mixing, yes. It keeps every track and bus in time, so you can use any plugin without worrying about alignment. For tracking, use low latency monitoring or the constrain option so the performer isn't hearing delayed sound.
Why does my mix sound different when I turn compensation off?
Because tracks are no longer being delayed to match the slowest path. Parallel buses and layered sounds fall out of time, which causes comb filtering. Turn it back on and restart playback.
Can I fix a plugin that reports its latency wrongly?
Not inside the plugin, but you can work around it. Render or freeze the track so the effect is printed into audio, or nudge the track manually by the measured number of samples. Use the polarity test to confirm the result.
How much latency is too much for recording?
Many engineers aim for around 5 ms of round-trip latency or less for critical tracking, though sensitivity varies by player. Even with zero-latency plugins, converters add roughly 1.5 to 2 ms, so the buffer and your monitoring method matter most.
Sources
- Work with plug-in latencies in Logic Pro for Mac, Apple Support
- Plug-In Delay Compensation, Cubase Elements 15.0
- Plugin Latency Table, A.O.M. Support
- Console 1 Mixing System Mk III, Softube
- Delay Compensation FAQ, Ableton
- Other Toolbar Items, The Ardour Manual
- Latency Considerations, The Ardour Manual
- Compensating for Latency, Eventide H9000 2.0 documentation