MIDI Drum Pad Velocity Feels Inconsistent? A 20-Hit Calibration Guide

Before changing settings, separate four layers

“The pad velocity is wrong” is not one fault. The MIDI Association explains that a Note On carries a note number and velocity, and that velocity is normally used to control relative amplitude. “Normally” matters because the receiving instrument still determines the audible response. Two hits sounding equally loud does not prove that the controller sent equal values.

The 20-hit baseline: make the problem repeatable

This 20-hit method is an editorial diagnostic framework from the FingerDrum team, not an industry certification. Its purpose is to hold the input constant before and after each change, replacing “it seems more sensitive now” with a result you can reproduce.

Prepare the test

1. Fix the physical conditions: place the controller flat on a solid, non-bouncing surface. Keep the palm and unused fingers off neighboring pads.
2. Disable constant velocity: turn off Full Level, Fixed Velocity, or an equivalent mode. Otherwise every output may be identical by design.
3. Reduce downstream variables: use one short sound with a clear attack. Temporarily bypass velocity gates, MIDI compression, randomization, and aggressive bus compression.
4. Test one pad first: calibrate a single pad, then spot-check the others with the same procedure. Do not change the whole map at once.

Play two groups of 10

For the first group, play 10 very light but intentional notes—the quietest motion you actually want to use, not an accidental brush. For the second, play 10 clear accents without slamming the pad. Keep the finger, strike position, and pacing the same. Log every velocity value when a monitor is available. Without one, record the audio and mark missed sounds, doubled sounds, and whether the two groups remain easy to tell apart.

Troubleshoot by symptom, one variable at a time

After each change, repeat all 20 hits. Do not move sensitivity, threshold, and curve together. If the result improves, you need to know what to keep; if it gets worse, you need a clean way back.

Novation’s Launchpad Pro MK3 guide treats velocity on/off, velocity curves, and pad trigger threshold as separate settings. Native Instruments provides a separate sensitivity procedure for Maschine pads. Those sources establish useful diagnostic categories; they do not make either brand’s labels or values portable to every controller.

What counts as calibrated? Retest against the same gates

The gates below are practical personal checks, not manufacturer specifications and not a performance rating. Tighten the quiet-hit requirement if ghost notes matter to your style. In a vibration-heavy live setup, prioritize protection against false triggers.

• Quiet hits are usable: at least 9 of 10 intentional light notes register.
• Accents remain controllable: all 10 accents register without every hit being flattened to the same maximum.
• No extra notes: the 20 physical strikes produce no visually or audibly confirmed double triggers.
• The groups separate: on blind playback, the light and accent groups are usually distinguishable.
• The result survives a restart: reconnect the device or reopen the project and repeat the test with the saved settings.

If “zero misses” brings frequent doubles, the setup is too eager for your motion and surface. If “zero doubles” removes all quiet notes, the threshold or filter has gone too far. Calibration means finding a repeatable working window for your playing and environment, not chasing a universal number.

After calibration: a five-minute accent ladder

Settings give the device room to represent dynamics; your fingers still have to produce them. Use one closed hat or short percussion sound for this 16-step drill. Start at a tempo you can control. Increase it slightly only after three clean passes; step back when missed or extra notes return.

Key: A = accent; q = controlled quiet hit.

1. Loop each row for 30 seconds. Move only the accent while keeping the other strikes consistently quiet.
2. Record all four rows. Check accent clarity, quiet-note detection, and whether the moving accent pulls your timing.
3. Alternate A and C. If transitions make you slam the pad, hold the tempo and reduce the motion.
4. For one comparison only, enable Fixed Velocity. The rhythm remains, but the dynamic target disappears. Turn it off again afterward.

Keep a calibration record you can reuse

Firmware, desk choice, pad wear, instruments, and performance environments change. A screenshot of parameter values alone cannot explain why the setup once worked; save the test conditions and result with it.

If the same controller settings behave differently across instruments, add the receiving instrument to the log. That comparison can quickly show that the change happens after MIDI input.

Common questions

When should I use Full Level or Fixed Velocity?

They are useful when you intentionally want every hit to output the same velocity, perhaps to enter a pattern quickly and edit it later. Turn them off for dynamic calibration and accent practice, or they hide whether the curve matches your touch.

Is velocity just volume?

Not exactly. The MIDI Association says velocity normally controls relative amplitude, while the receiving instrument determines the audible response. Inspect MIDI data and listen to the result so you can separate the controller from the receiver.

Can a software gate fix double triggering?

It can filter some low-value events, and Akai’s article demonstrates that approach. The cost is that a gate may also erase intentional quiet notes. Remove lingering pressure, excessive force, and an unstable surface first; treat filtering as a final tradeoff.