zenaxe
Fractal Fanatic
Like many I am configuring a general MIDI controller for the Axe III. One thing I noticed that would really be a huge improvement is that if the 'BYPASS' page had a setting for specifying whether the switch was a 'momentary' or 'latching' switch.
The current implementation for controls on the bypass page only supports a latching MIDI CC. This is a problem because for a general MIDI controller, it has no way to query if the preset has the block you are toggling enabled or not.
So if the preset is loaded and the thing you are toggling (like drive or delay or whatever) is in a different state than the switch you have to switch the controller twice for each thing that is out of sync with the preset's state on the first change.
If your MIDI controller and the AxeFx III supported it, a momentary switch that toggles the bypass is much better because a foot press does what you expect after a program change no matter how the preset is written.
It seems this might be a small change but would make the Bypass function much more effective for folks with generic controllers that support a momentary CC. IMHO
The current implementation for controls on the bypass page only supports a latching MIDI CC. This is a problem because for a general MIDI controller, it has no way to query if the preset has the block you are toggling enabled or not.
So if the preset is loaded and the thing you are toggling (like drive or delay or whatever) is in a different state than the switch you have to switch the controller twice for each thing that is out of sync with the preset's state on the first change.
If your MIDI controller and the AxeFx III supported it, a momentary switch that toggles the bypass is much better because a foot press does what you expect after a program change no matter how the preset is written.
It seems this might be a small change but would make the Bypass function much more effective for folks with generic controllers that support a momentary CC. IMHO