Before troubleshooting, confirm that delay is actually the issue. Some workflows tolerate latency fine; others need ultra-low latency. If you’re mixing a finished track with no live monitoring, a delay of 50–100ms won’t bother you. But if you’re recording a vocal performance or playing a virtual instrument, even 20ms can feel wrong.
The telltale sign: when you play something and monitor yourself in real-time, you hear a lag between your action and the sound coming back. Your voice feels delayed, or a key press on your MIDI keyboard takes a moment to trigger the synth sound.
If that’s what you’re experiencing, latency is your problem. If you’re just hearing a delay in playback of existing recordings, that’s usually a sync or track routing issue, not latency.
Is It Your Interface, Your Computer, or Your Monitoring Setup?
Latency can come from three places: your hardware (audio interface), your software (DAW and drivers), or your monitoring chain (headphones, speakers, wireless devices).
If you’re hearing delay through headphones plugged directly into your audio interface’s headphone output, the issue is likely in your interface’s hardware or driver, or in a plugin chain in your DAW.
If you’re hearing delay through your computer speakers or monitoring via USB headphones, the issue could be in your DAW’s monitoring setup, your USB drivers, or Windows audio settings.
If you’re using Bluetooth headphones, wireless headset, or a wireless speaker, the latency is likely inherent to the wireless device. Bluetooth alone can add 100–300ms of delay.
Measure your roundtrip latency with a latency measurement tool to get a number, then compare it to what you’re experiencing.
Buffer Size Is the First Suspect
Your DAW’s buffer size setting is the easiest latency culprit to spot and fix. Buffer size directly controls latency: smaller buffers = less delay, larger buffers = more delay.
At 48 kHz sample rate, a 512-sample buffer produces about 10.7ms of latency. A 256-sample buffer produces about 5.3ms. A 128-sample buffer produces about 2.7ms.
Open your DAW’s audio settings and look for buffer size. If it’s set to 1024 samples or higher, lower it to 256 or 128 and test. Do you hear a reduction in delay?
If you lower the buffer size and hear clicks, pops, or audio dropouts, your computer can’t handle that small a buffer. Raise it back up to the largest size where you get clean audio without glitches. That’s your current limit.
Outdated or Missing Drivers
A missing or outdated audio interface driver is a common source of unexpectedly high latency. Your interface came with a driver (usually an ASIO driver on Windows). If you’ve never installed it, or if your installed driver is several years old, latency can be far worse than the interface’s spec.
Visit your audio interface’s manufacturer website (Focusrite, PreSonus, MOTU, RME, etc.) and download the latest driver package. Install it, restart your computer, and select that driver in your DAW’s audio settings. Test latency again.
If you’re using a budget interface or built-in computer audio and can’t find a suitable driver, install a universal ASIO driver as a workaround. Follow the setup guide for ASIO4ALL if you’re on Windows.
Bluetooth or Wireless Audio
If you’re monitoring through Bluetooth headphones, a wireless headset, or a Wi-Fi speaker, latency is baked into the technology. Standard Bluetooth adds 100–300ms. aptX Low Latency reduces it to 40–130ms but still isn’t suitable for live monitoring of your own voice or instrument.
The fix: switch to wired headphones for monitoring while you’re recording. Use wireless audio only for playback and non-real-time listening. If you need wireless monitoring on stage or in a live setting, use a 2.4 GHz wireless monitoring system designed for low-latency performance (these can achieve 5–20ms), not consumer Bluetooth.
You’re Monitoring Through Your DAW Instead of the Interface
Many beginners don’t realize they can monitor audio directly through the interface’s analog outputs instead of routing it through the DAW. If your DAW’s monitoring is on, audio gets sent to your DAW, processed, and sent back out—adding a full extra buffer cycle of latency.
Turn off DAW monitoring and instead enable direct monitoring on your audio interface. Most interfaces have a direct monitor control (often a knob on the front panel or a setting in the interface’s control software). This routes audio from input to output in hardware, bypassing the DAW entirely and eliminating that extra latency.
Background Processes and System Load
Heavy background processes—antivirus scanning, Windows Update, browser tabs, Discord, Spotify—consume CPU power and force your DAW to use larger buffer sizes or experience dropouts.
Close all unnecessary applications before recording. Disable real-time antivirus scanning. Pause automatic Windows Updates. If you notice latency gets worse as your system runs, CPU overload is likely the culprit. Either shut down other apps or upgrade your computer’s RAM and storage.
Plugin Latency Adding Up
Some plugins introduce latency of their own. A linear-phase EQ might add 10ms. A convolver reverb might add 50ms. If you’re using heavy effects on your monitoring track, that latency stacks on top of your interface and buffer latency.
For live tracking with effects, disable high-latency plugins during recording. Use minimal or zero-latency plugins for monitoring. Save the convolver reverbs and linear-phase EQs for mixing after you’ve recorded.
Test your DAW’s plugin latency with a latency measurement to see if effects are the culprit.
Quick Diagnostic Test: Record a Click and Measure
The most reliable way to diagnose latency is to measure it yourself.
Record a click or tone with your interface while monitoring that signal in real-time. Use your DAW’s recording function to capture both the original click and what you hear coming back. Then look at the audio in your DAW’s waveform view and measure the delay between the two.
If the input is visibly delayed from the output, you’ve got a latency problem. If they line up almost perfectly, your latency is below the threshold of perception for that workflow.
This test tells you the true roundtrip latency of your entire system, not just the interface spec. Use an automated latency calculator tool if you want a more precise measurement, or do the visual test in your DAW for a quick diagnosis.
Frequently Asked Questions
I lowered my buffer size and now I hear glitches. What do I do?
Raise the buffer size back up until the glitches stop. That’s your computer’s limit with your current setup. You may need to upgrade RAM, close background apps, or get a faster computer to go lower.
Does latency get worse over time, or is it always the same?
It should be consistent, but DPC latency spikes can cause inconsistent delays on Windows. If latency used to be fine and suddenly got worse, a driver update or background process is likely the culprit. Restart your computer and check for updates.
My interface promises 3ms latency but it feels like 30ms. Why?
The manufacturer’s spec might be measuring input-to-output latency only, not including your DAW’s buffer and plugin processing. Or they’re measuring at a different buffer size or sample rate than you’re using. Always test real-world latency in your actual DAW.
Can I use a USB hub to connect my interface and reduce latency?
No, a USB hub usually increases latency slightly by adding switching overhead. Connect directly to a USB port on your computer for the lowest latency.
Is my latency worse on battery power than plugged in?
Yes, significantly. Windows power-saving features can double or triple latency. Always plug in your laptop during recording and set your power plan to High Performance.
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.