Customizable/multiple MIDI Inputs per Track, instead of only One or All

It seems this shouldn’t be hard to do? Why are we confined to All or One in 2026?

  • There are/can be conflicts with ‘All MIDI Inputs’ for complex setups when dealing with per-day/per-project needs.
  • Having to depend on 3rd party MIDI patchbays, Input Transformer scripts, etc is too cumbersome.

Please allow us to choose individual MIDI Inputs per-track.

Sometimes I have a huge library of drum oneshots I am sifting through to find sounds, and I want my studio controllers focused there - drumpad, 88 key keyboard, etc - but I might not want all my MIDI devices focused there (synths).

Some of my controllers even have dual MIDI out which I have incorporated into my setup and thus can result in double note trigger.

Yes I can use Input Transformer, MIDI Channel filtration, I have a hardware MIDI patchbay with software control… But it’s all so much more complicated to do that, than to just select the inputs I want in Cubase at the time that I need them.

There’s parts of my setup on the backend that I want to keep fairly static and refrain from changing.

(Cubase 9, 2018)
pick and choose midi input routing - Cubase - Steinberg Forums

@Raino had a good point in the above thread, but sometimes I need All to be All.

(Cubase 10, 2019)
Is it possible to have two midi inputs to one track? (Solved) - Cubase - Steinberg Forums

(Cubase 10, 2020)
Selecting Multiple MIDI Inputs - Cubase - Steinberg Forums

Would it really be that much work for Steinberg development to give us a checkbox menu for MIDI inputs? I have no idea.

Hi,

I would go the ‘All MIDI Inputs’ way. Changing the seeing takes probably add long as choosing dedicated MIDI Ports in a new MIDI Input Ports selector window.

Sorry I’m not fully understanding what you’re saying.

There are/can be conflicts with ‘All MIDI Inputs’ for complex setups when dealing with per-day/per-project needs.

Hi,

OK, so you want to keep it somehow persistent per project/track or even to be able to make presets, right?

I would recommend you to write a proper feature request out of it.

What would make it more proper in your opinion?