Latency is the delay between what you play or sing and what you hear back. In a home studio, most of that delay comes from the buffer size, which is the chunk of audio your driver and DAW hold before processing it. You can usually cut the delay a lot by choosing a smaller buffer, a better driver, and direct monitoring while you record. The trade-off is CPU load, and a buffer that is too small causes clicks, pops, and dropouts.
What latency is and where it comes from
Your signal passes through several stages on its way from a microphone or instrument to your headphones:
- Analog-to-digital conversion in the interface, which adds a small fixed delay.
- The input buffer, which holds samples so the computer can work on them in chunks.
- The DAW and any plugins on the track, which can add their own processing delay.
- The output buffer, which holds samples before they are played back.
- Digital-to-analog conversion, which adds another small fixed delay.
The total delay from input to output is called round-trip latency. It is the number that matters for performing, because it determines when you hear yourself.
What buffer size means
A buffer is a block of audio samples that the driver collects before passing them to the next stage. A larger block gives the computer more time to finish its work, which makes playback more stable. It also means audio arrives later.
Buffer size is measured in samples, but you can convert it to milliseconds with this formula:
buffer latency (ms) = buffer size in samples ÷ sample rate × 1000
| Buffer size (samples) | At 44.1 kHz | At 48 kHz |
|---|---|---|
| 64 | 1.5 ms | 1.3 ms |
| 128 | 2.9 ms | 2.7 ms |
| 256 | 5.8 ms | 5.3 ms |
| 512 | 11.6 ms | 10.7 ms |
| 1024 | 23.2 ms | 21.3 ms |
Each figure covers one buffer in one direction. It does not include the converters, driver safety buffers, or plugins.
Why the buffer setting is not your full latency
Round-trip latency includes an input buffer, an output buffer, the converter delays, and any extra buffering the driver adds. A common rule of thumb is that round-trip latency is two to three times the single-buffer figure. At 512 samples and 48 kHz, one buffer is about 10.7 ms, so the round trip can easily land somewhere around 20 to 30 ms.
The buffer setting you see in your DAW is only part of the path. To find the real number for your system, see the loopback test further down this page.
Buffer size for recording and for mixing
Recording and mixing want different things:
- Recording needs a small buffer, so the performer hears themselves with little delay.
- Mixing does not need real-time response, so a larger buffer gives the CPU room to run heavy plugin chains without dropouts.
Switching between a tracking setting and a mixing setting is a normal part of a home studio workflow. Buffer size does not change the quality of what you record. It changes timing and stability.
For starting values, see what buffer size to use when recording. If you are wondering whether a larger buffer suits your session, is 512 buffer size good covers that trade-off in more detail.
How to reduce latency without causing dropouts
- Use the right driver. On Windows, use your interface’s native ASIO driver where one exists. The ASIO explainer and the WASAPI vs ASIO comparison cover the options. On a Mac, Core Audio is the built-in low-latency path.
- Monitor directly while tracking. Hardware monitoring sends your input to the headphones from inside the interface, so the signal does not wait for the computer. See direct monitoring vs software monitoring.
- Turn on your DAW’s low-latency mode. The names vary. Logic Pro has “Low Latency Mode”, Ableton Live has “Reduced Latency When Monitoring”, and Cubase has “Constrain Delay Compensation”. In FL Studio, turn off Triple buffer while recording, as explained in how to fix audio and MIDI latency in FL Studio.
- Bypass or freeze heavy plugins while recording. Lookahead limiters, linear-phase EQs, some amp sims, and convolution reverbs can add their own delay.
- Close background apps. Cloud sync tools, browsers, and other heavy programs compete for CPU and disk time.
- Keep the connection solid. Plug the interface directly into a USB port rather than a hub. On a laptop, prefer an interface with its own power supply, since bus power can strain the machine.
- Check the sample rate. A higher sample rate makes each buffer shorter in milliseconds, but it also increases CPU load. Whether 96 kHz recording is worth it weighs that trade-off.
Plugins can add delay of their own
Most DAWs compensate for plugin delay in the recorded timeline, so the recording still lines up. The performer, however, still hears the delay while tracking. Lookahead limiters, linear-phase EQs, and convolution reverbs are the usual culprits. Bypass them while tracking and turn them back on for mixing.
Find your buffer setting
Buffer size is set in the DAW’s audio preferences or in the interface’s driver control panel. The exact label depends on the driver and its version. On Windows with ASIO, the control panel is often opened from the DAW’s audio settings.
To find the lowest stable setting, start at 128 samples, record a short take with headphones on, and listen for clicks, pops, or dropouts. If the take is clean, try 64. If you hear artifacts, go back up one step. If crackles persist at every setting, the cause may not be the buffer at all, so work through fixing static, buzz and digital noise from an audio interface.
Measure your round-trip latency
DAWs offset recorded audio using the latency the driver reports, but that reported figure is not always accurate. A loopback test shows the real round trip:
- Connect one output of your interface to one of its inputs with a patch cable.
- Record a short click or impulse in your DAW.
- Measure how far the recorded click sits from the original.
Some DAWs include a built-in latency test, so check your DAW’s documentation first.
Common misconceptions
- Lower is always better. A setting that causes dropouts ruins takes. The goal is the lowest setting that stays stable.
- A faster CPU removes latency. The buffer and driver set most of the delay. A faster CPU mainly lets you run a smaller buffer without dropouts.
- Recorded audio ends up late on the timeline. With latency compensation, the recording lines up. Latency mainly affects what the performer hears.
- USB 3 automatically means lower latency than USB 2. Driver quality matters at least as much as the connection.
Linux users
On Linux, PipeWire is the audio server that manages the buffer. Its “quantum” sets the buffer size. For the commands and realtime settings, see Linux pro audio setup.