You might be able to do it if you can find an action like 'inport action list', and save multiple setups in separate files. I don't think cycle actions are going to help here.
It's likely you'd need a .lua script to make this work.
If it was a Midi controller, you could assign each setup to separate midi channels. For example:
Tracking task: All buttons/controls on midi channel 1, assigned to actions used for tracking.
Mastering task: The same buttons/controls, but sent on midi channel 2, assigned to different actions you use for mastering.
There are 16 midi channels, so you could have 14 more task-setups.
Changing tasks would just be a matter of changing which midi channel the controller sends. If your memory is as bad as mine, you'd probably need some sort of overlay template to remind you which button does what...
|