The first screen shot (above) shows the Drum Editor window open for a MIDI track using the default GM‑based drum map. I'll then work through the construction of two example drum maps for the two popular drum sample instruments I mentioned above, but the same principles could be applied to any set of sampled drum sounds.
In addition, Mark Wherry discussed both of these back in SOS October and November 2003, so I've no intention of going through all the basics again here: a brief reminder of some key points will suffice, and you know where to go for some extra homework if required. The Cubase Operation Manual does a decent job of describing the main features of the Drum Editor and Drum Map functions. However, when programming your MIDI drum parts, you need to know that the MIDI notes you play are going to trigger the sounds you want to hear - and that's where a knowledge of Cubase's Drum Maps can come in handy. As an alternative, drum sample libraries such as Toontrack's Superior Drummer 2 or FXpansion's BFD2 offer amazing levels of detail, often with a large number of different performance articulations for key kit pieces such as snare or hi‑hat. The GM Drum Map being used in the Drum Editor.įor many home and project studio owners, recording a full drum kit is simply not a practical option.
Fortunately, you can create your own dedicated drum maps. Many Cubase users also own high‑quality drum virtual instruments and sample libraries that aren't mapped to the GM standard.
0 kommentar(er)
