Seeking feedback: The "Default State"

[brad]

@Torsten

But overall, this would definitely help me clean up my bindings page quite a bit!

Good to hear. I’m still undecided on this but it’s the best idea I’ve got so far.

@Torsten

With the default state, I assume that I will first have to navigate from the current state I am working on to the default state, make the change and then go back to the state I am currently working on?

What I was thinking here was a new command “Update Default State”. This would snap shot all the non-state controlled settings into the default state.

@Torsten

behavior be that all changes not influenced by state behavior will automatically be reflected back to the default state and saved with it?

Possibly but I think an explicit command is better.

@Torsten

I’m interested in what your thinking is on the editing side…

I think the full set of UI changes will be:

1. a fixed “default” state at the top of the state list which will be editable/lockable like all other states, but excluded from state navigation (first/next/prev/etc…).
2. the default state wouldn’t have name/program number associated with it.
3. a new command Update Default State
4. a new command to Reload State which will load the merged state.
5. a new toggle setting on the rack slot in the parent song to control whether to reload or apply state changes when loading the selected state. (this setting will be state controllable)
6. two new context menu commands on selected behaviours (in the behaviours panel): Update and Update Default which will update just those settings in the current or default state (respectively)

Also, I’ve already made some changes to the main menu to consolidate all the state related commands:

Brad