Add (missing) Midi Input device block

Until now, I have been using the bottom keyboard on MIDI channel 1 and the top keyboard on channel 2, relying on Omni MIDI Input Blocks to filter out unwanted channels.

I’ve learned that using Omni MIDI Input Blocks is not preferred, and I’m struggling to understand the Rig Manager.

I have set up MIDI device aliases (for example, BOTTOM and TOP keyboards), but when my controllers are not connected, I can’t select one of these aliases when adding a MIDI Input block.

So, when building my rackspaces, I need to have a MIDI keyboard connected to one of these aliases in order to add this input block in the wiring view. Is this correct?

I would expect that once I create an alias, I should be able to add it as a MIDI Input block, regardless of whether a physical controller is attached.

That way, I could build rackspaces without a physical controller connected and avoid having to change every Input Block afterward, instead using Rig Manager directly.

1 Like

You can build a rig with virtual MIDI, so you can build your rackspaces with the desired device aliases.
When you real keyboards are connected just switch the rig, dead easy

2 Likes

Thank you I have never used virtual midi, so I’m happy to hear about this solution!

See here: Hacks compilation - #3 by npudar

1 Like