An Update. I’ve abstracted my keyboards into racks and have Notes coming out from that rack into the VSTs.
Next, I want to look at faders, buttons, footswitches and pedals.
I think Torsten has his set up with abstraction based around physical hardware. eg. one or more intermediate racks and then the VSTs are connected or bound to that intermediate rack. The lines represent bindings and/or routes. Like this
I wonder whether there is any benefit in abstracting based around Functions as an alternative. For example building intermediate racks for a Piano, Organ, Audio Routing, Lighting Desk etc.
All of these racks would then be added to the song.
So the “Virtual Piano 1” rack would bring Notes from physical keyboard 1, Pedals from “physical keyboard 1”, String Resonance or dynamics slider from “Nano Key fader” The combined output of this rack would then go to the instrument rack containing the Piano VSTs.
The problems I am thinking about are easy ways to answer:-
- What have I mapped to this hardware button/fader?
- What have I mapped to this software function eg. “Next Song State”?
- How can I quickly repurpose this “NanoKey” which currently has faders mapped to functions across lots of different VSTs and C3 itself?
For the 3rd question, I might temporarily want to assign all the faders to be lighting controllers, It would be nice to just disable a rack with the existing config, and drop in a new “Lighting desk rack”.
I suspect this is all over complication, but it is going to take some effort to redo my songs and I’d rather get all the thinking out of the way before I do!
Any thoughts appreciated.