Hi @Neil_Durant,
Funny you should bring this up…
I spent most of today thinking about exactly this kind of issue, including the locked state stuff I mentioned in the other post and also a more predicable initial state for racks used across multiple songs. Also, state reset/revert all falls into this category.
I’ve come up with a couple of solutions, but none particularly elegant so I’ve not implemented anything yet.
My favourite idea so far is to introduce a concept of a “default” state. Unlike other states that only affect selected behaviours, the default state would set the entire state of the rack and serve as a predicable and editable base for other states to be overlaid.
Your idea of updating the non-state controlled behaviours is interesting too… Let me think about it some more. I’m open to other ideas here if any one else has thoughts…
Brad