Behringer Digital Mixer X32, X32 CORE, X32 COMPACT-TP, X32 RACK, X32-TP Protocol Manual

X32 MIDI Implementation (06 May 2014)

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

music-group.com behringer.com

1

PERMANENT MIDI ASSIGNMENTS OVERVIEW (REMOTE OFF)

MIDI RX Midi Ch Controller Value Comment

Scenes

Snippet 2 Program Change 1-100

Cue 3-6 Program Change 0-127 Ch3 -> Cue 1-127, Ch4 -> Cue 128-255, etc.

Mute Groups 2 CC80-85 on (127) / o (0), toggle latching

Faders 1 CC0-79 0-127 Value 95 = 0dB

Mute 2 CC0-79 on (127) / o (0), toggle latching

Pan 3 CC0-79 1-127 Value 64 = Pan Mid

MIDI TX Midi Ch Controller Value Comment

Mute Groups

Faders 1 CC0-79 0-127 Value 95 = 0dB

Mute 2 CC0-79 on (127) / o (0), toggle latching

1 Program Change 1-100

2 CC80-85 on (127) / o (0), toggle latching

Pan 3 CC0-79 1-127 Value 64 = Pan Mid

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

music-group.com behringer.com

2