Every pad by its drum name
The kit view lays out the pieces of the General MIDI Level 1 drum map, which the MIDI Association publishes: kick 36, snare 38, closed hi-hat 42, pedal hi-hat 44, open hi-hat 46, toms from 41 to 50, crashes 49 and 57, ride 51 and ride bell 53. General MIDI puts drums on channel 10, and most modules send there by default. Hit every pad, then every rim and cymbal edge: each note lights its tile and shows how often it fired and its velocity range. Notes the map doesn’t cover appear under Other notes played, named where General MIDI has a name for them.
Turn on Sound to hear each hit through simple built-in drum sounds, a quick way to hear whether soft and hard hits really differ.
Velocity and dynamics
Play each pad from a light tap to a full hit. A pad that jumps straight to high velocities, or never gets past medium, needs its sensitivity or velocity curve adjusted in the module. The histogram in Velocity range shows the spread of your whole session.
Double triggers and crosstalk
A double trigger is one hit that fires the same pad twice. The Chatter check catches it (the same note within 30 ms) and marks the tile and the log line. Crosstalk is different: hitting one pad fires another, usually a neighbour on the same rack, at a low velocity. It shows in the event log as a second, quiet note a few milliseconds after the one you played. Raise the crosstalk cancel setting for the pad that fires by itself, or move it away from the one that sets it off.
The hi-hat pedal
Move the hi-hat pedal slowly from open to closed. Its position appears in the control list below the checks, usually as CC 4, with a strip of every value it has reached. It should move in small steps with no jumps. Some modules never use the whole 0 to 127 range, so the check may stay at Not done even for a healthy pedal; a gap or a jump in the strip is what points to a fault. If the hi-hat never sounds fully closed, calibrate the pedal’s offset in the module.