Check out the updated hi hat guide to Superior Drummer 3! For version 2, see below in this article.
———–
Mapping the hi-hat pedal in Superior Drummer 2 can be very frustrating. Even when reading the software manual, it took me several hours to really grasp the process and manage to set it up correctly.
After a lot of trial and error, I was able to fine tune the process and I put together a “how-to” guide that anyone can follow.
It may look like a lot of work, but it’s not too bad when you know what to do, and you only have to do it once.
Note: I am using an Alesis Trigger I/O which is basically a very simple drum brain that doesn’t have built in sounds. However, the process I explain should work for any MIDI instrument (including all drum brains that can connect to the computer). For example, I even used these instructions to map a hi-hat to my MIDI keyboard, using one of the knobs as the “open” amount and one of the keys as the hi hat “hit”. I personally use Roland V-Drums, but any electronic drum set should work.
Set up your outgoing MIDI
Before getting into Superior Drummer’s settings, make sure you are outputting the correct MIDI data.
Your drum-brain, or whatever device you use to send MIDI to the computer, should be programmable to choose what note you want each pad to send. Refer to your specific device’s documentation on how to change these settings.
In General MIDI standards, Channel 10 is reserved for percussion, so use that as your MIDI output channel to remain consistent. You can probably use any channel and have it work, but you might as well set it up properly!
Confirm that your foot pedal’s continuous control (pedal pressure up and down) is outputting as CC004 (which is the Foot Controller CC message). You should be able to confirm this in your MIDI device’s (drum brain, etc) documentation.
Alternatively you can use a MIDI monitoring software to monitor the exact notes and CC messages your computer is receiving. This can be very valuable in setting up any MIDI mapping to avoid confusion. (You can also record some MIDI notes and automation in your DAW and write them down)
MIDI monitoring software options (many are free):
MidiYoke (PC)
MidiOX (PC)
MidiPipe (Mac)
Bone’s Midi Translator (Mac)
It’s best to use General MIDI standards for the three main triggers. Setup your MIDI device (or brain) to hi-hat to output the following MIDI notes for these triggers.
Open Hi Hat – A#1 (46)
Closed Hi Hat – F#1 (42)
Pedal Close – G#1 (44)
MIDI notes are often referred to in the form of musical notes (“A#1”) or MIDI notes (46). They are two ways of describing the same note (these are both the same), but your device may only display one or the other.
You can really use any notes you want to and just change the settings in SD2 later, but I’d encourage you to use these mappings because they are used universally; meaning your kit will automatically trigger the correct samples in a lot of other software outside of SD2 because they use the same standards.
Here is a list of all the General MIDI percussion mappings if you are interested.
SET UP SUPERIOR DRUMMER
Connecting the pedal’s levels of “openness”
Go to “Construct” (top left menu)
Go to the Instrument panel (bottom right corner).
Choose “Hats” in the Instrument drop down to edit the various hi-hat parameters.
Choose “hatsCtrl” in the Articulation drop down.
Type in CC004 or CC4 for the key. This connects your pedal’s amount of “openness” to Superior Drummer.
Connecting the “Open” hi-hat samples
Choose “Open 0” in the Articulation drop-down.
Hit “Remove” if there are any notes already entered int he “Key” parameter.
Type in A#1 and hit enter. This connects your open hi-hat MIDI trigger to the first of SD2’s open hi-hat thresholds. The more “open” the pedal is, the more “open” of a hi-hat sample SD2 will trigger.
Repeat this process for “Open 1-5” to connect all the open hi-hat levels of “openness.”
Go to the mapping menu (top left)
See that it highlights all of the articulations you have mapped so far.
Note: I noticed the current or previous mapping doesn’t always show up as highlighted, even though you just assigned it. This is a little confusing, but don’t worry if it doesn’t highlight right afterwards. Check it again later and it should be fine.
Connecting the Closed pedal
Back on the construct page choose “Close Pedal” as the Articulation.
Type in G#1 as the key.
Connecting all MIDI triggers to hatsTrig
In the construct section, choose the “hatsTrig” in the Articulation drop-down
Go back to the mapping section. Type in F#1, A#1 and G#1, hitting enter after each.
Below you can see all the notes that are mapped (highlighted as orange keys on the piano). It should look like this screenshot.
Now you have mapped all three MIDI notes to the hatsTrig articulation. This tells Superior Drummer that these are all the notes it is looking for when it needs to trigger a hi-hat sound.
A few things that make the process confusing
Viewing the orange keys in the mapping mode is the only way to check if you have multiple notes assigned to one articulation. For most articulations, aside from hatTrig, you will just want one note assigned. If you have multiples, use the “Delete” button in Mapping mode, or the “Remove” button in Construct mode. They both do the same thing, but Superior Drummer likes to make things seem confusing.
Keep in mind that often in Construct mode you will have an Articulation selected but the Key you typed in will be blank even though you have already assigned a key to it! This is another problem with SD2 that makes the process very confusing. Check the Mapping mode for that articulation to see that it has an orange key mapped to it. Often times the Key shows up as blank in the Construct mode, even though it actually is mapped. Superior Drummer is an evil bastard. (Oh, and don’t worry that you don’t see an orange note mapped for hatsCtrl because that is a Continuos Control message which is different from a MIDI note)
You should also know that “Note” in Mapping mode is the same thing as “Key” in Construct mode. Again, they just like to confuse you.
Another unintuitive problem is that to change the Articulation you are editing, you must go into Construct mode each time, change your Articulation selection and then go back to Mapping mode for more details, such as seeing all the notes that are mapped to it.
Pedal Correction

Select the hatsCtrl Articulation and go to the Mapping Mode. On the right hand side you are able to edit the curve of the CC values. This is how Superior Drummer interprets the values sent by your foot pedal for the the “openness” of your hi-hat. This is for fine tuning the feel to make it more realistic.
The high MIDI values signal when the hats are closed and the low values signal openness.
OUT Sliders (left): Leave these at full range as they are from 0-127. Pulling the sliders up or down limits the range of samples that can be triggered. For instance, if you pull the top slider down and limit the range of values, SD2 will only make “open” hi-hat sounds because the closed sounds are now out of range.
IN Sliders (bottom): Some MIDI pedals don’t output the full value range of 0-127. If your pedal only outputs as high as, 100, for example, you will never fully be able to close your hi-hat. This slider allows you to adjust the range of what your pedal actually outputs so you have a full, accurate range of control.
Use one of the MIDI monitoring applications (mentioned at the start of this tutorial) to confirm the range your pedal outputs.
Edit the Curve
Often the feel of the pressure you put on the pedal will feel off at first; not matching the “openness” of the actual sounds you are hearing. For example, maybe it is too open when it should be more closed sounding, or vice versa. Play around with the points on this curve until it feels more realistic.
Alternatively you can try some curve presets. These are located above the piano keys under Presets > MIDI > Pedal Correction
Remember to save your kit once you have it how you want it!
Furthermore
You can also add more features if you hi-hat pad allows for mapping the edge and bell and probably even more. My hi-hat pad is pretty basic so I am not able to test these features.
I should also mention that you can use the “Learn” function instead of typing in the notes into the “Key” section. Just press “Learn” and hit the pad you want to add. I personally advise against this because it has room for error such as triggering the wrong pad or multiple pads on accident. Just set your outgoing MIDI correctly and type them in by hand and it eliminates a lot of variables.
By Ivansc September 21, 2015 - 9:09 am
Thanks!
Very useful indeed.
But the part showing how to connect all MIDI triggers to hats trig is not immediately clear.
And isnt it a shame we cant do this sort of stuff in EZD2?
Regards, Ivan
By grayson September 21, 2015 - 3:08 pm
its the same as mapping all the others, except there are 3 notes instead of one. so you enter a note and hit enter each time. thats all there is to do. and you can confirm which notes you have added by looking at the piano on the mapping page… its kind of a dumb way of showing it, it should just show you the list of notes you have added. these notes can be added on either the mapping page or the contruct page, which i think i mentioned somewhere else, but they use a different word on each page even though its the same entry *smh*
By Blawck November 20, 2015 - 8:42 am
Hey man, thanks a lot for clarifying this! Saved my life from misery, annihilation, havoc, and obliteration
I have a question, regarding this part of you article:
“Connecting the “Open” hi-hat samples
Choose “Open 0” in the Articulation drop-down.
Hit “Remove” if there are any notes already entered int he “Key” parameter.
Type in A#1 and hit enter. This connects your open hi-hat MIDI trigger to the first of SD2’s open hi-hat thresholds. The more “open” the pedal is, the more “open” of a hi-hat sample SD2 will trigger.
Repeat this process for “Open 1-5” to connect all the open hi-hat levels of “openness.” ”
Does it mean that you put A#1 for Open (there is no zero here, I suppose just Open is the zero), A#1 fo Open 1, A#1 for Open 2, A#1 for Open 3, A#1 for Open 4 and A#1 for Open 5? Is it A#1 for all opens?
Thanks a bunch-a-bunch.
By grayson November 20, 2015 - 4:08 pm
Yes. A#1 is the MIDI note coming from your physical open hi-hat pad. “Open 1, 2, etc” articulations are basically the audio samples (recordings of the hi-hat being played) with different levels of “openness.” Because you want your open hi-hat pad (A#1) to be capable of all of these different sounds, you have to connect A#1 to all of them. So set up the first “Open 0”, and then do the same process for the rest of the “Open” articulations. If you only assigned one of the “Open” articulations, your hi hat would only connect to one audio sample, but you want that sample to vary depending on how open you have your foot pedal. That way it sounds and feels like a real hi-hat.
By Nick Blommel December 14, 2017 - 2:04 pm
Hi Grayson, I am trying this A#1 on all Open 0 through Open 5 but as soon as I go from Open 0 to Open 1 and enter in the A#1 value it removes it from Open 0. Same thing happens when I go to the next step. It is like only one articulation is allowed that note.
Does this make sense to you? It is driving me nuts. All my other toms and cymbals sound great but the Hi-hat (VH-11) is very frustrating. Hi-hat sounds perfect coming from my Roland TD9 module but SD2 seems to mess it up.
Thanks for all your help.
Nick
By Gary August 19, 2016 - 3:29 pm
Now why didn’t toontrack post instructions like these!!! Thanks!
By jdm August 25, 2016 - 6:00 pm
I think this is over-complicated, and likely not correct for SD2, anyway. You just have to map each note your hi-hat controller sends to hatsTrig and map the closed pedal and CC. Or, you can change your controller to send its various Open messages to the same one programmed in SD2 for hatsTrig. I have a Yamaha DTX905k, so created a separate kit for this.
Here’s my mapping. Basically just open & closed messages, in both tip and edge where appropriate, since DTX has multi-zone hats and cymbals.
instr. SD2 DTX DTX full name key note comment
Hi-Hat Closed tip hhBwCl hihatBow(closed) F#1 42 tip = bow
Hi-Hat Closed edge hhEgCl hihatEdge(closded) A#-1 22
Hi-Hat closed pedal hhFtCL hihatFootClose A-1 21
Hi-Hat open pedal hhSplsh hihatFootSplash B-1 23
Hi-Hat hatsTipTrig hhBwOp hihatBow(open) G#-1 18 tip = bow
Hi-Hat hatsTrig hhEgOp hihatEdge(open) F#-1 20
Hi-Hat ctrl CC4
By grayson August 29, 2016 - 3:19 pm
I am not using a DTX, I am using an Alesis Trigger IO. It’s basically as simple as it gets in terms of converting drums to MIDI. The process I wrote above will work for any instrument. Keyboards, finger drum pads, etc. An actual drum brain like a DTX could potentially make the process easier like you said, but this process works for any instrument.
By Mighty Unicorn November 27, 2016 - 11:30 pm
I am using a Roland TD-30 drum brain.
All is mapped properly, as things are looking to trigger perfectly. The problem is, SD2 can’t tell when I have the pedal tightly closed. I have mapped “Roland E-Drums” as the MIDI source.
When I follow your directions exactly as described, and I select “Hi-Hat” (“Hats” is no longer an option), then I look at the articulation drop-down list, there is no “Open 0” in the list anymore. The “Open” parameters now start with “Open 1”.
This kind of renders this instruction list irrelevant, does it not? Now that SD2 has changed the drop-down articulation list items, deleting the one that you specified, could you update this tutorial to reflect the reality of the current version of SD2?
Thanks!
By Todd December 1, 2016 - 8:00 pm
I have a TD 11 with CY5 hi hat trigger with Superior Drummer 2.0.
I have done all of this, and still the CC control/openess does not sound right.
The mid velocities/cc’s sound garbled. Anybody have a specific map for TD 11 that works with superior? I tried the Roland preset in Superior. Tried the pedal correction. IT doesnt sound right.
By Johnny August 18, 2017 - 8:20 pm
Hi,
I have a TD-11K. The problem I have is that SD2 is not interpretting the “openness status” of the foot pedal. I have everything as instructed, including CC4 in the hatsCtrl. I’ve used a midi monitor SW and i can see that when i press the pedal, the values are being read correctly. It’s just SD2 that is not doing anything with them.
What can be the issue? Do I need to activate anything else in SD2?
thanks!
By Clemens October 26, 2017 - 3:51 pm
Hi there, I have a problem you might know the answer for: When I press the hihat controller down to close hihat it triggers the tom sound as well. When I do the learn routine for the hihat, it works but it changes the sound of the tom as well. These two might be linked somehow. Any idea what that might be?
Cheers
By Nick Blommel December 14, 2017 - 2:43 pm
That may be due to your midi note numbers being the same. The fix to that would be to go into the control menu of your drum module and change your note number to something that is not already used. That is the process I go through using Roland
By Siadzix December 22, 2017 - 10:38 am
“Hi Grayson, I am trying this A#1 on all Open 0 through Open 5 but as soon as I go from Open 0 to Open 1 and enter in the A#1 value it removes it from Open 0. Same thing happens when I go to the next step. It is like only one articulation is allowed that note.
Does this make sense to you? It is driving me nuts. All my other toms and cymbals sound great but the Hi-hat (VH-11) is very frustrating. Hi-hat sounds perfect coming from my Roland TD9 module but SD2 seems to mess it up.
Thanks for all your help.
Nick”
I HAVE SAME PROBLEM HERE, Please reply.