Hi,
I'm not sure I'm 100% following you but yes, if you close MT Pro when presets have changed within the program, MT Pro should prompt you if you want to save the file (if confirm is set in settings). Only if you save the file, will the current presets (that have changed) be active.
If confirm is not set, it should not save the project and when opened again, the original presets will be re-activated (based on the last program file save).
I think you need to decide whether the controller tells MT Pro what state it should be at startup (by pressing a button on a controller to set a global variable or change a preset), or whether you want MT Pro to assume a given state (by global variable).
You can also tell MT Pro which presets to activate/deactivate at project start. The technique is to use a timer and have various translators activate, or deactivate presets using the same incoming timer. You could also use the "Init" timer to do this.
There is an option to deactivate all other presets when a preset is activated. You can also define "always active" preset that are not effected by this so that you can have say one preset that is never de-activated and then select among a group of the rest of the presets by activating only the one you want (having the others automatically be deactivated).
In your situation, if your controller is smart enough, you can certainly have MT Pro query the controller and then have the controller response message set the desired state (using global variable or preset change).
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz