I love the Rig Manager in general and thought I understood the concept of it, but there is a certain behavior creating issues for me.
What I do a lot in my rackspaces is using “Note on” as a trigger for widgets (to activate/deactivate layers, transpose etc)
That way I´m able to control a lot of things right there where the action happens without moving my hand to knobs or sliders or using too many footswitches etc)
Now the issue I have is, that Rig Manager won´t replace all these triggers when I use a different Keyboard.
So I assume I would need to create Aliases for every single Key I´m using in all the rackspaces (which are a lot of different ones as I choose them based on scale and range I´m playing the specific song)
While I totally understand that it is necessary to create aliases for knobs, sliders, rotaries etc. which are different on every controller, I don´t understand why it´s necessary for the keys / Note on.
Wouldn´t it make a lot of sense to also replce these triggers automatically when using a different rig?
What about this situation:
2 Keyboards used.
For the upper Note messages are assigned to widgets
Now both Keaboards are replaced by different Keyboards.
How should the system check what device is now sending the Note messages which are assigned to widgets?
I think your suggestion leads to technical issues which are not present now.
Because it doesn´t behave like I would expect.
(I assume most people would expect like me that every Key would work after switching the Rig, no matter if you´re playing a VSTi or controlling a widget with your keys)
And yes, because it creates manual work (which is unnecessary from my point of view)
I don´t get your point here. I doesn´t matter how many keyboards you have here.
In Rig Manager you will assign a dedicated replacement unit to any missing hardware.
So GP knows exactly what to replace with which controller.
It´s exactly the same for your midi In Blocks.
Not really - because you’re not actually learning notes when you’re just receiving them in a MIDI In block and passing them on to a plugin.
This might actually not be a bad idea to consider. I wonder how many people really need this? I would think that people just require a few notes to be mapped - I have about 5 notes mapped because they get used in certain songs to trigger widgets.
So what is the advantage of “not considering” this kind of “learned” Midi Inputs?
Or the other way around what would be the disadvantage of considering these when switching Rigs?
Don’t know. I guess there is a benefit to the extent it is really easy to make a trigger note an alias instead of using midi learn. On the other hand, it is pretty easy to create an alias for each note in Rig Manager yourself. On the third hand, keyboard notes are all “pre-mapped” (C1, C2, etc), so maybe it make sense to have them pre-set in GP’s Rig Manager.
I guess if you are going to do that, maybe you want to nudge user to use that alias in Rig Manager instead of midi learn. Or I suppose if they are using midi learn, you could have a pop up: do you want to use the controller alias in the Rig Manager (if they have Rig Manager set up). But, that might create an entire other layer of complications.
Judgment call, I suppose. I am sure you guys have plenty on your plates.
Even if this isn´t used much right now, I´m sure more and more users will see the benefits and use it in future.
Mapping all these learned Midi Notes automatically would create a more consistent, predictable functionality from my point of view.
Because I did the mapping already in Rig Manager on Controller level.
When I need to create Aliases for every single learned Midi note, it´s a double mapping, isn´t it?
As said earlier I would expect a Rig Manager Alias Mapping to work on every note whether it is related to a Midi in block or a single learned note.
I´m not a programmer so I can´t comment on how difficult this is to implement.
And for sure there are more important things to implement.
So I´m confident you will make a good decision.
I´m just throwing my thoughts at you
