Cool, but I have only two hands. I don’t see any practical use or necessity for this. Mind though, I am a ‘One man’ ensemble. But even with more than one musician I am curious about the scenario/workflow/setup that requires Multiple Midi-inputs per track ‘filter’ to avoid the ‘All Midi’ inputs.
Anyhow, cheers!
@Fantom here is an example why I want this feature, even as a one-man-group.
Thats only 5 Midi ports; I can imagine of even more, since I have 2 Fader-devices, one small and one 88key large keyboard, breath controller and some software ports for manipulating midi data (Bome)
Steinberg - please deliver!
OK, you’ve got a bunch of keyboards & controllers. Based on your description it sounds like they are all used to control different things. But without describing your desired routing it’s not clear why this would or wouldn’t work within the current restrictions. It’s not the total number of controllers that causes problems. The limitation occurs when you want to aggregate them in various combinations.
Exactly - a Cubase internal solution like BOME MIDI TRANSLATOR would be perfect
I think it’s more about per situation/session/project adaptation, ie, temporary templates on a per basis case. It’s not just about simultaneous use of two controllers, but bouncing around multiple setups or stations in someones studio.
One person gave the example of using their 88 key as a drum sound browser, while using their 4x4 pad for performance… ie two controllers to one MIDI track input.
But they may lay down a track using that setup, and then want to jump to a synth station across the room that needs to be configured a certain way.
To have to be jumping into MIDI preferences and disabling/enabling individual inputs is obviously not efficient nor musically seamless which should be the objective.
Yes checking check boxes isn’t all that musical either, but it’s still faster than the suggested workarounds, and if they also created MIDI Input presets, this would make it even faster for users to select common configurations they use.
I was just recently inquiring about something related with the DIVISIMATE guys… I would love to be able to play the melody unchained with my top keyboard while playing chords using DIVISIMATE with the 2nd bottom one.
Unfortunately, this is currently not possible. a) DIVISIMATE does not differentiate between channels and b) Cubase does not allow ad-hoc re-routing of specific input channels.
Initially, I thought there would be a simple workaround: create an empty MIDI channel, point the input of the keyboard to it and route it to the targeted track when needed. But Cubase currently (15) does not allow us to do even this…
Obviously, a direct way to quickly engage and disengage specific inputs, rather than an “all or nothing”, for a MIDI track in question would be even better.