◂ All articles
Velocity ceiling2 min

My MIDI velocity is capped: is the pad really the problem?

Plug your kit in

Don’t guess, measure. The kit check is open to everyone and needs no account.

Check my kit

You hit hard, yet the MIDI monitor stays well below the top of the range. The notes are there, but their values seem capped. eDrumWork calls this D04 when repeated strong strokes stay abnormally low compared with your normal playing.

The guided eDrumWork diagnostic compares those groups before you change anything on the module.

Must every accent reach 127?

No. A well-configured kit does not need to output 127 on every accent, and chasing that number can compress your whole dynamic range. The real warning sign is a lack of progression: you clearly hit harder, but the values stay bunched in the low or middle range.

Compare each zone with itself. A crash, a tom head and a snare do not share one universal target.

A test that avoids false conclusions

  1. Play several normal strokes in one consistent area.
  2. Follow with several controlled strong strokes.
  3. Look at the median, the maximum and the spread.
  4. Repeat to check that the difference is stable.

A low value near the edge of a center-triggered pad may reflect position rather than force. Hitting the same spot every time reduces this confusion.

If MIDI rises as it should while the sound stays quiet, check the mix, the virtual instrument or the audio level. If the raw values stay low, look at the response settings documented for your module.

Raising the output can help accents but may push ordinary hits toward the ceiling, which creates D03. Note the initial settings and retest all three playing levels after every change.

eDrumWork does not promise a perfect number. It checks whether strong playing really gets more MIDI headroom than ordinary playing.

Test my pad's velocity ceiling

Beta feedback and tools

Tell us what got in your way. Review the technical details before sharing.

Review technical details

The report includes your text and the context shown here. No MIDI, audio, private library or request log is attached. Submitted reports are stored with your account and deleted with it.

{
  "reportKey": "",
  "category": "blocker",
  "impact": "partial",
  "message": "",
  "context": {
    "audioChain": null
  }
}
Prepare email

Your email app sends the message. Attach the downloaded report and, if useful, a screenshot you choose. Fallback contact: betatest@edrumwork.com