1. Home
2. Support
3. Hits that never reach the app over USB MIDI

Support

Hits that never reach the app over USB MIDI

Updated 24 July 2026

The fix, step by step

1. Work out which failure you have. If the module itself does not react to a soft hit — no sound, no meter movement — the strike never registered, and no cable can carry a note that was never sent. That is a sensitivity problem; fix it in the module’s pad settings via that checklist. If the module clearly responds and the note is still missing, carry on here.
2. Try a different USB cable. A charge-only cable looks identical to a data cable — same connector, same length, same price on the shelf — and is the single most common cause of erratic MIDI.
3. Connect the module directly rather than through a hub, dock, or a monitor’s USB port. If a hub is unavoidable, use a powered one; an unpowered hub is a second point of failure you do not need.
4. On a Lightning iPad, use the genuine powered Apple Lightning to USB 3 Camera Adapter. An unpowered adapter cannot supply what a drum module draws, and it tends to fail intermittently rather than cleanly — which is what makes it easy to blame on the app. See connecting to a Lightning iPad.
5. Check whether the module is also driving a second destination — a computer, a DAW, another app — at the same time. Splitting its output can starve the connection reaching iQuantize even when each destination looks fine on its own.
6. Confirm what actually arrived in the app’s MIDI diagnostics. Every incoming note is logged as it arrives, so a hit that made it across the connection shows up there before you ever look at a score. If the event never arrived, no setting inside the app can recover it.

Why it always seems to happen on the busiest bar

A hi-hat roll sends far more MIDI messages per second than a slow groove does. A marginal connection that copes fine with a simple backbeat can start dropping notes the instant a part gets genuinely busy and asks for more than it can carry.

If notes only go missing in the fastest, densest bar of a chart and land cleanly everywhere else in the same take, suspect the link before you suspect your playing. A connection failing under load, rather than technique failing under tempo, is exactly the pattern that points at the cable.

It can make you look worse than you played

A hit that never arrives is counted exactly like a hit you never played: a missed note. Nothing downstream can tell “you did not play this” apart from “you played this and the connection lost it” — they are identical by the time a score is calculated.

So a flaky cable can genuinely drag a score down without you playing any worse, sometimes on the exact bar where you were most locked in. Rule the transport out before you read anything into a score. A cable swap and a repeat take cost two minutes.

This is the one way your gear can move a number, and it is worth keeping apart from the other one people worry about. A slow monitoring path — Bluetooth headphones, a fat audio buffer — cannot do this, because the timing comes off the MIDI message and never touches your audio output. A note that never arrives is a different failure: there is nothing to time. Delay in what you hear changes how you play; a dropped message changes what you are marked on. What e-drum latency actually is covers the first one.

Common questions