Home
What e-drum latency actually is, and why it matters

Latency

What e-drum latency actually is, and why it matters

Updated 3 August 2026

Latency is the gap between your stick landing on the pad and the sound reaching your ears. On an electronic kit it is not one number you can dial out — it is a short chain of separate delays stacked between the pad and your headphones, and any link in that chain can add to it.

It does not change what iQuantize scores: timing is measured from the hardware timestamp each MIDI message arrives with, not from when sound arrives. It changes something worse than a number. It changes how you play, because you adjust to what you hear without ever deciding to.

Three fixes cost nothing and cover most cases: disconnect the Bluetooth headphones, use wired ones instead, or monitor your own kit through the module’s headphone output and let the app play the chart. If none of those does it, the full checklist goes further.

Five links between the stick and your ears

“Latency” suggests one delay you could dial out in a settings menu. On an e-drum kit it is really a short chain of separate delays, stacked between the moment the stick lands and the moment you hear it: pad-to-module trigger detection, the module’s own output stage, the USB transport to your device, the audio buffer your app or interface holds, and the output device itself.

Each link can add a little. A module might publish a spec for its own trigger-to-output delay, but that figure ignores everything downstream of it: the buffer size your interface or app is set to, and the conversion happening inside whatever you are listening on. None of them shows up as a single figure anywhere, which is why “where is my latency setting” is usually the wrong question.

Why you can’t just feel whether it’s fine

Your ears’ threshold for noticing a delay is far lower than most drummers assume. Long before a gap is consciously audible as an echo, you have already started compensating for it — dragging slightly, hesitating on ghost notes, or just feeling like the kit “isn’t responding”, without being able to say why.

It does not feel like latency while it is happening. It feels like you are playing worse, or like the kit has gone sluggish, on a night when nothing else has changed.

What the delay actually costs you

What a laggy monitoring chain corrupts is your playing. You play to what you hear rather than to what you did: dragging a little, softening the ghost notes so they arrive with the beat, leaning on the click harder than you should. None of it feels like a decision at the time.

So fixing it is not about protecting a number. It is about not spending an hour rehearsing a compensation for a delay that will not be there on a friend’s kit, on an acoustic one, or on stage.

Bluetooth adds 100 ms before anything else does

Bluetooth headphones and speakers typically add 100 ms or more before sound reaches you, which is well past what a drummer can play around. That delay comes from wireless buffering and the audio codec every Bluetooth link needs, not from the build quality of any particular pair.

That is why a “low-latency” Bluetooth model does not solve this: the buffering is structural to how wireless audio works, not a defect a better brand engineers away. For scored practice, use wired monitoring — the headphone requirements list is what we would judge a pair against.

A 30-second test, no measurement rig required

Play a slow, steady quarter-note pulse on a single pad and listen closely to the relationship between stick and sound. If the sound feels welded to the stick — arriving with it, not after it — your monitoring is fine.

If it feels like the sound trails the stick even slightly, you have latency worth chasing down. Do the same on a closed hi-hat: it gives you a hard, dry tick with nothing behind it, and you can hide five milliseconds inside a kick sample far more easily than inside that. Then take the result to the fix-it checklist.

Where the delay actually comes from

Pad to module: Trigger detection at the head or rim, plus any crosstalk rejection
Module output stage: Internal processing before the signal reaches a jack or USB port
USB transport: Buffering as MIDI crosses from the module to your computer or device
Audio buffer: The block size your app or audio interface holds before playing a sound
Output device: The final conversion, in headphones, an interface, or a speaker

Think you have a latency problem?

Play a steady quarter-note pulse and listen — then fix it with the checklist.

App Store Download for Mac

Requires an electronic drum kit or a MIDI-capable drum module.

Common questions

Does latency make my timing score worse?

No. Timing comes from the hardware timestamp each MIDI message arrives with, so your monitoring path never reaches the score. It reaches your playing instead, which is the part worth protecting.

Which single change fixes it most often?

Disconnecting Bluetooth headphones or speakers. After that, monitoring your own kit through the module’s own headphone output, which skips the USB transport, the app’s audio buffer and your device’s output stage in one move, while the app plays the chart.

Can I use Bluetooth headphones if I buy a good enough pair?

No. The delay comes from wireless buffering and audio codecs, not the headphone brand or build quality. A Bluetooth link typically adds 100 ms or more, well past what a drummer can play around. Use wired monitoring instead.

How do I know if I actually have a latency problem?

Play a slow, steady quarter-note pulse on one pad and listen closely. If the sound feels welded to the stick, you are fine; if it trails even slightly, you have latency worth chasing down.

Where do I fix it once I’ve found it?

The latency fix guide works through the checklist in order of likelihood, starting with the wireless link and ending at what your device is plugged into.