Professional Documents
Culture Documents
Version 3.0
Validated against Firmware 2.70
Contents
Basic information ............................................................................................................................................................ 2
Quick facts on Helix:..................................................................................................................................................... 2
Helpful Resources: ....................................................................................................................................................... 2
Global Settings ................................................................................................................................................................ 3
Incoming MIDI Messages ................................................................................................................................................ 4
Predefined MIDI Commands: ....................................................................................................................................... 4
Setlist, Preset and Snapshot Recall ........................................................................................................................... 4
Emulating footswitches and Expression pedals ......................................................................................................... 5
Looper Controls........................................................................................................................................................ 6
MIDI clock (receive) .................................................................................................................................................. 7
Custom MIDI Command Assignments:.......................................................................................................................... 7
Controlling Block Bypass States ................................................................................................................................ 7
Controlling Block Parameters ................................................................................................................................... 7
Outgoing MIDI Messages ................................................................................................................................................ 8
Default MIDI Messages When Recalling Presets ........................................................................................................... 8
Command Center (not available on HX Stomp) ............................................................................................................. 9
Overview.................................................................................................................................................................. 9
Screen Layout........................................................................................................................................................... 9
Instant Commands ................................................................................................................................................... 9
Footswitch Commands ............................................................................................................................................12
Expression Pedals ....................................................................................................................................................13
Variax knobs............................................................................................................................................................14
Expression Pedal toe switch ....................................................................................................................................14
MIDI clock (send) ........................................................................................................................................................14
MIDI Thru....................................................................................................................................................................14
Other Key Details ...........................................................................................................................................................15
Checking Firmware Version .........................................................................................................................................15
Creating a MIDI Loopback Connection .........................................................................................................................15
MIDI message order ....................................................................................................................................................15
Command Center Snapshot Assignment Issue .............................................................................................................16
MIDI CC Quick Reference Chart .......................................................................................................................................17
Typical commands are Program Change (PC) messages, Control Change (CC) messages, and Note on/off
messages. These commands would then have {values} associated to the message for further control.
MIDI Clock is another common type of MIDI message. MIDI Clock is a constant stream of tempo information,
which can be used to synchronize multiple devices to the same BPM.
Some devices are very programmable, where the user can define what a MIDI message will cause to happen
when received; As well as define what message will be sent when a button/switch/knob/expression pedal is
operated. Other devices are more limited, where the MIDI messages are pre-set, in terms of what will happen
when a particular message is received; As well as what message is sent when a button/switch/knob/expression
pedal is operated. Helix devices have both pre-set commands, as well as user programmable commands.
A MIDI network uses a standardized 5-pin DIN connector and cables, or USB; and most recently, Bluetooth MIDI
devices have started to become popular for wireless MIDI communication.
Helpful Resources:
o Helix User’s Manuals
o Software & Firmware Downloads
o General MIDI Information
o Troubleshooting Tools:
The iOS “MIDI Wrench” app, running on an iOS device which is connected to the Helix using the
Apple Camera Connector Kit adapter, can be very helpful when troubleshooting MIDI issues, as
it allows you to see all MIDI messages coming in and out of the iOS device.
Equally good for troubleshooting is the “MIDI-OX” tool running on a PC. This also enables you to
see all MIDI messages being sent by the Helix, but also provides a control panel to send MIDI
messages back to the Helix. This can be very helpful for testing configurations.
The “Global Settings” – “MIDI/Tempo” screen is where the remaining MIDI settings are found
Incoming messages must be sent to the Helix’s “MIDI Base Channel”, for the Helix to process the commands.
This is done by configuring the MIDI command on the sending device.
For example: If the Helix is set for “MIDI Base Channel 7”, then the sending device should be configured to send
messages on Channel 7 for the Helix to process. This is not the same as the sending device’s MIDI base channel.
Each device on the MIDI network should have its own unique channel assigned, unless you want more than one
device to respond to the same messages.
You can recall a specific preset, and snapshot within that preset, by sending three MIDI commands
to the Helix. One is for setlist selection, one is for preset recall, and the 3rd is for snapshot recall. It’s
important to send the messages in that order, as they are processed as they are received. For
example: If you send a snapshot message 1st, followed by a preset message … the Helix will recall
the snapshot on the current preset, then recall the new preset afterward. This will cause the new
preset to be loaded with whatever snapshot was selected when the new preset was last saved.
All three of these commands can also be used independently as well. For example: If you just want
to change snapshots of the current preset, you can just send the snapshot MIDI CC command
without a setlist or a preset command.
As another point to consider: If you don’t send the snapshot command, the preset will load with
whatever snapshot was active when that preset was last saved. So if your presets already have the
starting snapshot you prefer, then there is no need to send the snapshot CC command in addition to
the preset PC command.
This can be beneficial if you want to automate activation of the Helix footswitches and EXP
pedals from a computer, an iOS device, or a MIDI controller.
In all three expression pedal messages, the value sent relates to the position of the pedal.
Where a value of 0 relates to 100% heel down, and a value of 127 relates to 100% toe down.
Footswitch Emulation:
Footswitch emulation commands only function against the “Stomp” footswitches. If the
Helix is in “Snapshot” or “Preset” mode, sending these CC commands will toggle the
“Stomp” footswitch even though the stomps are not being displayed on the Helix.
CC49{value} though CC53{value} commands will toggle the state of the Helix’s 1-5 stomp
footswitches.
o CC49 will control footswitch 1 …. CC53 controls footswitch 5
CC54{value} through CC58{value} commands will toggle the state of the Helix’s 7-11
stomp footswitches
o CC54 will control footswitch 7 …. CC58 controls footswitch 11
The value here isn’t important, as any value will simply toggle the footswitch’s state; just
like stepping on the footswitch with your foot.
There is no discrete MIDI command function for a footswitch’s on/off state; this means
you cannot send a footswitch “on” or “off” command, as any command sent on these
CC numbers will always toggle the footswitch to the alternate state.
Tuner toggle
A CC68{value} command, sent with any value between 0 – 127, will toggle the Helix
tuner on/off
Tap Tempo
A CC64{value} command, sent with any value between 0 – 127 will emulate the TAP
footswitch being pressed a single time.
The Helix looper can be controlled with MIDI commands as well. This works by triggering the
Looper’s controls with specific MIDI CC commands. These commands work for both the “1 Switch
Looper” and the “6 Switch Looper”.
The Looper mode does not need to be entered on the Helix to control the Looper functions with
MIDI. So an external MIDI controller can be connected, and MIDI commands configured on it, to
enable Helix Looper control without ever accessing the Looper mode on the Helix directly.
This means the Helix footswitches can continue to display Presets, Snapshots, and/or Stomps while
the Looper is being controlled though MIDI.
The Helix BPM can be controlled by external MIDI clock messages, or by the TAP Tempo
functionality. The Helix cannot receive a CC or a PC message to set tempo to a specified value.
In global setting, the “Receive MIDI Clock” setting can be set to Off, USB, MIDI, or Auto. When set to
something other than “Off”, and a MIDI Clock signal is detected on that connection, the Helix will
change its tempo to match the signal being received.
The TAP LED on the Helix will flash blue instead of red
The BPM no longer displays in the Tempo screen’s “BPM” parameter, but instead will show
“External”. You can access the Tempo screen by quickly touching the TAP/Tuner footswitch.
You cannot tap in an alternate BPM by tapping on the TAP footswitch, as the BPM will be locked
to the external MIDI clock signal
NOTE: You cannot assign CC numbers which are used in the predefined commands, to be used as
custom commands. For example: Because CC64 is used to emulate the TAP footswitch, CC64 is not
available for custom assignments to other functions.
Outgoing messages are configured with a MIDI channel for the message to be sent across. If the outgoing
message is configured for channel “Base”, it means the message will be sent on the MIDI channel currently
selected in “Global Settings” for the “MIDI Base Channel” parameter.
Each device on the MIDI network should have its own unique channel assigned, unless you want more than one
device to respond to messages being sent. So when configuring Helix outgoing MIDI messages, you should
choose the MIDI channel of the receiving device.
Recalling a preset that doesn’t have a Looper block in the signal path, will also cause a CC61{0} message
to be sent, which is the Looper’s stop command.
These default messages are sent out on whatever channel is set for the Helix’s “MIDI Base Channel” in
“Global Settings”, and cannot be changed to send on a different channel.
These default messages are only sent when the “MIDI PC Send” setting within Global Settings is set to
something other than “Off”. It can be set to USB, MIDI, or Both. When set to MIDI, these default
messages are sent over the 5-pin DIN connector only. When set to USB, these default messages are sent
over the USB only, and when set to both, these default messages are sent over both the USB and the 5-
pin DIN connector.
Note that these default MIDI message are the only place in the Helix where you can configure a MIDI
message to be sent on only USB or only the 5-pin MIDI DIN connector. In all other cases where MIDI is
sent out of the Helix, it will always go over both connection types, assuming “MIDI Over USB” is turned
on in “Global Settings”.
This is important to know if you have one MIDI device connected VIA USB, and a 2nd MIDI device
connected VIA the 5-pin DIN connector, and you only want PC messages sent to one of those devices
upon preset recall. These default messages are the only way to accomplish doing this.
When viewing the Command Center screen, a small “Triangle” icon shown above any of the
items indicates a command assignment has been made on that item.
The Command Center is entered by pressing the [Menu] button on the Helix, then pressing
down on the 3nd encoder knob, labeled “Command Center”.
Screen Layout
Once entered, the Command Center screen will show various items to which commands can be
assigned. The top row shows 6 lightning bolts, which represent “Instant Commands”.
Below the Instant Commands are two rows of 6 footswitches. These represent the 12
footswitches on the Helix.
To the right of the Instant Commands, is another footswitch. This represents the integrated
expression pedal’s toe switch, which is activated by pressing hard on the toe end of the
integrated expression pedal.
Also on the screen are three expression pedals. They represent expression pedals 1, 2 and 3
(from left to right).
Lastly, there are two knobs above expression pedals 2 and 3. These knobs represent Variax
control knobs found on Variax guitars, and can only be utilized if you have a Variax guitar
connected VIA the “Variax Input” jack on the back of the Helix.
When Presets are recalled, all assigned Instant Commands will be sent.
When Snapshots are recalled, all, some, or none of the Instant Commands may be sent;
depending on the configuration of the commands.
Reselecting the currently active Preset will retrigger the Instant Commands to be sent,
just as when the preset is initially recalled.
From a timing perspective, the Helix sends Instant Commands in order from left to right. So if
the order of commands is important to the receiving device, be sure to assign them in Command
Center accordingly.
To setup an Instant Command, access the Command Center screen and use the Helix joystick to
select one of the lightning bolt icons, then use the encoder knobs to configure the MIDI
command to be assigned.
MIDI CC
o Upon preset recall, the configured CC MIDI message will always be sent
o Upon snapshot recall, the configured CC MIDI message will only be sent if the
snapshot being recalled has a different value than the currently active snapshot
o The CC value can be changed across snapshots, but the CC number itself cannot
o Upon preset recall, the configured PC MIDI message will always be sent
o Upon snapshot recall, the configured PC MIDI message will only be sent if the
snapshot being recalled has a different value than the currently active snapshot.
The exception to this is if the “Duplicate PC Send” option in Global Settings is
turned “On”. In that case, the PC message will be sent when changing
snapshots, even if the PC value isn’t different between the 2 snapshots.
o Note this MIDI message has more than just a “Program” (or PC) parameter
available. In addition to encoder #4 (where the PC’s {value} is set) it also shows
two additional parameters of “Bank CC00” and “Bank CC32”. These are specific
to Bank and Program change message which some MIDI devices require to
successfully execute a bank or program change over MIDI. Without getting into
too much detail, the CC00 command represents the MSB (Most Significant Bit)
message for the bank change, and the CC32 command represents the LSB (Least
Significant Bit) message for the bank change. In many cases, these two
parameters can be left “Off”, but may need specific values depending on the
receiving device’s requirements.
MMC
o An MMC message is a “MIDI Machine Control” message. It’s typically used to
control playback of a DAW or external looper (ie: transport control).
o It sends out a predefined “Transport Control” message for the command.
o The available MMC messages are: Stop, Play, Forward, Rewind, and Pause
Ext Amp
o This command doesn’t actually send any MIDI messages out, but is used to
control the signal on the “EXT AMP” connection on the back of the Helix.
o The “EXT AMP” connection can be used to control amplifiers, or other devices,
where a ¼” signal cable is used to trigger specific functions. For example, trigger
the tremolo circuit on a tremolo equipped amplifier, or trigger a function on an
external pedal that supports expansion foot switches over ¼”, etc …
CV Out
o Like the “Ext Amp” command, the “CV Out” command also does not send any
MIDI messages out, but is used to control the “CV” connection on the back of
the Helix.
o The “CV” connection can be used to control devices which have a ¼” expression
pedal input jack. It’s essentially a simulated expression pedal. The “CV Out”
message type in Command Center is then used to define the simulated
expression pedal’s position.
o The “CV Value” parameter on the “CV Out” command relates to the position of
the simulated expression pedal.
Note that MIDI command types: “CV toggle”, “Note on”, and “CC Toggle” are NOT
available for assignment as Instant Commands, but ARE available for assignment to the
footswitch icons.
So if a MIDI CC command is assigned to Instant Command #1, and CC#4 is chosen … it must
remain as a MIDI CC#4 command for all snapshots within the preset, although the value of the
CC#4 command can be changed per snapshot.
When changing snapshots in a preset where Instant Commands have been configured, only the
Instant Commands where the value is changing due to being set differently in both snapshots,
will be sent out of the Helix when the snapshot is recalled. The only exception to this are PC
messages, when the “Duplicate PC Send” option is turned on in Global Settings.
To configure different values between snapshots, simply change the value parameter in the
MIDI message, and then be sure the snapshot is saved. There is no need to press down on the
encoder knob to do this, and brackets [ ] will not appear around the value like they do when a
parameter is assigned to a snapshot controller.
It’s important to know how the “Snapshot Edits” setting in Global Settings is set when
configuring Instant Commands for snapshot control.
If “Snapshot Edits” is set to “Recall”, then any changes made to Instant Command
parameters will be automatically saved for the currently loaded snapshot.
If “Snapshot Edits” is set to “Discard”, then the [Save] button on the helix must be
pressed twice, to save the preset, and for the changes to be saved on the snapshot.
To remove Instant Commands assignments, change the “Command” parameter to “none” and
ensure the preset is saved. Things can quickly become confusing if you have different values
across different snapshots. So if things start acting strange or unpredictable, clear the Instant
Command by selecting “None”, then save the preset, and start over.
If an Instant Command is setup to change values between two snapshots, but not the other 6:
Then when changing to a snapshot where a value has not been defined, the screen will continue
to show the last value which was sent, and the MIDI Instant Command message will not be
resent.
It’s important to note that Footswitch Command assignments in Command Center will not be
sent if the footswitch the command is assigned to is in Snapshot mode. So if a footswitch is
displaying “Snapshot #”, and a command is assigned to that footswitch in Command Center, the
command will not be sent when that footswitch is pressed.
Footswitch Commands can be assigned to all 12 footswitches, and will be sent when the
footswitch is activated, in all cases, other than when the footswitch is in Snapshot mode. Even
the “Mode”, “Tap”, “Bank ^” and “Bank v” footswitch can have MIDI commands assigned to
them in the Command Center.
Most other features of Footswitch Command Center assignments are the same as Instant
Commands, in that the values of the commands can be customized per snapshot, and the
“Snapshot Edits” setting within Global Settings impacts if the changes must be saved before
changing to another Snapshot. Even the state of the footswitch itself can be saved on a per-
snapshot basis.
To setup a Footswitch Command, access the Command Center screen and use the Helix joystick
to select one of the 12 footswitches, then use the encoder knobs to configure the MIDI
command to be assigned.
Available MIDI messages for Footswitch assignment are the same as Instant Commands, but also
include three additional types:
CV Toggle
o Like the “CV Out” command, the “CV Toggle” command does not send any MIDI
messages out, but is used to control the “CV” connection on the back of the
Helix. The “CV Toggle” command type is used to toggle the value of a CV
command back and forth, with each press of the footswitch.
o The “CV” connection can be used to control devices which have a ¼” expression
pedal input jack. It essentially simulates an expression pedal. The “CV Toggle”
message type in Command Center can then used to define the simulated
expression pedal’s position.
o The “Dim Value” and “Lit Value” parameters on the “CV Toggle” command
relate to the position of the simulated expression pedal when the assigned
footswitch is Lit and when it is not Lit (or is Dim).
Note On
o The “Note On” command can be used to send MIDI note messages.
o This is useful when controlling a software instrument on a remote device.
Expression Pedals
The three expression pedals in the Command Center relate to EXP 1, EXP 2, and EXP 3. When
assignments are made to these, the messages will be sent when the expression pedals are
activated.
EXP 1 and EXP 2 can be controlled using the integrated expression pedal, and switching between
the two is done by activating the expression pedal’s toe switch. As an alternative, an external
pedal can be plugged into the EXP 2 jack on the back of the Helix for controlling Expression
Pedal 2.
EXP 3 can only be controlled by utilizing an external expression pedal plugged into the EXP 3 jack
on the back of the Helix.
Unlike Instant Commands and Footswitch Commands, the values set to Expression Pedal
Commands within the Command Center cannot be different between snapshots.
MIDI CC
o Will send a range of MIDI CC messages when the expression pedal is operated
CV Out
o Will send a range of CV messages, through the CV connection on the back of the
Helix, when the expression pedal is operated.
Variax knobs
There are two Variax Knob Controllers in the Command Center. One is the Variax volume knob,
and the other is the Variax tone knob. These operate just like the expression pedals, and have
the same commands available.
Like the Expression Pedal Controllers, the Variax Knob Controllers also cannot have different
values for different snapshots.
The Helix can send the tempo/BPM signal out regardless on how the Helix is setting BPM. Regardless if
it’s set for global, or per preset, or per snapshot, or if it’s receiving Global Clock from an external device
over MIDI …. the Helix can still pass MIDI Clock to other MIDI devices.
For example, the Helix could be connected to a computer or an iOS device over USB, and receive MIDI
clock through this connection. Then the Helix could pass the MIDI Clock signal it is receiving over USB,
to other devices over the 5-pin DIN connection.
MIDI Thru
Since MIDI is a network of devices, sometimes devices will be daisy chained together. This means not all
messages being sent over the network are intended for every device on the network. The Helix has the
ability to pick up and process the messages intended for it, but also pass all MIDI traffic through to other
devices.
For example: If the Helix is connected to a computer running a DAW, over USB, and that DAW needs to
send messages to the Helix and a keyboard; the keyboard could be connected to the Helix’s MIDI
“Out/Thru” 5-pin DIN connector, and the “MIDI Thru” option switched on.
Even though the Helix and the keyboard would have different MIDI channels assigned to them, the DAW
on the computer could send messages to the keyboard, by having them pass through the Helix.
When creating this loopback type connection, it is important to configure Global Settings in such a way
where an endless loop of MIDI commands does not happen. If this does happen, the Helix will appear to
freeze up, and none of the footswitches, knobs or buttons will function; although sound will continue to
pass through.
If this endless loop does occur, simply unplugging one end of the MIDI cable from the back of the Helix
will resolve the frozen condition.
When using a MIDI loopback setup, The Global Settings should be configured as follows to prevent the
endless loop scenario:
“MIDI Thru”
o This should be switched “Off”
“Receive MIDI Clock”
o This should be switched “Off”, or set to “USB”, but not to “MIDI” or “Auto”.
“Send MIDI Clock”
o This should be switched “Off”, or set to “USB”, but not to “MIDI” or “MIDI+USB”.
“MIDI PC Receive”
o This should be switched “Off”, or set to “USB”, but not to “MIDI” or “MIDI+USB”.
“MIDI PC Send”
o This should be switched “Off”, or set to “USB”, but not to “MIDI” or “MIDI+USB”.
When a preset is recalled, MIDI messages are sent in the following sequence:
So if you are relying on the default PC messages to change an external device’s bank, and then
also have Command Center commands established in your presets; Those Command Center
commands will not be sent to the bank being recalled on the external device, but will be sent
prior to the bank being recalled. To work around this, turn the “MIDI PC Send” option off in
Global Settings, and then use the very 1st Instant Command to send the PC “Bank Change”
message to the external device.
Firmware 2.60 changed the order of MIDI messages to be more logical, where the default MIDI
messages which are sent when a Preset is recalled, are now sent out 1st, followed by any
Command Center messages second. This solves synchronization issues when trying to align
Helix Presets with an external device’s bank selection with MIDI commands.
Within the Command Center, on firmware 2.54 (and maybe previous), there is an issue where Instant
Command assignments, which have varying values across snapshots, will all change to the same value
under a particular circumstance. This happens when a new Instant Command is selected for the same
command which has already been setup on a different Instant Command
For example: If you setup Instant Command #1 with a CC10 command, and assign value of 10 for
snapshot 1, a value of 20 for snapshot 2, and a value of 30 for snapshot 3; and then save the preset.
After doing this, a CC10 command will be sent by Instant Command #1 when you select snapshots 1, 2
or 3; and the value of the command will be 10, 20 or 30, depending on which snapshot is selected.
The issue arises if you then go to a new Instant Command, and simply scroll the encoder knob to select a
command for CC10. Even if you don’t save the preset, but just scroll the encoder to display CC10, the
issue occurs. What happens is the previously configured CC10 command for snapshots 1, 2, and 3 will
all be changed to have the same value and will lose the snapshot values 10,20 and 30 which were
assigned to them.
To fix this, the user must go back and set the snapshot assignments again for the Instant Command.