Delay Compensation Calculator | PDC Track Align

Delay Compensation Calculator

Work out the per-track plugin delay compensation (PDC) offsets needed to align every track to the highest-latency track – convert samples to ms, find the master timeline shift and round-trip monitoring delay

🔌 Quick Presets
🎛 Delay Compensation Inputs
Master (Max) Latency
all tracks align here
Largest Compensation
samples added
This-Track Comp
selected track
Round-Trip Monitor Delay
live monitoring

Full Compensation Breakdown

Number of tracks
Alignment reference (max latency)
Master latency in ms
Compensation rule
Largest compensation (samples / ms)
Total compensation across tracks
Selected track compensation
Master latency in beats (at BPM)
Round-trip monitor delay
Mode note
📊 Per-Track Compensation (Current Inputs)
Track #Latency (samples)Compensation Added (samples)Compensation (ms)
🎚 Delay Compensation Spec Grid
31.3 ms
1500 smp @48k
max-track
Comp Formula
smp/SR
ms = x1000
max smp
Timeline Shift
💿 Samples to Milliseconds by Sample Rate
Samplesms @ 44.1kms @ 48kms @ 96k
641.45 ms1.33 ms0.67 ms
1282.90 ms2.67 ms1.33 ms
2565.80 ms5.33 ms2.67 ms
51211.61 ms10.67 ms5.33 ms
102423.22 ms21.33 ms10.67 ms
150034.01 ms31.25 ms15.63 ms
204846.44 ms42.67 ms21.33 ms
409692.88 ms85.33 ms42.67 ms
🔌 Typical Plugin Latencies
Plugin TypeTypical LatencySamples @48kms @48k
Dry / zero latencyNone00.0 ms
Minimum-phase EQVery low0–640–1.3 ms
Compressor lookaheadLow~256~5.3 ms
Linear-phase EQHigh1024–409621–85 ms
Multiband / mastering limiterHigh1500–204831–43 ms
Upsampling / oversampledVariable512–300011–63 ms
📐 Compensation Example (Max minus Track)
Track LatencyMax LatencyCompensation AddedComp ms @48k
0 smp1500 smp1500 smp31.25 ms
256 smp1500 smp1244 smp25.92 ms
512 smp1500 smp988 smp20.58 ms
1024 smp1500 smp476 smp9.92 ms
1500 smp1500 smp0 smp0.0 ms
💡 Pro Tips
PDC delays the faster tracks to match the slowest: Plugin Delay Compensation looks at every track's reported plugin latency, finds the maximum, then delays each lower-latency track by max minus its own latency so they all line up at playback. A 0-sample dry track gets the full delay added; the highest-latency track gets none.
The whole timeline shifts by the maximum latency: Because every track is pulled back to align with the slowest one, the entire project plays back delayed by the master (max) latency. That delay is harmless on playback, but it is exactly the round-trip you hear when monitoring through latency-inducing plugins live, so freeze or bypass heavy plugins while tracking.

That’s because you’ve recorded yourself hitting a snare drum and it sounds just right, until you play back the mix and the snare seem to be just a little bit off the beat. It is a little too loose against the kick. But that’s not you. That’s your plugins. The new software instruments, coupled with moddern audio interfaces, have a small amount of latency (delay) between you playing a note and hearing it. When tracking in real time, it’s a nightmare. On playback, it can go unnoticed if your DAW properly compensates for plugin delays.

Knowing how the DAW aligns those helps keep your drum tight and avoid phasing issues. It works in theory. But doing it yourself by hand can be a little tough. Here’s the deal: When your DAW loads all the plugins on a track, it notes their reported latency. It then looks through all the tracks in the session and finds the maximum number. It use this maximum as the new anchor for the timeline. Then it moves all the other tracks forward or backward based off the difference between their own latency and the maximum.

How Plugins Change Your Drum Timing

So if I have one vocal chain loaded up with a serious linear-phase EQ that adds 1500 samples of delay, all the rest will be nudged back to match it. And it’ll do this even though they may not need any delay. To make sure you know how far to push things around, the calculator up top will convert the sample amounts into milliseconds, which give you a clear picture of amount of movement required.

Because if you don’t get things aligned, it creates what’s called comb filtering, a hollow phasing sound that muddles the mix. There’s a hidden variable: Sample Rate. Each sample is just a single point in time, and you can change how long they are based off your project settings. In a typical session, a sample take about point zero two milliseconds at 48 kilohertz. At 96 kilohertz, that duration halves. That means a thousand sample latencies sounds twice as long in high-res sessions.

When troubleshooting timing problems, many engineers forget about this conversion factor. “Oh, that’s not that many samples,” they think. “I’ll ignore it.” Later, they realize the cumulative delay across multiple tracks has knocked the rhythm section out-of-phase with the guide track. The chart on the page explain this plainly. Six-four samples translate into one point three milliseconds at standard studio rates, or zero point seven at higher resolution.

Typically, these days, it’s all about linear-phase equalizers. By design, those devices takes audio and process it evenly around every single frequency point. That means looking ahead into the data stream to keep the phase in sync. It adds a lot of latency. Dry tracks and minimal-phase plugins don’t add any. Lookahead compressors add some but less so.

So now you’ve got your snare track as dry but then you’ve EQ’d your kick and added a full two tenths of a second to its timing. Not good because your snare isn’t hitting the same time anymore. So what does the DAW do? It delays the snare for you. What happens if your monitor buffer can accommodate this increased load? You’ll hear sweet FA wrong. What if it can’t? Guess what you begin to hear? You will hear echoes while you’re tracking.

The usual solution to this problem is freezing tracks during your intensive mix session. Bouncing the plugin chain to an audio file removes the latency completely. No more compensation from the DAW. It require less CPU power. Round trip monitoring delay is reduced. This is very helpful if you are using oversampled saturation plugins or multiband limiters that can easily add hundreds of milliseconds of latency. Yes, you’re stuck without the ability to tweak real time. But you also have stability. It is a choice between performance and flexibility.

Manual nudges are sometimes the better option different than automatic compensation. Sometimes you may have one track with a buggy plugin causing a wrong latency report. Rather than have the whole session shift automatically, you’d like to force it back into line manually. In this case, you could avoid the auto system altogether and surgically correct just that one region by nudging it forward/backward in samples. This allows for total control on your timing while leaving the other tracks intact. You will need to listen carefully, often using transients as reference points to ensure things are lining up properly.

So in summary, delay compensation in plugins is one of those invisible tools that make your mix stick together. You seldom know it’s there unless it isn’t working or you misinterpret the sample-to-millisecond conversion and your timing gets off. Being able to know how many milliseconds each plugin adds to your signal path helps plan your signal chain better. Try to put heavy phase linear processing on buses as opposed to individual instrument tracks where possible. Make sure your buffer size is set before tracking. A thousand samples is not just a number, but a chunk of time that throws off a groove. Tighten the chain and the timing falls into place.

Delay Compensation Calculator | PDC Track Align

Leave a Comment