Saturday, October 3, 2026
Friday, October 2, 2026
Cubase: Beat Designer
Beat Designer: drum machine‑style pattern creation with a simple workflow.
Create drum machine‑style grooves in a flash with Cubase’s Beat Designer.
Classic drum machines such as the LinnDrum or those in Roland’s TR range helped to shape a whole smörgåsbord of electronic and dance music styles, but their influence didn’t only live in the distinctive sounds they offered: the grooves of their drum patterns were also a hugely significant factor. The feel of these grooves came from the grid‑based pattern creation process that lay at the heart of these machines — and with Cubase’s Beat Designer MIDI plug‑in you can emulate that workflow. What’s more, with a few key tricks under your belt, patterns can be created really quickly. So, without further ado, let’s explore Beat Designer’s, um... beat designing options!
Basics: Sounds & Beats
You can configure Beat Designer’s lane layout to suit your needs.Beat Designer is placed as a MIDI insert plug‑in on whatever instrument track you wish to use. You’ll need to load a suitable drum instrument, of course, and the bundled Groove Agent SE or a sliced drum loop within a Cubase Sampler Track both make good candidates. Beat Designer does include some good beat presets and, as I’ll discuss below, a single instance can host up to 48 different patterns (four sub‑banks of 12 patterns each). It’s easy to switch between patterns too, and if you set a cycle region and let Cubase loop playback, you can audition your pattern creations as you work. Initially, though, Beat Designer opens ready for you to start creating from scratch, without any pattern pre‑loaded.
The central part of Beat Designer’s GUI is occupied by the pattern grid. Arranged vertically on the left side is the list of eight individual drum lanes and you can add/subtract lanes as required via the small ‘+’ and ‘‑’ buttons on the far right of each lane. If the default drum selections don’t suit, you can use the drop‑down menu in each lane to pick the drum sound target from your drum instrument. You can also use the small speaker icon to audition each selected sound; it’s simple and easy to configure.
You can add hits by either clicking on a single lane/step, or clicking and dragging to add multiple hits (for example, on the hi‑hat lane). Where you click vertically within a step provides initial control over that step’s velocity (high velocities at the top, low at the bottom). Hits are colour‑coded based on velocity. Clicking and dragging up/down on a step lets you adjust velocity or, if you hold Shift while clicking/dragging, change the relative velocity up/down (until a step reaches min/max velocity values) for all active steps in a lane. You can also change the velocity on selected multiple steps by clicking/dragging vertically on one step, and then dragging sideways across other active steps before then moving up/down to set the velocity. Equally, you can add volume ramps up/down by repeating this same mouse movement while holding the Alt/Opt key. And, of course, clicking on an already active step deactivates it.
If you don’t want to roll you own, Beat Designer includes a good selection of pattern presets to explore and adapt.This whole process is really simple and obviously makes for very speedy rhythm creation, but there are further useful shortcuts on offer too. For example, holding Shift, clicking on a step within a lane and then dragging left/right allows you to move all the steps within a lane. You can also copy one lane to another by holding Alt/Opt and clicking within the lane label area, then dragging to the lane where you wish to place the copy. And, for some further interesting rhythmic experiments, hold Alt/Opt and drag left/right over a lane: this inverts all the steps (so active steps become inactive and vice versa).
Step, Swing, Flam & Offset
The number of steps and the step resolution can be set on a per‑pattern basis. Both settings are located top left of the GUI, and there’s some fun to be had here, particularly if you create a pattern using a tried and trusted 16 steps/16th‑note step‑length format and then change the number of steps or pick a triplet step‑length format. Equally, if you use two separate drum instruments, each with its own instance of Beat Designer but set to different step counts or step lengths, you can be rewarded with some very cool — and sometimes wonderfully odd! — rhythmic interaction.
Beat Designer can also apply swing on a per‑lane level to every second beat in a pattern, or every third beat if using triplet steps (so bear in mind that the number of steps you use influences how swing impacts). For each pattern, you can configure two levels of swing, using the sliders with the diagonal icons that are found at the bottom right. For each lane, swing can be set to off or to one of the two swing amounts, using the appropriate diagonal icon at the right end of each lane. This can be a great way to add a nice groove to your hi‑hats, for example, but more extreme swing settings on your hats, kick and snare also let you experiment with the more ‘uncomfortable’ rhythms used in some types of hip‑hop or lo‑fi music.
You can add one‑, two‑ or three‑note flams to any active hit — their timing and level are configured using the group of sliders located bottom left and set at the pattern level. If you hover the mouse over the bottom of any active step, a three‑dot icon will appear and you can click this to add one, two or three flams to that step.
The horizontal sliders found to the right of each lane (next to the on/off buttons for swing) apply a timing offset for that lane, allowing you to push/pull the timing of the active hits relative to the main grid. This serves two main functions. First, you can use it in a corrective fashion; for example if the lane is triggering a sample that contains a short rise to its peak level you might want each hit earlier in time for that sound. Second, you can use it more creatively to create a rushed (ahead of the beat) or laid‑back (behind the beat) feel to elements of your groove. Or if Dilla‑style hip‑hop beats are your thing, you can use it to explore just how ‘off but not off’ you can take your rhythms. As with the swing settings, offset settings are configured at the pattern level.
Pattern Performer
As mentioned above, a single instance of Beat Designer can hold up to 48 different patterns. These are managed using the four sub‑bank and 12 pattern buttons, found at the bottom centre of the GUI. Slots that contain a pattern are indicated with a small circle icon, and clicking on a specific sub‑bank/pattern button combination makes that pattern active for editing/playback. Dropping down the Pattern Functions menu (found at the top right) provides menu options for copying, pasting and clearing patterns. This makes it easy to create variations: just duplicate a pattern and then customise the copy.
The Pattern Functions menu allows you to perform various operations in Beat Designer or export the MIDI patterns to your DAW tracks.This menu offers a couple of other useful functions. First, the top three entries let you shift an entire pattern left/right one step at a time or to reverse the whole pattern. Second, courtesy of the options at the base of the menu, there are a number of ways to copy the contents of a pattern, or all the patterns within one of the four sub‑banks, onto a Cubase MIDI or instrument track, and once there you can further edit the MIDI using the Cubase’s standard MIDI or drum editors. A particularly useful option is the Fill Loop With Pattern command: this inserts the current pattern as many times as required to fill the region between your left and right locators, and it’s a super‑quick way to get your initial Beat Designer drum groove up and running so that you can work on other elements of the track. (Once you’ve copied your pattern data to a MIDI track, remember to bypass Beat Designer, so as to avoid any double triggering of notes!)
If you prefer to create a performance by triggering pattern changes on the fly, enabling the Jump button (top right of the GUI) lets you use the four‑octave key range from C1 to switch between any of the 48 pattern slots. Once Jump is enabled, the GUI adds a Now button that allows you to toggle between instant pattern switching or switching at the start of the next bar, and you can record the trigger notes to capture your performance (and, if you wish, edit them after recording).
Get Creative
You can create all sorts of beats using the various tools I’ve outlined above (inverting lanes, different step lengths, shifting lanes left/right, etc) but the real beauty of Beat Designer is its speedy workflow — if classic drum machine beats are what your project needs, then it is well worth taking the time to explore it. Meanwhile, just to give you an idea of the sort of pattern variations you can generate really quickly, I’ve included some audio examples on the SOS website: https://sosm.ag/cubase-0823
Thursday, October 1, 2026
Wednesday, September 30, 2026
Cubase: MIDI Logical Editor
The Extract Kick Drum (C1) to New Track preset.
When it comes to MIDI editing, Cubase’s MIDI Logical Editor can do magic!
If I had to identify options for a ‘most underutilised features in Cubase’ list, prime candidates would be the Project Logical Editor (found only in the Pro version) and the MIDI Logical Editor (found in the Pro and Artist versions). Both are incredibly powerful editing tools but, because they use Boolean logic (commands can be chained together to make ‘true or false’ decisions, which determine the eventual editing outcome), they can also seem somewhat intimidating. It’d be a great shame if you let that put you off, though, because both are incredibly useful and have the potential to streamline lots of repetitive editing tasks. Fortunately, Steinberg include some excellent presets for them in Cubase, and unpicking an example or two provides a fairly gentle entry into these powerful tools. In this column, I’ll do just that for the MIDI Logical Editor, which is, as its name suggests, a tool for doing things to your MIDI data.
Double Your Kick
Let’s start with a preset that’s easy to understand, yet turns a very common MIDI editing task into something close to a single click: Extract Kick Drum (C1) to New Track. Layering multiple sounds is common practice with MIDI‑based drums so, for this example, let’s assume we have created a MIDI clip that triggers our main drum virtual instrument (VI), and we want to double the kick performance with a second VI.
The first screen shows the content of the preset (the preset system is accessed at the very top of the UI). The upper panel (Event Target Filters) lets you specify criteria to define what MIDI events are selected for editing. In this case, there are two criteria used. The first simply states that the Filter Target ‘type’ is ‘equal’ to a MIDI ‘note’, meaning that all MIDI notes (and nothing else) are potential targets for selection. However, the second line refines that selection by specifying that the note’s pitch must be equal to C1 (that’s the default MIDI note used for the kick drum, though you can change this if desired). The entry in the Bool column (on the right of the UI) is worth paying attention to. In this case, it is set to ‘And’ (as opposed to ‘Or’). This means that the MIDI Logical Editor will only select items that meet both the first and second criteria. For this preset, that means it will only select MIDI notes whose pitch is equal to C1.
In this preset, the GUI’s lower panel (Event Transform Actions) is empty. I’ll cover this section below but for now note that, with no entries here, the selected MIDI data (notes with a pitch of C1) will not be altered in any way. However, at the very bottom of the GUI, Extract To Track has been specified — so when we hit the Apply button, all the selected C1 notes will be copied from our main drum MIDI clip into a new MIDI clip and placed on a new track. Hey presto! We can now assign this track to an additional kick drum sound, to layer perfectly with our original.
While this is an editing task that you could perform manually, that requires a number of steps. Using the MIDI Logical Editor preset is faster — and faster still if you assign this preset to a key command (the Key Commands window has sections covering both the MIDI and Project Logical Editors). For presets you use regularly, the task then becomes a single click, whether for one selected MIDI clip or several.
Add A Bass Note To Chords
Now we’re familiar with the MIDI Logical Editor concepts, our second example preset, Add Sub Bass To Chords, can be explained fairly easily. With a suitable MIDI clip selected, the Filter Target criteria in the preset will search through the clip to find notes. If it finds a time position where at least two notes are playing (a simple definition for a chord), it will select the lowest note in each chord.
The Add Sub Bass to Chords preset.
The Transform Action panel is also used here, and has two entries. The first subtracts 12 from Value 1 (in this context, Value 1 is note pitch), while the second subtracts 20 from Value 2 (note velocity). Also notice that the specified action is ‘Insert’. So, when we click Apply, this preset selects the lowest note in every chord in the clip, lowers its pitch by an octave, reduces its velocity value by 20, and then ‘inserts’ those transformed versions of the notes into the clip, leaving the original notes intact. So your clip now contains a lower (octave down) bass note for all the identified chords. Ta‑da! A simple way to beef up any MIDI part containing chords.
Incidentally, the most common of these (sometimes rather cryptic!) labels (Value 1, Value 2, etc) are explained within the Operation Manual PDF, should you need a reference.
The 10% to Downbeat 4_4 preset (at the top), with the MIDI before (middle) and after (at the bottom) the preset has been applied.
Beat Accenting
Our final preset example demonstrates something a little more sophisticated: the ‘note accenting’ preset, called +10% to Downbeat 4_4. As in the previous examples, the Target Filter is looking for MIDI notes and, for the notes selected, Value 2 (note velocity) is transformed by multiplying it by 1.1. However, it’s the additional Target Filter criteria that make this interesting. These all consider the position of the note within the bar, and each defines a position range around the main four beats of the bar (this is done using PPQ values; Pulses Per Quarter note, which is MIDI’s unit of timing).
Notice that the Bool term used for these Position filters is ‘Or’. This means that, to be selected for editing, the MIDI item must both be a note ‘And’ (the Bool term used in the first criteria) an event which sits within the first Position timing range, ‘Or’ in the second position timing range, ‘Or’ the third... and so on. Notice also that the last Position criteria is there to catch notes at the very end of the bar; that is, notes played ‘early’ at the start of the next bar.
The screenshot shows what this preset does to the MIDI velocity data for a simple MIDI clip created using the Arpache SX MIDI plug‑in. In the original pattern, every note has the same velocity but, after the preset has been applied (actually, I applied it five times to make the changes more obvious), notes falling on or very close to the beats are emphasised, giving the performance a stronger rhythmic character. You could easily apply this preset to any MIDI clip (for example, MIDI drums), and similar presets are available that emphasise different beat combinations. You can drag within the position displays if you want to adjust the range specified in these criteria. If you like this one, then do check out the Crescendo In Cycle range preset — that’s also brilliant.
Want to create some semi‑random changes to your MIDI parts? The Event Counter parameter provides one possibility when added to a suitable preset.
Homework
For your MIDI Logical Editor homework, I’ll leave you to ponder one final screenshot that shows one of my own DIY presets. As the preset title suggests, for the selected MIDI clip(s), the first Filter Target criteria is looking for MIDI notes. However, in the second criteria, for the Last Event type (the MIDI notes), only Every Other Event will be selected and, in fact, by then using the Event Counter (Parameter 1) set to 7 (Parameter 2), only every seventh note within the sequence ends up selected.
We could then apply a number of different Transformation Actions to process the selected note but, in this case, I’ve simply chosen to Delete them. Having deleted every seventh note in the original MIDI clip, if we apply the preset a second time, the selected (and then deleted) notes fall in different places. Repeated applications to something like the steady arpeggio pattern shown earlier will break up the regularity of the notes in an almost random fashion, so can create useful variety. You can increase this sense of randomness by creating a second preset that uses a different value (Parameter 2) for the Event Counter. If you create key commands for each preset, they’re then easy to execute on the fly — and, if you don’t like the results, just execute Undo until you get back where you started. Of course, if doesn’t just have to be Delete; you could apply Transform Actions to change the pitch, velocity or even the position (which can be an interesting way to add variations to the timing/feel) of the selected notes.
The Power Of Logic
This short introduction won’t make anyone a MIDI Logical Editor ninja overnight, but it does shows how gentle exploration and editing some of the supplied presets can take you towards understanding what’s going on under the hood. Hopefully, it also shows you that the MIDI Logical Editor needn’t seem so intimidating — and reveals some of the potential of this powerful Cubase feature!
Tuesday, September 29, 2026
Monday, September 28, 2026
Steinberg update Cubasis and Dorico apps
Toggling the bypass status for insert plug‑ins on multiple tracks: a great shortcut for A/B comparison.
Embrace the power of Cubase’s Project Logical Editor, and you can become a workflow ninja!
In last month’s workshop I demonstrated just how powerful the MIDI Logical Editor, found in both the Pro and Artist versions of Cubase, can be for manipulating MIDI data, but as I mentioned in that column Pro users also have something called the Project Logical Editor. This is a similar logic‑driven tool that allows you to simplify complex tasks, but in this case rather than work with MIDI data, it’s used to streamline project‑level tasks. As with the MIDI Logical Editor, if you’re not used to working with Boolean logic, the Project Logical Editor can feel intimidating at first, but exploring just a few example presets will soon get over that initial speed bump.
Better In Or Out?
We’ll start our introductory tour with a preset that’s conceptually easy to understand yet does a super‑useful job. ‘Toggle Inserts Bypass of Selected Tracks’ is found in the Mixing category of the Factory presets and does as the name suggests: action this preset and all the insert plug‑ins on the currently selected tracks will have their bypass status switched, with active plug‑ins put into bypass and bypassed plug‑ins made active. The first screen shows how this is achieved.
As with the MIDI Logical Editor last month, the options in the Event Target Filters panel dictate what objects are to be selected. The Event Transform Actions panel then specifies what changes are to be made to those selected objects. In the upper panel, the ‘Container Type’ is selected if it is ‘Equal’ to ‘Track’ and if its ‘Property Is Set’ to ‘Selected’. This means that only tracks that you’ve selected within the Project or MixConsole windows are going to be changed by any of the commands specified in the lower panel. In that lower panel, a single entry applies a ‘Track Operation’ to the ‘Inserts Bypass’ parameter: it ‘Toggles’ the status of the bypass setting. This preset can be a really useful function for A/B comparisons. For example, you can select all your subgroup bus tracks and quickly bypass their insert plug‑ins to check whether all those mix processing moves are helping as intended, or hindering. Another scenario is use it on one or more tracks to toggle between two instances of an EQ or compressor (or both) that are configured with different settings, to see which you prefer.
And since you can configure a key command to execute any Project Logical Editor preset, once you’ve selected the tracks you wish to work with, a single click lets you toggle the bypass status of all the insert plug‑ins. There are other (equally useful) presets within this Mixing category that provide similar ‘bypass’ options for the sends and EQ panels within the MixConsole — I’ll leave you to explore their potential!
It’s easy to clear out unwanted automation data for only the selected tracks in a specific song section.
Automation Reclamation
Have you ever got deep into a mix and decided that within one section of the song, the mix just isn’t quite right? Stripping out the automation data (for example, volume, pan, EQ, and any send and insert effects) in a single project section can be a time‑consuming process. Thankfully, there’s a Project Logical Editor preset for that: ‘Delete All Automation Data for Selected Audio, Instrument and MIDI Tracks inside Cycle’.
The name may be a bit of a mouthful, but this preset does what it says on the tin. Once you’ve placed the left and right locators around the appropriate section of the project timeline, simply select which tracks you wish to remove the automation data from, then execute the preset. As shown in the screenshot, four entries in the Event Target Filters panel do the heavy lifting. The first two selection criteria identify that ‘Media Type’ that is ‘Equal’ to ‘Automation’ data and that it is ‘Contained’ within an ‘Event’ (ie. an audio or MIDI clip). However, the selection process also considers the third and fourth criteria: the automation data must have a ‘Position’ ‘Inside Cycle’ (between the left and right locators) and the ‘Parent Object Is Selected’ (the ‘Parent’ property is the Track upon which the event sits), so only tracks you have already selected will be acted upon by the preset.
For the automation data that fulfils these combined selection criteria, no transformations are specified in the lower panel. But at the base of the UI, the ‘Delete’ action is specified. When we hit the Apply button, any selected automation data is therefore deleted and replaced by a straight automation line joining the nearest automation points before and after the left and right locators. As a means of cleaning up an unwanted mess of automation data within selected tracks in a portion of a project, it’s a pretty speedy solution.
This preset is a great candidate for DIY modifications. For example, if you select the last of the current criteria, you can use the Insert button to refine the selection further. And if you enter ‘Name’ as the Filter Target, ‘Contains’ as the condition, and ‘Volume’ as Parameter 1, then only volume automation data will be selected. When this revised version of the preset is applied, volume automation is reset but other automation data is left intact — very useful if you just want to rethink the track levels within a song section. Of course, you could also apply the preset across your entire project by simply placing the left/right locators appropriately...
Ready to tidy up your unwanted muted parts?
Refuted When Muted
As I work through a busy project, I’ll often end up with lots of audio and MIDI clips that I muted as I ‘trimmed the fat’ while mixing. Once I’m happy that these elements are surplus to requirements, the ‘Delete All Muted Parts And Events’ preset (in the Parts And Events category) provides a speedy way to declutter. The screenshot shows the selection criteria used to find all the muted elements in your project (as with the previous example, no transformations are applied in the lower panel; the selected items are just deleted when you hit Apply). The key thing to note is how the selection criteria find only ‘Container Types’ that are ‘Equal’ to MIDI ‘Parts’ or (in the Bool column) audio ‘Events’ or ‘Audio ‘Parts’. The final entry then ensures only those Events/Parts that are currently muted actually get selected. Usefully, there’s also a Delete Muted Tracks preset (in the Tracks category) if your project requires a different ‘tidy up’ strategy.
It’s easy to add the date (or other details) to selected track names with the Project Logical Editor.
Make A Date
The final screenshot shows the ‘Add a Date to selected MIDI + Audio Track Names’ preset (from the Naming category). Given our earlier examples, the approach used in the four Event Target Filters panel should feel familiar. The four entries combine to identify all ‘Container Types’ that are ‘Tracks’, and that have the ‘Property’ of being ‘Selected’ and the ‘Media Type’ is ‘MIDI’ or ‘Audio’.
All tracks that meet these criteria (essentially all MIDI or Audio tracks that you have selected within the Project or MixConsole window) are then subjected to the entry in the Event Transform Actions panel. The Action Target is the track’s ‘Name’, and the Operation is set to ‘Append’ (that is, add something to the existing name). In this case, Parameter 2 is set to ‘Std. Names’ (if you click on this, a drop‑down menu of options appears) and Parameter 1 is ‘Date’. When you hit the Apply button, every selected audio and MIDI track has the current date added to its existing name.
For projects you’ll be working on over an extended period of time, adding the date to specific tracks can be a really helpful reminder of how the project has evolved. Which vocal take was the original? What’s the most recent version of the saxophone solo? And, if you work with collaborators and want to keep track of who added what to a project, you can simply adapt this preset by clicking on the ‘Date’ entry in the Parameter 1 column and type your own text such as your name or initials. Run both this modified version and the original ‘Date’ version, and every track you select can get your name/date added to its name, making it easy to see who has done what (and when) as the project moves between the various collaborators.
Surface Scratching
The above examples are very much the tip of the Project Logical Editor iceberg, but they should show you the potential for automating some pretty complex tasks. I hope they’ll encourage you to explore the various preset categories to find titles that might be useful to improve your own Cubase workflow. And remember, many of these presets can be candidates for the kinds of simple DIY customisation demonstrated above — even if you don’t feel ready to roll your own presets from scratch.
Combining the MIDI Logical Editor and Project Logical Editor with the use of key commands and the Cubase Macro features (both topics we have covered here in the past but are probably worth revisiting soon) can be absolutely transformative to your Cubase workflow — and bring Cubase ninja status within reach!