If this or any other toolbar buttons I mention are not visible in the Drum Editor, click the gear icon at the top-right of the editor’s window to open a menu from where you can enable it. The grid displayed by the Drum Editor is dependent on the active Grid Type, which is accessed via a drop-down menu on the toolbar at the top of the editor window. The menu also has options for opening the Drum Map Setup window, where you can load, configure and save maps, and to import a map from the VSTi providing the drum sounds (if the VSTi supports this feature). Clicking in this field opens a pop-up menu from where you can choose from the currently available maps – a General MIDI map is always available. Assigning a Drum Map to a track also causes the Drum Editor to be shown in the Editor tab of the project window’s lower zone whenever any of that track’s parts are selected.ĭrum Maps are assigned to a track in the top section of the Track Inspector – the field in question is located below the MIDI I/O routing selectors and has an icon that resembles a kick drum and beater. This tells Cubase the track is being used for drums, and so double-clicking parts on such a track will open the Drum Editor rather than the Key Editor. To open selected parts in the Drum Editor instead, we can use the MIDI > Open Drum Editor menu option, but a more streamlined approach is to assign a Drum Map to tracks that contain drum parts.
NI simply missed the chance to deliver Cubase (or other DAW) integration worth using to me like that, and to keep me as a customer, who has bought and enjoyed a lot of their stuff in recent years.By default, double-clicking on a MIDI part will open Cubase’s Key Editor, the classic piano-roll MIDI note editor common to all DAWs. I still enjoy a lot of my older NI content, but I do so within this great Cubase workflow now, making groove bulding a breeze: in every aspect, from using sample content over midi groove building up to seamless DAW midi integration and mixer routing. Now I am using Cubase 10 (my DAW of choice) with Groove Agent 5, since some days, and have completely abandoned Maschine and Battery, within these days, for a new and really much smarter workflow, miles ahead of anything the Cubase-Maschine/Battery combination has ever offered me. And then it's in my best interest to look for better alternatives, looking at what they have offered people like me so far, and what not. It's their right to develop Maschine however they want.
NI has simply more or less ignored Cubase (and other DAW) users, who were wishing to use a better integrated and stripped down Maschine version VSTi (without too much of a complicated NI Maschine sequencer overload plugin, wasting resources) in a DAW environment all this time. I've been trying to get a halfway decent Maschine workflow within Cubase patiently, for years.
0 kommentar(er)
