Ableton Live handles latency better than most DAWs thanks to its Delay Compensation feature, which automatically syncs all tracks regardless of plugin latency. But that same feature adds a cost: when you enable it, everything is delayed by however much the most latency-heavy track needs. You can feel that delay when recording.
The trick is balancing two things: keeping Delay Compensation on for accurate playback, while using settings that minimize the actual latency you feel when monitoring during recording.
Understanding Ableton’s Latency Settings
Ableton’s latency comes from four places:
Hardware Latency (A/D and D/A conversion): Unavoidable. Typically 1–3ms from your audio interface.
Buffer Size: The main lever you control. Smaller buffers = less latency but more CPU demand.
Plugin Latency: Devices and plugins can add delay. Ableton compensates, but that compensation itself adds latency to everything.
Delay Compensation: When enabled, Ableton delays all tracks to the latency of the most delayed track so everything stays in sync. Good for accuracy, bad for monitoring feel.
Reducing Buffer Size (Biggest Impact)
Buffer size is the primary control. It’s measured in samples. The formula is: Latency (ms) = (Buffer Size / Sample Rate) × 1000.
At 128 samples and 48kHz: (128 / 48000) × 1000 = 2.67ms just from the buffer alone.
Step 1: Access Audio Preferences
Go to Preferences > Audio. Under “I/O Buffer Size,” you’ll see the current setting (often 512 or 1024 samples).
Step 2: Lower the Buffer
Start at 256 samples if recording MIDI or playing software instruments. If you’re recording audio and monitoring hardware (guitar, mic directly into the interface), try 128 samples.
256 samples at 48kHz = 5.3ms buffer latency 128 samples at 48kHz = 2.67ms buffer latency
Step 3: Test for Glitches
Lower buffer = higher CPU load. Play your set. If you hear pops, clicks, or “system overload” alerts appear, your computer can’t keep up. Increase to the next higher setting (512) and test again.
Step 4: Find Your Floor
Most modern computers with decent CPUs can handle 128 without issues in a modest project (10–15 tracks, reasonable plugins). If you have a dense session with lots of VSTs, you might need 256 or 512 during initial recording and can lower it once you freeze tracks.
Using Reduced Latency When Monitoring (Key Setting)
This is Ableton’s secret weapon. When enabled, it bypasses Delay Compensation for the track you’re recording on, giving you real-time feedback without the full delay that would hit the rest of your set.
How to Enable:
Go to Options > “Reduce Latency when Monitoring.”
What It Does:
Normally, if your set has 100ms of total delay (because you have plugins with latency), everything gets delayed to keep everything in sync. But Reduced Latency bypasses that for your current recording track. You hear yourself with minimal delay, while the rest of the playback stays locked.
The Trade-Off:
Your recording is placed in time correctly by Ableton automatically (it offsets it to account for the overall latency). But while you’re recording, the rest of your set is delayed relative to you. This can feel odd if you’re listening to drums or a click on other tracks—the click might feel slightly behind your performance.
Most musicians adjust to this. If it bothers you, you can:
- Record with monitoring OFF and use direct hardware monitoring from your interface.
- Record with a separate audio track set to monitor mode OFF so Ableton compensates correctly.
Turning Off Delay Compensation (For Live Performance)
Delay Compensation is on by default and essential for accurate mixing. But for live performance or when you absolutely need zero latency, you can disable it temporarily.
How:
Options > “Delay Compensation” (toggle off)
What Happens:
All delay from plugins vanishes. Your overall latency drops to just buffer + hardware (maybe 3–10ms total). But now tracks with different plugin loads will be out of time with each other. Use this only for live performance where timing matters more than precision.
Once you’re done performing, turn Delay Compensation back on.
Freezing CPU-Heavy Tracks
If your session has lots of reverb, convolution, or heavy processing, those plugins introduce latency that affects your entire session. Freeze them to remove their latency from live processing.
How to Freeze:
Right-click a track with CPU-heavy plugins > “Freeze Track.” Ableton renders the track to audio, removing the plugin from real-time processing.
Before Freezing:
Make sure Delay Compensation is ON. When you freeze, the track is rendered with all its latency baked in, and then the compensation is removed. The timing stays correct.
When to Freeze:
During recording and initial arrangement. Unfreeze during final mixing if you need to adjust those plugins.
Checking Plugin Latency
Some plugins add lots of latency. Hover your mouse over a device’s title bar—the bottom of the screen shows how much latency that device introduces.
Lookahead plugins (compressors, limiters with “lookahead” enabled) intentionally add latency to preview the signal. Mastering plugins like iZotope Ozone can add 50–100ms.
These aren’t problems for mixing, but they increase the overall session latency when Delay Compensation is on. If your overall latency is high and you’re not sure why:
- Hover over devices to see their individual latencies.
- Disable the most latency-heavy plugins while recording.
- Re-enable them for mixing.
Using Driver Error Compensation (DEC)
Sometimes your audio interface reports its latency incorrectly to Ableton. Recordings end up slightly out of sync even though compensation is on.
How to Adjust:
Preferences > Audio > “Driver Error Compensation.” Most interfaces need 0 (default), but some need ±1 to ±20ms.
How to Find the Right Value:
Ableton has a built-in lesson for this. Go to Help > Help View > Audio I/O. Find the lesson on Driver Error Compensation—it walks you through testing and calibrating.
Typical value: 0 to 10ms, rarely higher. If you set it above 20ms, you might have other issues (bad USB cable, outdated drivers, wrong interface).
Sample Rate (Minor Impact)
Sample rate affects latency per-buffer, but changing it shouldn’t be your first move. Higher sample rates mean less latency per sample, but you’re processing more data.
44.1kHz vs 48kHz: Negligible difference (less than 1ms).
96kHz vs 48kHz: Latency per buffer cuts in half, but CPU load doubles. Only helps if you’re already at that sample rate for other reasons.
Set your sample rate based on your project needs (recording vocals? 48kHz is standard). Don’t change it just to chase latency.
Real Ableton Latency Numbers
With good settings:
- Buffer 64 samples, 48kHz, ASIO driver, single instrument: 3–5ms overall latency
- Buffer 128 samples, 48kHz, ASIO driver, 5–10 tracks: 5–10ms
- Buffer 256 samples, 48kHz, moderate plugins, Delay Compensation on: 10–15ms
Any of these is usable for recording. Anything under 20ms feels responsive for most musicians.
Windows vs. Mac (Driver Matters)
Windows:
Use ASIO drivers if your interface has them. ASIO bypasses the Windows mixer and talks directly to your interface. Latency is typically lower and more consistent. If no ASIO available, try WASAPI Exclusive mode. Avoid DirectSound or MME—they add significant latency.
Mac:
Core Audio (Ableton’s default) is built into macOS and optimized for low latency. No driver installation needed. Latency is typically 5–15ms at 128 samples. No advantage to chasing alternative drivers.
Quick Latency Optimization Checklist
- [ ] Set buffer to 128 or 256 samples (lowest your CPU can handle)
- [ ] Confirm you’re using ASIO (Windows) or native Core Audio (Mac)
- [ ] Enable “Reduce Latency when Monitoring”
- [ ] Close unnecessary background apps
- [ ] Disable plugins on tracks you’re not actively using
- [ ] Freeze tracks with heavy plugins (reverb, convolution, mastering)
- [ ] Set sample rate to your project standard (48kHz or 44.1kHz)
- [ ] Test with a loopback to confirm actual latency if recordings feel off
When Latency Still Feels Bad
If you’ve optimized buffer and driver but latency still bothers you:
- Use direct hardware monitoring from your audio interface instead of monitoring through Ableton.
- Record with Monitor OFF and use your interface’s direct output.
- Confirm your interface’s reported latency is accurate (test with <a href=”https://soundlatencytest.com/audio-latency-test/”>an audio latency test</a>).
Direct hardware monitoring bypasses Ableton entirely and gives you zero latency feedback—you’re hearing your mic or guitar through the interface’s mix knob, not through software.
Dalton is an audio testing and latency optimization writer at SoundLatencyTest. He focuses on audio latency analysis, sound delay testing, recording performance, and audio troubleshooting tools for producers, gamers, streamers, musicians, and audio engineers.