Console Inputs •
••
• 93
MIDI Map File Format
The console events that can generate MIDI and their map file name are listed below:
Whole Hog II HOG JandsHog Map file name
Choose buttons Choose buttons Select Buttons choose
Go buttons Go buttons Go buttons go
Halt buttons Halt buttons Halt buttons halt
Flash buttons Flash buttons Flash buttons flash
Faders Faders Faders fader (preceded by
value sent by
fader_val)
Tool buttons above
right hand lcd
Tool buttons Tool buttons rh_tool
Numeric keypad Numeric keypad Numeric keypad keypad
Parameter wheels Parameter wheels Parameter wheels wheel (preceded by
value sent by
wheel_val)
Next page button next_page
DBO button dbo
Release button release
Step up skip_up
Step down skip_down
Main stop main_stop
Main go main_go
Tool buttons above
left hand lcd
lh_tool
Touchpanels pressed touchpanel (preceded
by X and Y coords
sent by coord_x,
coord_y)
Fourth Menu Palette Group menu buttons group_menu (for all
menus, index 21 & 22
are the scrollup &
down keys)
Third Menu Palette Position menu
buttons
position_menu
Second Menu Palette Colour menu buttons colour_menu
First Menu Palette Beam menu buttons beam_menu
Macro menu buttons macro_menu
Page menu buttons page_menu
All other buttons All other buttons others
The following are
used to encode
continuous values,
and precede other
messages as listed
above:
coord_x
coord_y
fader_val
wheel_val
The possible MIDI messages that you can map to are:
Map file name Index Console events which can be mapped to
the MIDI event
note note number, eg, ‘note:34’ All button events
polyatouch note number, eg,
‘polyatouch:34’
All button events
controller controller number, ie, 1 > 32
[14 bit] & 65>128 [7 bit]
Value events
progchange program number All button events
pitchwheel none Value events
chanatouch none Value events