Euphonix CS Series Manual page 4

Christian Dolenga
2. Data formats / message types
Now we take a look at how those commands are sent and how we can interpret and translate
them into useful commands. MIDI messages (and bytes in general) are usually expressed in
hexadecimal, which is a convenient way of reducing the number of digits of an 8-bit (binary)
message. So a binary message of 1111 1111 would result in FF, 0111 1111 would become 7F
and so on. Since the first bit is reserved for the start or end of messages, the highest value of a
MIDI command cannot exceed 7F, which in decimal would be 127, which brings us to the typical
7-bit limit of 128 Notes (0 counts as value), 128 CC values, 128 whatever, if not used together
with another MIDI message. If we use CC pairs (e.g. CC01/CC33) to target a controller, we get 14
bits resolution, which results in 16384 values, being more appropriate for sensitive things, such
as volume faders on a console...
2.1. ES108 messages (MOTU Port 1)
Please refer to the "MIDI Implementation" pages in the "ES108 Installation/Service
Manual", starting at page 5-1. By the time of writing I have no desire to hijack the data and
reuse it for something different than what it already does best: controlling my ES108A
2.2. ASCII Characters for "CleaR Displays" (MOTU Port 2)
The messages sent from MixView look like this:
F0 2B 7F 14
where F0 and F7 always mark the start and end of a SysEx-message,
2B 7F are usually the manufacturer IDs (so no other devices on that port accidentally react
to that message), but in this case I'm not so sure,
on the CleaR Displays,
channel 16, etc...),
20 20 20 48 65 6C 6C 6F
H
are the 8 characters in ASCII-code to display, where
named channel 18 Lower Fader "Hello", then that would be the SysEx message that's being
sent on either loading the snapshot (along with all the other fader names), (re-)naming that
fader, or releasing it after adjusting its level. During fader movement (either physical or
automated) the dB value in 0.25 dB increments or decrements is sent as ASCII characters,
which results in A LOT of consecutive messages.
By the time of writing I don't know yet how to get a program to directly translate the MIDI
message into ASCII characters, but I'm working on it. The long-time goal would be to build
one's own version of those "CleaR Displays", either as an overlay on a computer screen, or
as hardware with an Arduino and 8x1 character LCDs...
Euphonix MIDI capabilities
11 40 20 20 20 48 65 6C 6C 6F
11 targets channel eighteen
40 targets the lower fader
e l l o
F7
14 is the command type for displaying text
(00 would be channel 1,
(00 would target the upper fader), and finally:
20 stands for empty space. If you
Revision 1
0F would be