The notes that you associate names with – shown in the Drum Map’s Pitch column – are just the notes that Cubase uses internally to represent different drum-hit events. You can define these names directly from within the Drum Editor (just double-click on an instrument name to edit it), or you can do so from the Drum Map Setup panel. Cubase solves both of these problems with Drum Maps.Īt their most basic, Drum Maps associate a drum-instrument name with a MIDI note, and it is these names that are displayed in the Drum Editor’s instrument list. This can be a problem for producers when they want to experiment to hear how a rhythm part will sound through different drum-kit banks and/or instruments – the different sounds associated with each note can be comically different.Ī similar issue exists if you’re playing drum parts using a controller, because different instruments and sound banks may require you to learn different key layouts, or to reprogram your pad controller.
#Halion sonic se 3 drum kit map Patch#
Where one drum patch or sample bank may assign a kick drum to note C1, another may have a tambourine assigned to that note. The problem is that there is no common template or specification that governs the specific mapping of drum sounds to note numbers. However, whether it’s external hardware, plug-in software, or synthesised or sampled drum sounds (or a mixture of the two), nearly all of these drum-sound sources have one thing in common: drum ‘kits’ are stored as patches in which each drum sound is assigned to, and therefore triggered by, a specific MIDI note. T h ere are loads of ways to generate drum and percussion sounds in the studio these days – we’re spoilt for choice with all sorts of beat-making methods.
0 kommentar(er)
