it would be nice to have the possibility of organizing bindings inside folders keeping track of extensive binding-setups. Maybe folders with own names and a switch to turn them on and off?!
And what I’m really missing is a possibility of multiple selection of different objects to change common values like state behaviors, common output/inputs, colours and so on.
The target of a binding is the thing upon which it acts. A binding inside a rack cannot target any plugins that aren’t in that rack. In other words, the rack defines the scope of access for the bindings inside.
There are many binding targets that are global in scope, such as Song. These targets are available in or out of racks. Specific plugin instances are not global in scope, however.
Bindings in racks inside the background rack don’t “see” the environment MIDI ports as input or output for bindings. So using embedded racks to structure my background rack unfortunately doesn’t work for most of my bindings there (unless I manually route the environment ports to those sub-racks via bindings or routes at the top level - which would somewhat defeat the point of simplification…).