X32 Midi Implementation - Behringer X32 User Manual

70
X32 COMPACT DIGITAL MIXER User Manual

X32 MIDI Implementation

MIDI RX > SCENES
Whenever program change messages in the range 1-100 are received on MIDI
CH01, the corresponding scene of the X32 internal show memory will be loaded.
This requires the following preconditions:
Setup / remote
> MIDI In/Out check marks must be set according to the connection on
which MIDI input will be accepted (via physical MIDI connectors on X32 or
S16, or via XUF Card)
> MIDI In/Out check mark must be set for "Enable MIDI Scene Recall"
Setup / global
> when tick mark "Con rm Pop-Ups" / "Scene Load" is active, also MIDI
scene recalls will only become active after manual con rmation
> if you prefer activating scenes via MIDI program changes immediately,
un-check the "Con rm Pop-Ups" / "Scene Load" tick mark
Scenes View / home
> valid scenes must be stored in the internal X32 show le. It is not possible
to recall empty scenes.
> the scope of changes applied by a MIDI scene recall depends on the Scene
Safes, Parameter Safes and Channel Safes settings, same as with recalling
the scene locally.
MIDI TX > SCENES
Every scene can be assigned one speci c MIDI command/event. Each time the
scene is loaded the MIDI command will be sent out once. Possible choices for MIDI
commands/events to be found on Scenes View/MIDI page:
O > no message will be sent upon scene load
Program Change > select the MIDI Channel and the Program Number
(using knobs 4/5 at the main display)
Control Change > select the MIDI Channel, Controller number and value
(using knobs 4-6 at the main display)
Note > select the MIDI Channel, Note number and velocity (using knobs 4-6
at the main display) > will send out a Note On command directly followed by
the same Note O command
MIDI RX > ASSIGN
Whenever assignable controls are set up for transmitting MIDI commands,
reception of that same command (status or continuous) will be re ected on the
respective assignable control element (button light, encoder LED collar).
MIDI TX > ASSIGN
We restricted the user assignable MIDI commands to some generic elements,
in order to keep things simple enough:
Encoders 1-4 > can be assigned to sending control changes, program
changes or notes
> parameters are currently 'Channel' and 'Value'
> for CC and Note commands 'Value' = controller number/note number,
and the encoder rotation determines the controller value/note-on velocity
> for Program Changes only the channel is speci ed, and the encoder
rotation determines the program number
Buttons 5-12 > can be operated in two modes, 'MIDI Push' (non-latching)
for momentary commands, or 'MIDI Toggle' (latching) for static commands
MIDI Push:
> can be assigned to sending control changes, program changes or notes
> parameters are currently 'Channel' and 'Value'
> for CC and Note commands 'Value' 0...127 = controller number/note
number, and the button momentarily toggles the controller value/note-on
velocity to 127 (depressed)à0 (released]
> for Program Changes 'Value' 0...127 = program/preset number, that will
be sent upon pressing the button
MIDI Toggle:
> can be assigned to sending control changes or notes
> parameters are currently 'Channel' and 'Value'
> for CC and Note commands 'Value' 0...127 = controller number/note
number, and the button toggles the controller value/note-on velocity
between value/velocity 127 and 0 with every operation
n.b.1) The ASSIGN section also re ects/displays reception of the same MIDI
commands that are selected for transmission
n.b.2) The MIDI commands assigned to the ASSIGN controls can be
transferred to and from stage via AES50 using the S16 stage box MIDI I/O