Organise routes and bindings for pedals, switches, control surfaces?

[terrybritton]

Are you doing this abstraction as I outlined in this post, where I create a master rack which I then embed into another?

Workflow examples? Setup guidelines? Good practices?

I have done some more experimenting with this approach, using the MIDI Outputs customized to the rack and the rack’s bindings to send data to them. In so doing, I’ve discovered a couple cool things. So, let’s imagine a synth keyboard that has notes (duh), a sustain pedal, mod wheel, aftertouch and pitch bend. Let’s also imagine it has two knobs, one called “User 1” and the other called “User 2”. (My Kawai K5000s has such named knobs!) We might want to separate out the sustain pedal (and perhaps…

It was the only way I could keep my custom routes “permanent” while still allowing states to run things.

Terry