Plugin Delay Compensation (PDC) Explained for Producers

What is plugin delay compensation?

Plugin delay compensation is automatic time alignment. When one plugin holds audio back, the DAW holds every other track back by the same amount so the whole mix still plays in sync.

Apple's Logic Pro guide describes the mechanism clearly: the DAW finds the channel strip with the maximum latency and delays the other channel strips by an individual amount so they all play back together^[1]. The cost is a short pause between pressing play and hearing the tracks, plus extra delay on anything you monitor live.

Without PDC, a kick with a linear-phase EQ would land late against the hi-hats, and a parallel drum bus would comb-filter against the dry drums. With it, you rarely notice latency at all until you try to record.

Why do some plugins add latency?

A plugin adds latency when it needs to see audio before it can process it. Most EQs and compressors work sample by sample and add nothing. Lookahead dynamics, linear-phase filters and FFT-based tools must buffer a chunk of audio first, and that buffer is the delay.

Lookahead is the simplest case. Ableton's Limiter offers 1.5, 3 or 6 ms of lookahead to catch fast peaks, and the manual notes that the longer the lookahead time, the higher the latency^[2]. Linear-phase EQ is the extreme case: FabFilter says linear-phase filters delay the entire signal, and higher resolution means longer latency^[3].

Converting samples to milliseconds

Latency readouts often show samples. Divide by the sample rate and multiply by 1,000: 512 samples at 48 kHz is about 10.7 ms, and 5,120 samples at 44.1 kHz is about 116 ms. The trade-offs between linear-phase and regular EQ are covered in linear phase vs minimum phase EQ.

How do FL Studio, Ableton Live, Logic Pro and REAPER compensate?

All four compensate automatically by default, but each exposes different switches. Knowing where they live saves a lot of guessing when something drifts.

The Logic setting trips people up most. If your only linear-phase EQ sits on a bus or the stereo out and compensation is set to audio and instrument tracks only, the aux path is not covered. Apple's guide says to choose All in that case^[1]. Logic also shows each plugin's latency in samples and seconds when you hover over its slot.

Why does PDC make recording feel laggy?

PDC delays playback so tracks stay aligned, but anything you monitor live has to wait for the slowest path too. A 116 ms linear-phase EQ on the master makes a live MIDI keyboard feel unplayable.

Each DAW has an escape hatch. Logic's Low Latency Monitoring mode bypasses plugins that push the record track above a limit of up to 30 ms and turns off its sends unless you mark one Low Latency Safe^[1]. Ableton's Reduced Latency When Monitoring option gives input-monitored tracks the lowest latency, at the risk of those tracks being out of sync with compensated return tracks^[6]. FL Studio can bypass a track's latency compensation only when recording or stopped^[5].

Buffer size adds its own latency on top of plugin latency. Latency and buffer size explained covers that side of the problem.

When does plugin delay compensation break?

PDC only works when the DAW knows the exact delay and the signal path lets it add matching delay elsewhere. These are the usual failure points.

• A plugin misreports its latency The DAW compensates the wrong amount. FL Studio has a per-plugin Wrapper, Settings, Latency offset for exactly this^[4].
• Hardware inserts Outboard gear adds converter delay the DAW cannot measure on its own. Ableton's External Audio Effect has a Hardware Latency slider for manual compensation, set in samples for digital connections and milliseconds for analog ones^[2].
• Feedback routing A loop has no stable end point to align. REAPER disables PDC when feedback routing is used^[7].
• Tempo-synced effects after a latent device Ableton warns that devices that take timing from Live's clock may sound out of sync when placed after devices that cause delay^[6]. Put LFO tools and gated effects before the linear-phase EQ.
• Sidechain keys Logic and FL Studio state that compensation covers sidechain routing^[1]. In any DAW, a key taken from a heavily processed track is worth checking by ear, because early or late triggers change how sidechain compression pumps.
• Automation lag Parameter moves can land late on delayed tracks. Logic compensates automation data^[1], and FL Studio has a Compensate automations option^[4].

The audible symptom of a broken parallel path is comb filtering: a thin, hollow, flangy tone when the dry and processed copies are summed. Phase cancellation explained shows why a few milliseconds of offset is enough to cause it.

How to check that PDC is working

A null test gives a yes or no answer in about a minute. If two identical signals cancel, the timing is perfect.

1. Duplicate a drum track
   Use something with sharp transients, such as a kick or snare loop, and route both copies to the same bus.
2. Add the suspect plugin to one copy
   Load the linear-phase EQ, lookahead limiter or hardware insert, set flat or neutral so it changes timing but not tone.
3. Flip polarity on the other copy
   Use a utility plugin's phase or polarity invert on the untouched duplicate.
4. Play and watch the meter
   Near silence means PDC is doing its job. Audible clicks or a thin drum sound means the copies are offset.
5. Nudge until it nulls
   If it does not cancel, adjust the manual offset or hardware latency field a few samples at a time until the level drops to its lowest point.

Workflow habits that avoid PDC problems

Most PDC trouble disappears if high-latency tools arrive late in the session. Arrange and record with low-latency plugins, then add the heavy ones when you mix and master.

• Track first, polish later Keep linear-phase EQs and big lookahead limiters off the master while recording. Add them at the end of the mix bus chain.
• Use the lowest resolution that works FabFilter recommends Zero Latency or Natural Phase modes for almost all mixing, and calls linear phase a problem-solving tool^[3].
• Check parallel chains after changes Swapping one plugin on a parallel drum bus can change its latency. Re-run the null test after big chain edits.
• Print hardware passes Record outboard processing to a new track once it sounds right, then line it up by eye against the original transient.
• Leave PDC on Ableton and REAPER both advise against disabling compensation in normal use^[7]. Solve monitoring lag with low-latency monitoring modes instead.