To reduce latency in your DAW, lower your audio buffer size while tracking, use the correct low-latency driver for your interface (ASIO on Windows, Core Audio on Mac), and lean on direct or hardware monitoring so you hear yourself without the round-trip delay. Those three moves fix most of the “why does my playing feel late?” problem in minutes. Everything else below is fine-tuning.
Violet Recording is reader-supported — we may earn a commission from links on this page, at no extra cost to you.
Latency is the short delay between a sound going into your interface and coming back out of your headphones. A little is normal. Too much makes a vocal feel a beat behind or a guitar strum arrive after your hand moves — impossible to perform to. The good news: you rarely need new gear. You just need to know which settings actually matter and when to change them. This guide walks through how to reduce latency in your DAW step by step, in the order a working producer would check things.
Set the right audio buffer size before you track
The buffer size is the single biggest lever you have. It’s measured in samples — common values are 32, 64, 128, 256, 512 and 1024. A smaller buffer means less delay but asks more of your CPU (you may hear clicks, pops or dropouts). A larger buffer is easy on the CPU but adds delay.
You’ll find this setting in your audio preferences:
- Ableton Live: Preferences → Audio → Buffer Size.
- Logic Pro: Settings → Audio → Devices → I/O Buffer Size.
- FL Studio: Options → Audio Settings → Buffer length (the ASIO panel also has its own buffer control).
- GarageBand: it manages this automatically, but you can nudge it under Settings → Audio/MIDI.
The trick is to use two different buffer sizes for two different jobs. When you’re recording, set the buffer low — 64 or 128 samples — so what you play feels tight and immediate. When you switch to mixing, raise it to 512 or 1024 so your computer can run all your plugins without choking. There’s no delay penalty when you mix, because nothing is being recorded live, so a big buffer is free performance. Getting into this habit of dropping the buffer to track and raising it to mix solves more latency complaints than any other tip here.
Use the correct low-latency audio driver
The driver is the software bridge between your DAW and your interface, and the wrong one adds delay you can’t tune away.
On Windows, always use an ASIO driver. If your interface came with its own ASIO driver (Focusrite, PreSonus, Universal Audio and most others do), install it and select it in your DAW’s audio settings — it will almost always outperform the generic Windows audio path. If your device didn’t ship a dedicated driver, ASIO4ALL is a free, widely used fallback that wraps your hardware in an ASIO layer. Avoid MME, DirectSound or WASAPI (shared mode) for live recording; they carry noticeably more latency.
On Mac, Core Audio is built in and already low-latency, so there’s no separate driver to install. Just make sure your interface is selected as the input and output device rather than the Mac’s built-in mic and speakers, which are slower and lower quality.
If you’re still learning how the interface, driver and DAW fit together, our guide to setting up an audio interface covers the whole signal chain, and what audio latency is explains the round-trip in more depth.
Reduce latency in your DAW with direct or hardware monitoring
Here’s the move that beats every software setting: don’t listen to yourself through the computer at all while recording. Most audio interfaces have a direct (or “zero-latency”) monitoring feature that splits your input signal and sends it straight to your headphones in hardware, bypassing the DAW round-trip entirely. You hear your voice or guitar with effectively no delay, while the interface still sends a clean copy into the DAW to be recorded.
Look for a “Direct Monitor” button on the interface, or a mix/blend knob that balances between the live input and the computer playback. Many modern interfaces also include a small mixer app (Focusrite Control, UA Console, and similar) where you set up this monitoring path. When you use direct monitoring, remember to turn OFF software monitoring for that track in your DAW, or you’ll hear yourself twice — once instantly and once delayed, which is worse than either alone.
The one catch: direct monitoring gives you the dry signal only. If you want to sing with reverb in your headphones, you either add a touch of hardware/console reverb or accept a low DAW buffer and monitor through the software. For most tracking, dry-and-tight beats wet-and-late.
Freeze, bounce or disable heavy plugins
Plugins are the usual reason you can’t run a low buffer. Convolution reverbs, amp sims, heavy synths and lookahead limiters all add processing load, and some add their own latency on top. When your project gets big and playback starts stuttering, you don’t have to raise the buffer and live with delay — you can lighten the load instead.
- Freeze tracks you’re not actively editing. Freezing temporarily renders a track (with its plugins) to audio so the CPU stops calculating it in real time. Ableton has Freeze Track; Logic has Freeze on the track header; FL Studio can render patterns to audio. Unfreeze when you need to tweak.
- Bounce in place a finished MIDI part to audio so its synth stops running live.
- Disable rather than just bypass plugins you’re not using — a bypassed plugin often still loads its latency and CPU. Removing or disabling it fully frees the resource.
Watch out for lookahead effects on your monitored recording chain. A mastering limiter or lookahead compressor on the master bus introduces delay that your DAW tries to compensate for globally, and that compensation can make live input feel late. While tracking, take those off the master and add them back at mixdown.
Tune sample rate and other settings sensibly
A higher sample rate (say 96 kHz vs 44.1 kHz) technically lowers latency at the same buffer size, because samples pass through faster. But it also roughly doubles the CPU and disk load, which can force you back to a bigger buffer — so it’s usually a wash and not worth chasing for latency alone. Record at 44.1 or 48 kHz unless you have a specific reason not to. If you want the trade-offs, see sample rate and bit depth explained.
A few smaller wins that add up:
- Close other apps — browsers, chat clients and cloud sync tools all steal CPU and can cause dropouts that push you toward a higher buffer.
- On a laptop, plug in and set the power plan to high performance; power-saving modes throttle the CPU and hurt real-time audio.
- Check your DAW’s reported latency readout (many show input/output latency in milliseconds in the audio settings) so you can see the effect of each change instead of guessing.
- Keep drivers and your interface firmware up to date; manufacturers do ship latency and stability improvements.
As a rough feel guide, round-trip latency under about 10 milliseconds is comfortable for most players, and under 5 ms is excellent. Above ~20 ms you’ll start to notice it on percussive parts.
Common latency problems and quick fixes
A few patterns come up again and again:
- “I hear myself twice.” You’ve got both direct monitoring and DAW software monitoring on. Turn off input monitoring on the recording track.
- “Recorded audio lands slightly early or late in the timeline.” This is delay compensation, not live latency. Make sure your DAW’s automatic plugin delay compensation is enabled, and if your interface driver reports its latency incorrectly you can nudge a recording offset in preferences.
- “MIDI feels laggy from my keyboard.” MIDI latency follows the same buffer rule — drop the buffer while you play parts in, and freeze heavy soft-synths you’re not recording.
- “Clicks and pops at a low buffer.” Your CPU is maxing out. Freeze tracks, disable unused plugins, or raise the buffer a notch until it’s clean.
If you want a metronome that’s rock-solid while you set your buffer and test your feel, our free browser audio tools include a click you can run alongside your session.
Once your monitoring feels tight, the rest of the recording chain matters just as much — gain staging keeps your levels clean, and if vocals are your focus, recording vocals at home and mixing vocals pick up where tracking leaves off. For more on dialing in the room and the rig, browse the Home Studio Setup hub. Newer to the whole workflow? Start with the best free DAWs for beginners.
Frequently asked questions
What is a good buffer size for recording versus mixing?
Use a low buffer — 64 or 128 samples — while you record so the delay is tiny and performing feels natural. Raise it to 512 or 1024 samples when you switch to mixing, because a bigger buffer lets your computer run more plugins with no downside once you’re no longer tracking live.
Does a faster computer or more RAM reduce latency?
Not directly. Latency is set by your buffer size, driver and sample rate, not raw horsepower. A faster CPU helps indirectly by letting you run a lower buffer without clicks and pops, so you can hold that tight setting on bigger projects — but the buffer itself is still the control you adjust.
Why does my audio still feel delayed after lowering the buffer?
Usually a lookahead plugin (a limiter or lookahead compressor) on your master or recording chain is adding delay the DAW compensates for globally. Remove those while tracking. If you monitor through software, switch to your interface’s direct/hardware monitoring instead to skip the round-trip entirely.
