For most recording with software monitoring, start at 128 samples. Drop to 64 if your computer runs it cleanly. Lower the buffer until you hear clicks, pops, or dropouts, then go up one step. For mixing, use a larger buffer, usually 512 to 2048 samples.
Starting points by task
| Task | Starting buffer | Notes |
|---|---|---|
| Vocals or guitar through software monitoring | 128 | Try 64 if the computer handles it. |
| MIDI keyboards and virtual instruments | 64 or lower | Needs a fast computer; step up if you hear glitches. |
| Large sessions with many tracks | 256 | A safe compromise when CPU load builds up. |
| Tracking with direct monitoring | Whatever runs cleanly | The buffer matters much less, because you hear the dry input from the interface. |
| Mixing and mastering | 512 to 2048 | Gives plugins room, and you are not performing live. |
For why 512 suits mixing but not live tracking, see is 512 buffer size good.
Round-trip math
At 128 samples, one buffer adds about 2.9 ms at 44.1 kHz or 2.7 ms at 48 kHz, in one direction. At 64 samples, the figures are 1.5 ms and 1.3 ms. At 256 samples, one buffer adds 5.8 ms or 5.3 ms.
Many players are comfortable with a round trip under about 10 ms, but the threshold varies by person and instrument. The audio latency and buffer size guide explains how one buffer becomes the full round trip.
Why the right setting depends on the performer
- Vocalists are often the most sensitive. They hear their own voice through their head as well as through the headphones, so delay is easy to notice.
- Drummers need a quick response. Drum attacks are sharp, so even small delays can throw off timing. Direct monitoring helps here. See direct monitoring vs software monitoring.
- Guitarists using amp sims and keyboard players hear only the processed sound, so they need a low buffer. Without a dry signal to fall back on, delay is hard to ignore. Keyboard players can also check the controller side with how to reduce MIDI latency.
Find the lowest stable setting
- Set the buffer to 128 samples in your DAW or the driver control panel.
- Bypass or freeze heavy plugins on the tracks you are recording.
- Record a short take at full performance level, with headphones on.
- Listen for clicks, pops, or dropouts, and watch your DAW’s CPU meter.
- If the take is clean, try 64. If you hear artifacts, go back to 128.
Prepare the session before tracking
- Bypass or freeze heavy plugins, and turn off lookahead and linear-phase processors on the tracks you record.
- Turn on your DAW’s low-latency mode. Logic Pro calls it Low Latency Mode, Ableton Live calls it Reduced Latency When Monitoring, and Cubase has Constrain Delay Compensation. Cubase’s ASIO-Guard is a separate setting that doesn’t change the latency of monitored tracks; see how to disable ASIO-Guard.
- Use direct monitoring when you don’t need effects in your headphones.
- Close background apps that use CPU or disk.
Settings that don’t change the recording
Buffer size does not change the quality of what you record. For most home recording, 44.1 or 48 kHz at 24-bit is a sensible choice. A higher sample rate shortens each buffer in milliseconds, but it also increases CPU load and may force a larger buffer anyway.
Common mistakes
- Using the mixing buffer while tracking. Leaving a large buffer on during recording is a common cause of lag.
- Looking for one correct buffer. The right setting depends on your CPU, driver, and plugin load.
- Choosing the lowest possible setting. Dropouts ruin takes, so pick the lowest setting that stays stable.