Plugin workflows
Plugin latency and delay compensation: why your session feels late
Separate interface buffer delay from plugin latency, then restore timing without breaking your mix routing.
Keep plugin delay compensation enabled for ordinary mixing. If playing through the DAW feels late, first distinguish the interface buffer from delay added by plugins. Lowering the buffer helps the first problem; it does not remove a limiter’s lookahead or an EQ’s processing delay. A session can play in time and still feel slow to perform through.
By Spectraforge Audio3 min read
Published
Guide review: Captum Records and AS Mastering. AI-assisted writing and source checks. How these guides are made.
Compensation aligns playback; it cannot make live input arrive early
Classify the symptom before touching the timeline. Late headphones during a take point toward monitoring. A hollow dry/processed blend points toward relative timing or phase. Notes that remain misplaced in a clean playback session may be a recording or performance problem. These need different fixes.
Trace the monitored path, including groups and the master
Save a diagnostic copy and note any manual track offsets. Temporarily remove unexplained offsets in that copy. Inspect the monitored track, every group it passes through, its returns and the master. Check reported device latency where the host exposes it; CPU load alone is not a latency measurement.
Remove one suspect processor at a time, beginning with lookahead, linear-phase or high-quality modes. Bypass may retain the plugin’s reported delay: Ableton explicitly documents that device deactivation keeps latency in effect. Removing the device in the copy is a clearer isolation check. Restore it before testing the next suspect.
Suggested check: the synth responds slowly only in this song
Play the same instrument in a blank project and then in the song. Use the same interface, buffer and instrument settings. If only the song feels late, remove its master lookahead limiter in the diagnostic copy and repeat. A restored response implicates that path; changing MIDI notes or buying a faster interface would not address the evidence you have just gathered.
If the blank project also feels late, investigate the interface’s reported input/output delay, driver and buffer. Avoid monitoring the same input through both the interface and the DAW unless you deliberately need the two paths. Their different arrival times can make a voice sound doubled or hollow.
Keep recording and mixing settings explicit
For recording, use a stable buffer and the minimum monitoring chain the performer needs. Print heavy backing parts when that frees resources. In Live 12, Reduced Latency When Monitoring can reduce additional compensation on monitored tracks, but those tracks may then disagree with compensated returns. Audition the actual cue mix before recording a full take.
For mixing, restore the intended devices and full compensation. Check a short render’s first attack, a busy passage and its ending. If the problem occurs only in an offline render, compare a real-time render and give support the exact host, plugin versions and routing. Keep a note of the device that caused the delay instead of leaving a mystery track offset behind.
Technical references
Listening exercises are proposed practice routines. Worked examples illustrate the stated setup; they are not reports of our listening tests. Editorial process and corrections.