MIDI Control Aliases for all 88 keys?

Hey guys,

in some songs I use specific Note On or Note Off messages to control a widget. When I assign one key in the Widget Properties the specific device is assigned too.
Switching to another keyboard the widget doesn’t work even if I use the same Midi Device Alias for both keyboards.
Why isn’t it possible to choose a Midi Device Alias in the Editor of the MIDI message?

My workaround (in preparation for upcoming use cases) would be to define 88 MIDI Control Aliases for all keys and then assign one alias to the widget, but it would be kind of tedious to assign all keys on different keyboards and it would mess up the rig manager.

Is there a better way to do it?

Is there any issue with key ranges in the midi block?

So, perhaps the key where the widget assigned is not active (due to the key range selected in the MIDI IN Block) or maybe changed to a different note (due to transpose being applied)?

Just throwing this out there…

Jeff

No, all the sounds and split zones work fine on both keyboards. Also the defined Midi Control Aliases like Faders and Buttons work without problems using both keyboards.
The only exception are those widgets controlled by specific keys, because they depend on the specific device.
I’m looking for a kind of “Midi In OMNI” in the editor of the MIDI message in the Widget Properties.

Did you actually switch your rig via rig manager and associate the alias with the different controller?

I use the same rig configuration, but switch the associated MIDI device (Hammer 88 or the other keyboard) of my device alias “Main”.
But as you can see in the screenshot above, the Midi message is specified to Hammer 88 and not to an alias.

Even when it shows the old device, does it react on the actual device defined in the rig manager?

Did you define a MIDI control alias and assign that to the widget?

It only reacts to the shown device, not to an assigned device alias.

If I define a MIDI control alias to the specific key it works well when switching keyboards.

So anytime I want to use a widget controlled by a key in whatever use case, I have to define a MIDI control alias for the Note On and/or the Note Off message.
Continuing this workflow I may need for all 88 keys 2 MIDI control aliases, which leads to my initial question…

I know this workaround would work, but it is kind of messy to have 176 MIDI control aliases in the rig manager…
(Therefore a sort or filter function in the rig manager would be appreciated - as discussed here Sort / Rearrange MIDI Control Aliases in Rig Manager?)

This is not a workaround, this is how it is designed.
And do you really use 176 different note messages to drive widgets?

1 Like

That’s true.

There might still be another solution for your specific case, @ClaudioKrott:

Send the notes in the global rackspace to a port called “Local GP Port”.


In my example both the inputs “UM-1” and “Network Session 1” are merged to the GP Port. In your case these would be your different controller keyboards.

You can then learn your widgets to the desired messages coming from the GP Port and won’t ever need to change them when switching keyboards.
Even with this hack, it would be definitely worth to still use control aliases for this in the rig manager:

And please don’t ever use the OMNI MIDI In this case!

2 Likes

Thanks, this works well!

1 Like

Yes, you’re right!

Until now I didn’t use all keys to drive widgets, but in preparation I created all 176 control aliases. So when I learn a widget it automatically chooses the control aliases, and I don’t have to worry, that any widget wouldn’t work when I use another keyboard, because I forgot to create a control alias.

If anyone wants to use it, here is a .rigsetup with all 176 control aliases:
88 Keys as MIDI Control Aliases.zip (4.6 KB)

1 Like