The way I did it was to write down, on a piece of paper (!) the midi notes for each kit piece in SD3 (both heads/centers and rims), then enter those numbers for each user kit on my module. I also renamed those TD-9 user kits so I can see at a glance which set of toms I'm triggering. So, on the TD-9 I created a number of user kits with different midi mappings ( how to map your pads exactly depends on your module - on the TD-9 it's FUNC->MIDI) so that I can just change the kit on the module to have my physical rack tom triggering Tom 1, Tom 2, Tom 3 in Superior Drummer, etc. I also have some aux pads/triggers, so out of the box nothing translates correctly to SD3. I'm using a TD-9, but configured as 1 rack tom, and 2 floor toms. I could midi-learn the different pads and possibly save a User Preset but it's a pain in the ass to do, plus I don't know if you can easily midi-learn all articulations (all of my toms including the rim "click" sound trigger, which I love on toms). How do you guys work around this? Should I just set up a couple extra tom pads, just to have them available for other kits? It's not ideal as I've gotten used to my layout (as most of us have). I was hoping it would just move further down or something. it just triggers the Racktom 1 in addition to my 1st tom trigger. Because my tom 1 trigger does trigger the Racktom 1 on screen, my tom 2 trigger does not trigger floortom 1 (like I would expect Superior to intelligently re-map it). But when I have my stuff mapped, I have to manually "learn" that specific kit. Other configs might have the "1 up, 2 down" style. Like the default, tom 1 is the smallest tom, and then tom 2 is the 3rd tom, and tom 3 is the 1st of two floor toms. My two racktoms are Racktom 1, and my floor is Floor 1. When loading different kit presets (even just with the Core library), you'll notice say, the Gretsch Default is a racktom and a floor.
0 Comments
Leave a Reply. |