Digilite Pulse MX - MIDI Interface Control; MIDI Configuration

PULSE MX
64
- 7 - MIDI INTERFACE
The main playback functions of the console can be controlled by MIDI comunication protocol; this can
be usefull for controlling and/or syncronizing the console playback by any device capable of trasmitting
Midi messages.

The playback functions controllable by Midi protocol are:
1. Cue list activation
2. Cue list release
3. Cue List ash activation
4. Cue List ash deactivation
5. Cue list intensity submaster setting
6. Cue list eect speed master setting
7. Cue list eect size master setting
8. Page change
Before exploring how the Midi conguration window works we will talk a little bit about Midi messages
structure: a Midi message has 2 or 3 bytes depending on message type; the rst byte, called Midi status
byte, contains both the message type (Note On , Note O,..) and the channel number; the following
bytes, called Midi data bytes, have dierent names and meanings depending on message type and their
value can range from 0 to 127. In order to control the console playback functions it is necessary to assign
a Midi status byte to each of them; the available messages for console playback control are:
• Note O: 3 bytes, followed by Note number and velocity
• Note On: 3 bytes, followed by Note number and vel0city
• Control Change: 3 bytes, followed by Control number and New value
• Program Change: 2 bytes, followed by New program
NOTE: by convention it is assumed that a Note On message with zero velocity is interpreted as Note O
Due to its features, the Program Change message cannot be used to control the master setting functions
(functions 5,6 and 7).
MIDI Configuration
The Midi conguration window can be opened by pressing the Midi conguration button from Setup
Menu.
First of all you have to dene which cannel Midi messages directed to the console will be transmitted on:
you can set this value by moving the rst wheel; if you select All, the console will receive all Midi mes-
sages regardless of the channel number which they are transmitted on.
Then you have to select the specic Midi message that will manage each functions. In order to do this
you have to move the second and third wheel for selecting respectively the message type (Midi status
byte) and the starting value for the rst Midi data byte (Midi start value).
The rst Midi data byte value represents the number of Cue list involved by the function; this number is
obtained by making the dierence between the Midi data byte value and the Midi start value, if the dif-
ference is null the current cue will be selected.
In this way a range of 25 values for each function will be reserved except for the Change page command
that require only 24 values to address all the pages because the destination page number is calculated
as the dierence above mentioned plus 1.
The Playback level, Eect speed and Eect size commands need 3 bytes messages in order to be com-
pletely dened (thus they cannot be managed by the Program change message that has 2 bytes only),
the rst Midi data byte contains the Cue list number (using the same convention already pointed out on
previous paragraph) and the second Midi data byte contains the master value information coded in two
dierent way depending on the command: