Useful?.. Oh yes!
I’m using your Baby gigging 3 times a week in different (rather complicate) configurations, and I face the need to toggle controller mapping for instance.
Let’s say you don’t have enough switches in your controller to control what you wish.
You would like to have a “control” switch or key which changes the “page” (mapping) of your switches.
This “page change” event would enable/disable the group of corresponding bindings and voilà!
Yes, for time being, you can embed this in a “controller” rack, memorizing binding group status in states with “page” event changing states (that’s what I’m doing now) but it is complicated to target VST’s which are in another rack.
You can even duplicate the main rack state to just memorize different status of bindings groups, but it becomes messy.
A binding being able to enable/disable groups (including it’s own group) would be a much smarter solution IMHO.
And this combined with the new “conditions”…hum!!
A kind of “bindings state” within the state!
Let’s dream even further, if I dare…
Multiline bindings with logical operators (i.e Cubase logical editor)