The most logical place to start is the velocity/value edit mode, which lets you vary the MIDI velocity of each step, adding a level of dynamic variation and interest into the part. Once you’ve set the number of steps, it’s simply a matter of inputting the note triggers into the step grid.Īs well as being able to switch steps on or off accordingly, there’s also a number of additional parameters that can edited by switching the edit mode. If you want to program a two-bar drum loop, set the step sequence to 32 steps rather than changing Pattern Region’s length. By default, the Pattern Region will be four bars in length but have only 16 steps, meaning that the step sequence will repeat four times.

One of the first points to consider with your Pattern Region is the desired number of steps you require.

Open the region and you’ll see rows with musical names (Kick, Snare, Hi-Hat, etc) rather than the cryptic note numbers common to the piano roll editor. Creating a new Pattern Region with an instrument from Logic’s library, therefore, creates a customised mapping grid that tallies with the drum kit you’ve loaded. These contain both the musical information and the mapping data that ties them to a given patch setting. With this display, it’s easy to quickly identify what part of the kit you’re working – especially when compared to the piano roll editor – and, more importantly, you can program complex rhythm patterns across multiple drum voices.įor the Step Sequencer to work, it needs its own unique type of region, called a Pattern Region. The Step Sequencer displays its musical information in grid form, with a unique Row (much like a track lane) for each part of the drum kit. Though not exclusively designed for drums, there’s no doubt that the Step Sequencer pairs perfectly with drum-based virtual instruments, especially those included with Logic Pro X.

Automation logic pro x