MIDI velocity · drum pads · troubleshooting
Soft Drum-Pad Hits Sound the Same? A Fixed-Velocity Audit
When a light tap and an accent produce nearly the same drum sound, do not start by changing your technique. Capture a tiny controlled pattern, compare the MIDI values before judging the audio, then test the pad, the sender setting, and the receiving instrument one layer at a time.
Scope: this is a diagnostic for a setup that receives MIDI notes. MIDI velocity is data attached to a Note On, and a receiving instrument can map it in its own way. The test does not certify a controller, repair hardware, or claim a universal velocity curve. FingerDrum does not automatically inspect external MIDI devices or change their settings.
Play four light, four medium, and four accented strikes on one pad with all routing fixed. If the captured velocities are identical, look for a fixed-velocity or source setting. If they differ but the audio does not, inspect the receiving instrument's velocity layers, zones, or dynamics. If the values vary inconsistently, return to pad response and technique—not a sampler setting.
Freeze one pad, one sound, and one record path
Use one pad and a newly recorded MIDI clip. Disable note-repeat, randomization, velocity processing, MIDI effects, and duplicate routes for this pass. Keep the same kit, channel, note, monitoring level, and instrument preset. Save a copy before editing. A changing sound or changing route makes a convincing comparison impossible.
Do not infer velocity from meter height alone. The MIDI Association describes velocity as part of a Note On message and says it determines relative loudness for a note; the receiving sound can still ignore or reinterpret that information. Yamaha's FGDP-30 guide likewise distinguishes a fixed Trigger Note Velocity value from a velocity curve and minimum/maximum settings. Those examples establish why a sender and receiver should be inspected separately; they are not instructions for every controller.
Capture a 12-hit ladder and write down the values
At a slow, comfortable tempo, strike the same zone four times in each group: light, medium, then accented. Leave enough space to read the event list. Do not chase target numbers or try to make the groups mathematically even—the question is whether your deliberate changes survive the path.
| Group | Hits | Captured velocity | Heard change? | First observation |
|---|---|---|---|---|
| Light | 1–4 | ____ / ____ / ____ / ____ | yes / no | ____ |
| Medium | 5–8 | ____ / ____ / ____ / ____ | yes / no | ____ |
| Accent | 9–12 | ____ / ____ / ____ / ____ | yes / no | ____ |
Use the editor or monitor that shows the data actually recorded by the target application. A controller's own display, a raw monitor, and a DAW clip can disagree when a filter or transformer sits between them. Log the channel and note as well as velocity, so a mapping mistake is not mislabelled as a dynamics failure.
Name the first mismatch instead of changing everything
| Code | What the ladder shows | Next isolated check |
|---|---|---|
FIXED | All 12 recorded values match, despite intentionally different strikes. | Inspect the sending device or MIDI effect for a fixed velocity, fixed curve, or replacement rule; confirm it with its exact documentation. |
RANGE | Values change, but are compressed, capped, or unexpectedly floored. | Check the sender's curve and its minimum/maximum limits, then repeat the same ladder. |
SOUND | Values clearly differ; the audio scarcely changes. | Inspect the receiving instrument's dynamics or velocity response. Ableton documents velocity zones for Instrument and MIDI Effect Rack chains; a zone can deliberately restrict which values reach a chain. |
PAD | Values jump around within an intended group, or some strikes are missing. | Keep software fixed and repeat slowly on the same zone; then follow the exact controller's setup guidance. |
ROUTE | Raw input differs from the stored clip. | Inspect record filters, MIDI effects, channel conversion, and duplicate inputs one at a time. |
A fixed setting is not automatically wrong. It can be an intentional production choice. The failure is only a mismatch between the behaviour you want and the one you have measured.
Use A0/B/A1 so a “fix” is evidence
- A0: save the original 12-hit clip and its values.
- B: change exactly one documented setting at the first failed layer; record a new ladder, not a hand-edited copy.
- A1: restore the original setting and repeat. The original result should return.
- B2: reapply B and compare all three groups at the same monitoring level. Keep it only if the intended contrast returns without new misses, double hits, or unwanted routing changes.
After the diagnostic, make the musical decision separately. A narrow range may be perfect for a machine-like pattern; a wider, stable range may suit expressive hand-played parts. Keep the captured clip and the setting name with the project so the next session starts from evidence.
Common questions
Does a different MIDI velocity always mean a louder sound?
No. It is a message value; the receiving instrument decides how—or whether—to use it. Compare data and sound separately.
Should I set every pad to the same curve?
Not by default. First show a repeatable mismatch on the specific pad and playing range you use. A documented curve can be a valid test variable, but it is not a universal correction.
Can I “fix” the clip by drawing velocities afterward?
That can be an arrangement choice, but it does not identify why the live capture flattened. Preserve an unedited diagnostic copy first.
Sources and access date
These primary sources document message semantics and representative controller/receiver settings. Accessed September 18, 2026.