steverosburg
Experienced
This is a piggyback off another thread, but I'll put in a separate formal "wish" request for it.
I know that when using non-Axe-Fx mode (or setting an IA to "NONE") that you can map 2 CC's to a single IA. I would like to do more, for example engage three effects (Drive 1, Amp 1 X/Y and Delay 1) and disengage another (Chorus 1), and do the reverse when disengaging. I know this is possible with external controllers, but they have problems of their own (LED states do not update to match, and you can't individually change the bypass state of an effect if it's bypass state is governed by an external controller).
I assume this would have the same inherent problem today as external controllers as far as the desire for IA LED's to reflect the current state of the Axe-Fx. There are separate wishes in for that.
oddb0d and javajunkie have discussed another solution involving multiple presets in non-Axe-Fx mode which do this kind of state management. I really don't want to lose Axe-Fx mode (one of the main reasons I bought the MFC), and I really don't want to have to manage multiple presets per song within the MFC. I know another approach would be to just copy presets within the Axe-Fx which only involve state change, and then leave the MFC in Axe-Fx mode, but that's such a waste of resources.
I know that when using non-Axe-Fx mode (or setting an IA to "NONE") that you can map 2 CC's to a single IA. I would like to do more, for example engage three effects (Drive 1, Amp 1 X/Y and Delay 1) and disengage another (Chorus 1), and do the reverse when disengaging. I know this is possible with external controllers, but they have problems of their own (LED states do not update to match, and you can't individually change the bypass state of an effect if it's bypass state is governed by an external controller).
I assume this would have the same inherent problem today as external controllers as far as the desire for IA LED's to reflect the current state of the Axe-Fx. There are separate wishes in for that.
oddb0d and javajunkie have discussed another solution involving multiple presets in non-Axe-Fx mode which do this kind of state management. I really don't want to lose Axe-Fx mode (one of the main reasons I bought the MFC), and I really don't want to have to manage multiple presets per song within the MFC. I know another approach would be to just copy presets within the Axe-Fx which only involve state change, and then leave the MFC in Axe-Fx mode, but that's such a waste of resources.