Overview
mTroll has special support for
Axe-Fx processors.
It includes a default
config.xml data file
that targets Axe-Fx processors.
When using mTroll with an Axe-Fx, first edit the
axefx.config.xml file
to make sure the channel specified in the
DeviceChannelMap matches the
channel of your Axe-Fx. Then open the file in mTroll.
Notes
These are my notes which need to be fleshed out. Check out the
axefx.config.xml data file for actual use.
Enhanced Axe-Fx support is dependent upon:
- Axe-Fx version 10 firmware
- a DeviceChannelMap mapping with device name "AxeFx" or "Axe-Fx"
- "AxeFx" device name being mapped to the same channel as your
actual Axe-Fx
- the use of that device name in defined patches (ie,
device="AxeFx" in the patch definition)
- Axe-Fx to mTroll sync support is dependent upon both MIDI in and out being
connected between mTroll and the Axe-Fx
new patch types:
AxeToggle and
AxeMomentary
- automatic conversion from
Toggle and
Momentary patch
types if
device specified in patch is "Axe-Fx" (continue to use
Toggle and
Momentary patch types if you use
use
device="AxeFx", otherwise use
AxeToggle and
AxeMomentary explicitly)
- effect block bypass CCs are automatically assigned to the Axe-Fx default
values if effect name is found (and cc is not explicitly specified)
- new attribute
singlestate="1" used to prevent automatic generation
of B group (for example, to use with Volume Increment and Volume Decrement
assignments in momentary patches - "Axe Volume Incremnt" in
config data file).
- new attribute
cc="x" to define the control change number (or
override the default) for a sync patch (required for use with Feedback Return
bypass assignment - see "Axe Fdbk Return" in
config data file).
- new attribute
invert="1" used to invert the A (127) and B (0) groups
that are automatically generated.
new patch type:
AxeFxTapTempo
- same as Momentary but switch LED syncs to specified Axe-Fx
device MIDI in port (assuming Axe-Fx unit is set to send realtime tempo sysex
to its MIDI out)
- no command strings are necessary (if not present, Axe-Fx default is used)
new metapatch:
SyncAxeFx
- forces a sync of the bypass state for all AxeToggle patches that
are mapped to Axe-Fx effect blocks
- use this command if you manually change presets on the Axe-Fx front panel to sync
up LEDs for effect blocks in mTroll
- automatically invoked after each program change when using interactive program
change engine mode on the channel specified by "AxeFx" device map
new patch command:
AxeProgramChange
- similar to ProgramChange but does patch name and effect block
sync after a 50ms pause
- supports program change numbers of 0-383 (via automatic bank select and program
number conversion)
- same as standard ProgramChange command + Sleep command
+ SyncAxeFx metapatch
- note that the Patches in the axefx.config.xml data file do not have names; When
AxeProgramChange command is invoked, a sync will occur and the name
of the Axe-Fx patch will be appended to the Main Display window automatically