When programming and editing drum patterns, you have two options now: Classic MIDI Roll, or Pattern Event.
Competitors have hybrid options, and they work fantastically.
Show the names of the drum type on the piano keys instead of the typical key name when using the MIDI roll. For example: Instead of ‘C1, C#1, D1…’ it shows ‘Kick, Snare, CH…’ and collapse the editor to only show keys with drums on them. (Bitwig does this in the most natural way, for reference).
We should be able to copy/paste/delete/duplicate in the Pattern Editor
The weird quirk when you make a pattern event, add a pattern, then delete the pattern event and change track to MIDI event, create a MIDI event on the track, and it still plays the deleted pattern…needs to stop.
This has been doable in Cubase since forever, if you select a drum map for the track. Then the drum editor will open instead of the key editor, which features the drum names (as defined in the drum map) and also can collapse the view to only the drum notes used.
From what I can tell, the only way this works is to create a MIDI track (not an instrument track), route that track to an instrument track with a VST drum machine on it (Groove Agent, for example), and then create the drum map in the MIDI track…is this really the only way?
Is there no way to just right click > add drum track, and use the drum map?
If not, that is an absurd way of doing things lol.
I’m sure there’s some reason for it, but I really cannot see the sense in it.
I might be mistaken, but isn’t it the case that currently, when you double-click on a part of a Drum Track, the Key Editor (usually the default editor) opens and not the Drum Editor, which would actually make sense?
Moreover, you can’t assign a Drum Map to a Drum Track to achieve this behaviour, like in a MIDI or Instrument Track.
Ya, if you double click or create an event in the timeline in any way, it default creates a key editor, unless you have ‘pattern event’ selected in the inspector. But, the issue is that you cannot have a Drum Map on the Drum Track lol which….seems insane.
So the only way to do it is to make a second midi track (Just a midi routing track, not an instrument track) and route it to the drum track.
And even then, it’s not like it extracts the names of the samples or drums used on each midi note, so you have to basically open this huge spreadsheet and manually type in every drum piece.
It’s wild. It feels like 2005 in here sometimes lol
I’m pretty sure there weren’t any such glitches in Cubase SX 3.1
I’m increasingly getting the unsettling feeling that not a single person at Steinberg has actually spent a single minute really working with Cubase. All the flaws only come to light after the release of the version, through feedback from paying customers. How else could such a multitude of hair-raising errors, such as those in MIDI remote control, color settings, hub problems, and many other shortcomings like these, remain undetected in the “final product”?
Or am I simply too conservative and think that by buying a product I have a right to its guaranteed functioning?
Shortcut: you don’t need to switch this in the Inspector. If you hold down the Ctrl/Cmd key when creating a part it will always be the opposite of the setting in the Inspector.
That’s most probably not true. The flaws that came to light before the release also might have been addressed before the release and thus you’ll never get to see them.
Nevertheless, I also would wish for less bugs in Cubase.
