I’ve created many threads over the past couple weeks specifically about MIDI, but I wanted to group them all together in one thread (as well as a couple others) because the summary of them together would be a potent update.
Sort of in topological order (but maybe importance as well?)
1.) Improve The MIDI Input/Output Selector
There are many times where ‘All MIDI Inputs’ is not an appropriate setting, but, more than one input might be needed.
With my current setup and projects, this is pretty much all the time.
It would be great if Steinberg gave us more of an advanced virtual MIDI Patchbay. I rely on my MOTU Clockworks software sometimes, but it’s dated and the UX is terrible… lacks basic modern GUI and HUI protocols. Cubase Input Transformer doesn’t really cut it in many ways.
click picture to enl…
2.) Need for Enable/Disable MIDI Chase per track
Sometimes a project contains four scenarios.
1.) I’m recording both the MIDI and Audio of a hardware synth
2.)I’m editing that MIDI and sending it back out to the synth, and re-recording the Audio
3.) I’m using the same synth for multiple layers of sounds, instrumentation and parts across multiple tracks.
4.) The Cubase project might contain completely different compositions/songs/ideas throughout the timeline.
the track list would look something like this:
3.) Event Names Obscuring Data Problem
I need/use event names quite a bit, but the fact they obscure data is a bit of a problem for both audio and MIDI.
Gif of problem
You can see once zoomed in I cut a note I could not see
requested solution, move/re-scale data down when Even Names enabled
Also, please separate Event Icons, from Event Names. When Event Names if off, the Event Icons (Time Stretch, ARA2, Shared Copy, e…
5.) Show Event Colour somewhere/better on Muted MIDI Events
I use a lot of colour coding for good takes, alright takes, needs edit, bad takes, etc.
It’s a bit of a problem that muted MIDI events do not show colour.
I tried the border and the baseline as separate solutions, but because of screen resolution, I thought the combination of them both was the best result.
muted audio events could also adopt this, as the colo…
6.) MIDI Track Edit Mode (Edit All Events in MIDI Editor)
This would be a simple but useful workflow enhancer.
My question to the current paradigm, is, why do we have to select events for them to show in the MIDI Editor Window?
It might be more efficient at some (if not all) stages of project to be able to just select the track and have all MIDI data (except for muted?) for that track show in the MIDI Editor.
This would be increasingly useful for advanced users who use the PLE to make instrument specific track selections. For example, a user could u…
7.) Need Logics style of MIDI Velocity Nodes
Apart from being easier to see in general when looking at a a succession of notes grouped closely together, or looking at a chord and the notes individual velocities - there is another aspect as to why this is very much needed in Cubase…
If a user has selected multiple MIDI parts across multiple MIDI tracks, for example, a Cello track, Violin Track, and Viola Track, so that they can be viewed and edited together in the MIDI Editor… there’s …
8.) MIDI Parts Selection Menu Should Mirror Colours of Parts
9.) Creative Skew/Transform Editing of MIDI Notes
Trying to edit the feel of a section of MIDI notes, one note at a time, can be very tedious, counter productive, and sometimes destructive.
It can be a difficult thing to try and slightly adjust the feel of something, so that it doesn’t lose its magic, but its timing is improved to mesh better with everything else.
Or perhaps, someone realizes that everything is too quantized and needs some humanity to it.
The LE can do some of these things, but using the LE isn’t always intuitive and the out…
10.) MIDI Part Versions (Like TrackVersions)
The explanation is that, on a film score… there can be hundreds of small changes to note selection, which could be misdirections. Each project is different, some film directors give insanely detailed musical and sound feedback down to the sound of the snare drum being used, some give no or barely any feedback at all.
The MIDI Part Versions are for the composer to try a bunch of different things to just a few beats of the audio in a few seconds of an entire composition.
This could stack up to b…
11.) Customizable Multi-Grid Grid Mode
It would be great for a user to be able to create a few customizable grids, capable of combining different grid types, and colour coding the grid lines.
This could be done within the current quantize panel, but it would be adapted so that, instead of focusing on only one length division, the user could add multiple length/quantize divisions.
Each division could have some options enabled or disabled separately:
-‘Snap Bypass On/Off’. Ie, someone might want to see the Triplet Grid as a guide, b…
12.) Multiple MIDI Channel Editing/Display
Say I have a dual channel synthesizer (Nord Wave) where, I might be controlling CC74 on Channel 1 and Channel 2 using an external controller like a Novation 25SL MKII, and I’m recording that MIDI to a single track in Cubase.
Currently, unless I’m not aware of it, there is no way to tweeze apart CC74 data on Channel 1 and Channel 2. It is instead summed into a sort of glitched out single Omni CC74 where Channel 1 and Channel 2 fought against one another.
My current workaround is to have two MID…
13.) MIDI Part Parts (Flocks) Like Audio Parts
The main reason I’m requesting this, is because of another feature request in which this would solve a protocol conundrum in that other feature request:
This could also just generally be useful in various situations, specifically, a good example would be recording multiple MIDI takes of a synth solo and comping the MIDI… it would be nice to contain all the edits and potential variations into a Audio Like Part.
The terminology would need to be worked out obviously… I’m not sure why MID…
**ADDITIONAL THREADS ALREADY OUT THERE**
Drum Map Improvements
Suggestion for Drum maps:
Show a dialog box before cubase deletes a map (Do you really want to delete this? because there’s no undo)
Ability to have global and local drum maps
Drum maps templates and ability to create a drum map from a template you pre-saved
Ability to drag pitches to organize them vertically Kick and then Snare may be drag the crash above the kick later
Ability to add and delete pitches to what you’re using only (and throw away the other octaves)
Multiple selection on pitches…
the drum map is a good tool for mapping midi ‘ins’ and ‘outs’ but it is limited to 127 notes (as if it is only one one channel),
It should act like normal midi tracks - you can have two midi events on the same note but can go to different channels.
Then you can have more than one drum VSTi in the drum map editor, each with its own range of 127 notes - instead of all of them sharing the same 127 note range. (you can have more than one VSTi at the moment but they cannot share the sam…
Add ability to delete rows (remove notes).
Add ability to play note values in via a keyboard.
Old school. This might even be before old school. Editing one line at a time…
[drum map editor]
It would be great to have an option to choose drum map in the in place editor. wouldn’t it be?
Or am I missing something in Expression Map Setup?
I want to set up Quick Controls output to external synth, assigning the appropriate CCs for what is dictated in the synths manual which are completely unrelated to what Cubase lists as CC message types.
Am I missing something somewhere?
VSTi parameter names really, should automatically relay to CC Lanes. This obviously would have to be a VSTi developer protocol.
It would be great to be able to rename CC’s in Note Expression (and Cubase in general) so as to indicate what parameter they control.
I use many CC xx (Control xx) controllers so being able to name them would help a lot.
When you have a list like the e.g. below it’s difficult to remember what’s what.
CC 54 (Control 54)
CC 55 (Control 55)
CC 56 (Control 56)
CC 57 (Control 57)
CC 58 (Control 58)
CC 59 (Control 59)
CC 60 (Control 60)
I like being able to show and hide various Midi CCs but I can’t figure out how to rename them which is a little annoying especially when trying to remember many of them all saying CC21, CC22, CC14, CC54, CC67 etc.
Being able to actually just give them a name (in the brackets), for example, CC21 (Vibrato) would be a huge step forward in Cubase’s Midi World.
There’s a couple threads about custom CC Maps already,
I want to create CC maps for all my analog synths.
To what extent this could be intertwined with expression maps, or be a completely separate interface/protocol, I’m not sure - but - It would be good if these proposed custom CC Maps could be selected within Expression Maps editing as well, thus showing up in the Expression Map ‘Output Mapping’ Controller menu.
Further, there could be an option for users per Expression Map, to display CC#+…
Getting deep into Expression Maps and Articulations at the moment,
I’m experimenting with using Expression Maps to also change parameters and settings on External Digital Synths using MIDI CC.
It’s actually working quite well, but I’ve realized the limitation is that the whole Expression Maps system is data-monophonic, ie, only one Articulation can be active at any given time.
It would be great if there was a 3rd Articulation type that can send a message even while another articulation is act…
This would speed things up considerably.
Select multiple Slots, and be able to add/edit Output Mappings
Slots that differentiated mappings, those mappings would show as grayed out and not editable (though maybe right click option to add to all selected)
Slots that have the same mappings, whether existing prior to multi-selection or added during multi-selection, show as not grayed out and can be edited as a group.
currently, ‘Tab’ goes to the right and cue ‘Articulation 1’ selection.
Ctrl+Tab or Ctrl+Enter or something, should go downward to the next slot name.
Expression Maps is something I’ve held out on for some time, just dug into it for the past week.
-Clear all Remote or Bypass Remote (Because the remotes block MIDI note input, and user may only be using Articulation Lane instead of Remote Triggers)
-Folders in the Expression Maps menus/search. (Folders auto-open to reveal user search matches)
-Expression Map Setup window needs better resizing capability - some column widths to narrow and obscure names.
-Duplicate Expression Map
Steinberg, please consider adding some basic useful features to setting up/maintaining Expression Maps that will go a long way to helping us save time and sanity.
In the Expression Map Setup window:
Please allow us to duplicate a map. A ‘Duplicate’ button would suffice.
Please let us reorder the maps in the list by drag & drop or at least sort alphabetically.
Please add some sort of indication whether a Map is in use in the project. This could be as simple as adding a little icon next to it, …