I wonder if this could be generalized as "control objects should optionally store their state on exit, and load that state on startup" as a way of persisting UI state between sessions. I suspect this is a Hard Problem but it would be nice to have a generic solution to this kind of issue.
> control objects should optionally store their state on exit
This is a tricky to solve. IIRC some controls are not saved because they're not necessarily visible/obvious in the GUI and may create issues when they're not in the default start after startup, like decks' crossfader orientation for example, or quantize, or master Fx routing.
I wonder if this could be generalized as "control objects should optionally store their state on exit, and load that state on startup" as a way of persisting UI state between sessions. I suspect this is a Hard Problem but it would be nice to have a generic solution to this kind of issue.