How to Fix MIDI Latency on Mac

Last updated: March 2026

MIDI latency is the delay between pressing a key on your MIDI controller and hearing the resulting note from your software instrument. While MIDI itself is a low-overhead serial protocol, latency can accumulate from hardware connections, drivers, and — most significantly — your DAW's audio buffer settings. This guide explains every source of MIDI latency on macOS, how to measure it, and how to reduce it to a playable level.

What causes MIDI latency on Mac?

MIDI latency is not a single value — it is the cumulative total of several components stacked together:

• Hardware-to-Mac MIDI latency: the time from pressing a key to the MIDI message arriving at macOS. Typically 1–3ms over USB, 5–15ms over Bluetooth.
• CoreMIDI processing: macOS's MIDI layer adds less than 1ms in normal conditions. This is not a significant factor.
• DAW MIDI processing: some DAWs add a small fixed delay to synchronize MIDI with audio tracks. Usually 1–3ms.
• Audio buffer latency (dominant source): the most impactful factor. Your DAW processes audio in chunks called buffers. At 44,100 Hz sample rate: 64 samples = 1.5ms, 128 samples = 2.9ms, 256 samples = 5.8ms, 512 samples = 11.6ms, 1024 samples = 23.2ms.
• Audio output latency: the audio hardware's output buffer adds another 5–15ms depending on the interface and driver.

Total typical latency ranges from 10–30ms. Below 10ms is imperceptible for most players. Above 20ms becomes noticeable and affects rhythmic accuracy for live playing.

USB vs Bluetooth vs DIN MIDI latency

USB MIDI is the gold standard for low latency. The MIDI message travels from the keyboard, through the USB cable, into CoreMIDI, and is available to your DAW in typically 1–3ms. USB is reliable, consistent, and immune to wireless interference.

Bluetooth MIDI (BLE MIDI) adds 5–15ms of additional latency. Bluetooth also introduces occasional jitter — small variations in timing — which can make rhythmically precise playing feel slightly loose. For sustained chords, ambient playing, or non-time-critical use, Bluetooth is acceptable. For tight rhythmic playing, choose USB.

DIN MIDI (5-pin) is a serial protocol at 31,250 bps. A 3-byte Note On message takes approximately 1ms to transmit. With a modern USB MIDI interface, total DIN-to-Mac latency is typically 2–4ms — similar to direct USB. Older interfaces with large internal buffers can add more.

Measuring MIDI latency with Midilize

Midilize's Monitor Mode shows a precise timestamp on every MIDI message. You can use this to measure how consistently your device is transmitting:

1. Enable your device in Midilize's Sources panel
2. Switch to Monitor Mode (Cmd+1)
3. Play a series of notes at a steady tempo
4. Compare the timestamps between consecutive Note On messages

Consistent timestamps indicate a stable connection with low jitter. Variable timestamps that deviate significantly from the expected interval suggest jitter — more common over Bluetooth or through a low-quality USB hub.

Midilize does not measure round-trip latency (from key press to sound output) directly, as that depends on your DAW and audio hardware. But it isolates the MIDI input side, confirming whether your controller is the source of any timing problems.

Reducing audio buffer latency in your DAW

Audio buffer size is the primary lever for reducing perceived MIDI latency. Here is how to adjust it in common DAWs:

Ableton Live: Go to Preferences > Audio and find the Buffer Size dropdown. Reduce it to 128 or 64 samples. The "In" and "Out" latency values update in real time showing the total round-trip latency. A typical low-latency setup shows 6–12ms total.

Logic Pro: Go to Logic Pro > Preferences > Audio > Devices and reduce the I/O Buffer Size. Logic shows the resulting latency value next to the setting. Smaller buffers increase CPU load — monitor the CPU meter in the top bar and stop if you see overload warnings.

GarageBand: GarageBand manages its buffer automatically. Using a dedicated audio interface (rather than built-in Mac audio) gives GarageBand lower-latency options to work with.

Trade-off: Smaller buffers require your CPU to finish processing more often. At 64 samples, your CPU has only 1.5ms to complete all audio processing before the next buffer is needed. On a loaded session with many plugins, this can cause audio dropouts (crackling, pops). Use 64–128 samples when recording or playing live, and increase to 256–512 when mixing with many plugins.

Using a dedicated audio interface

Built-in Mac audio (the headphone jack or USB-C audio) uses Apple's generic audio driver, which is designed for broad compatibility rather than minimum latency. A dedicated USB audio interface provides:

• Optimized low-latency drivers with stable performance
• Hardware direct monitoring: hear your input with zero latency through the interface while the DAW processes in the background
• More stable clock, reducing audio jitter
• Combined MIDI and audio in one device (many interfaces include MIDI ports)

Interfaces such as the Focusrite Scarlett series, Native Instruments Komplete Audio, or Universal Audio Volt provide reliable low-latency performance on macOS with minimal driver issues.

Best practices for low MIDI latency on Mac

• Use USB MIDI for live performance — not Bluetooth
• Connect directly to a Mac USB port or a powered hub rather than a bus-powered adapter
• Set DAW buffer to 64–128 samples when playing or recording; increase when mixing
• Close background applications that consume CPU while playing live
• On a MacBook, plug into power — battery power can trigger thermal throttling that increases audio processing latency
• Freeze or disable CPU-heavy tracks while recording new parts

Troubleshooting high latency

Latency is unusually high despite small buffer: Check that your audio interface driver is up to date. Some older drivers enforce a minimum buffer size. Check Activity Monitor — another process may be consuming CPU and starving your DAW.

Latency varies unpredictably: This is jitter. Most commonly caused by Bluetooth MIDI or a failing USB connection. Switch to a direct USB connection and test again. Jitter can also be caused by USB hubs that throttle power under load.

Keyboard feels laggy even with low buffer: If you have reduced the audio buffer but still feel lag, check whether your output monitoring path adds latency. Some headphone amps or speakers with DSP processing add 5–20ms of audio output delay after the DAW. Test with headphones plugged directly into your interface.

Apple Silicon and MIDI latency

Macs with Apple Silicon (M1, M2, M3, and later) have significantly improved MIDI latency characteristics compared to Intel-based Macs. The unified memory architecture and more efficient OS scheduling mean that CoreMIDI timestamps are more accurate and jitter is lower. In practical terms, MIDI input latency on Apple Silicon Macs is rarely a problem even at moderate buffer sizes.

One important note for Apple Silicon: if you are running older MIDI tools or plugins that were compiled only for Intel (x86_64) and run under Rosetta 2 emulation, there is an additional translation overhead. Most MIDI-related plugins have been updated with native Apple Silicon builds. Check that all your MIDI processing plugins are running natively — in Activity Monitor, look for a "Kind" column showing "Apple" rather than "Intel" for natively built processes.

Battery life is also relevant: macOS can throttle CPU performance when running on battery to conserve power. If you notice inconsistent MIDI latency when away from power, go to System Settings > Battery and check whether "Low Power Mode" is enabled. Disable it during live performance or recording sessions.

Low Latency Mode and direct monitoring

Logic Pro includes a Low Latency Mode (accessible from the Audio menu or by pressing Cmd+Shift+L). When enabled, Logic automatically disables any plugins that add processing latency above a threshold you set, allowing you to play with a very small buffer without audio dropouts from latency-heavy plugins. This is particularly useful when you have reverbs, delays, or convolution plugins on mixer tracks that you want to keep in your project without them causing latency while tracking new MIDI parts.

Ableton Live has a similar concept through Reduced Latency When Monitoring, accessible in Preferences > Audio. This disables latency-inducing plugins on monitored tracks temporarily while recording, then re-enables them on playback.

Hardware audio interfaces often support direct monitoring — a hardware mixer within the interface that lets you hear your input immediately, bypassing the DAW entirely. This gives true zero-latency monitoring of audio inputs. While MIDI itself does not benefit directly from hardware monitoring (MIDI is not audio), the setup reduces total perceived latency by ensuring the audio output path is as short as possible.

Frequently asked questions