C-2
Rev 2.2, 10/31/94
column headings (119 in this example). From MIDI, you send an edit buffer data set command
(1Ch) with a parameter offset value of 4Ah and a parameter value of 77h (119d).
The offset value is added after multiplication by the scale factor and is stored with its own
offset of -64. The stored offset is doubled before being applied to the realtime MIDI value. The
offset is stored in the 601 as an unsigned value having a range of 0-127. Each step in the
stored value between 0 and 127 represents an offset increment of 2, and the actual offset is
derived from the stored offset as follows (dec):
offset
v
=
−
(
) *
64
2
where: v = stored value (0-127) and
offset
= (-128 to +127)
The value applied to the edit buffer is derived as follows:
e
m k
v
=
+
(
* )
where: e = new edit buffer value,
m = modulation value
v = stored offset,
k = stored scaling value from table
Note
: in the 601, the scale factor is shown as
SCAL
on the display.
For the purposes of Realtime MIDI, each edit buffer parameter has a range of 0-127 regardless
of what the actual range of values is, as specified in the tables at the end of this appendix.
Thus an on/off type of parameter will be
off
if the result of the offset and scale operation
ranges from 0 to 63 and
on
if the result is in the range of 64-127.
In software version 1.1 and higher, Realtime Block 1 has two additional parameters that apply
an upper (CLPH/clip hi) and lower (CLPL/clip lo) limit to the final parameter value. You can use
these parameters to keep a realtime MIDI value within a useful range. Realtime Block 2 has an
additional modulation source,
bLC1
that is the output of Realtime Block 1.
As each parameter change request arrives, it immediately modifies the appropriate edit buffer
location, and inserts a DSP update request into a 128 byte FIFO queue. The 601 processes the
queue as time allows. If a burst of requests fills the queue, new requests are discarded until
there is room in the queue. If your MIDI controller spews data and overruns the 601's queue,
the 601 may ignore the extra data. If the stream of data ends before the 601 finishes processing
its queue, the 601 may miss the last message in the data stream. A program change forcefully
clears the queue.
C.1.3 Sysex Implementation (F0)
All sysex messages use the universal system exclusive code format. The MIDI sysex message
uses the following format (hex):
Send:
<sysex><mfrID><unitID><unit#><command><data ...><EOX>
<F0><00><00><5E><01><#><command><data ...><F7>
Send a Edit Buffer Data Set message to the 601, and set the level for Filter 1 of the parametric
equalizer block to +12 dB:
<sysex><mfrID><unitID><unit#><command><offset><value><EOX>
<F0><00><00><5E><01><#><1C><06><70><F7>
where:
F0 is the midi sysex command
00 00 5E is Symetrix’ ID
01 identifies the 601
# is the unit number
1C is the Edit Buffer Data Set command (see Table 3)
06 is the level parameter from the Filter 1 table (Table 11)
70 is the value for +12 dB from Table 27 (see also Table 11)
Summary of Contents for 601
Page 46: ...4 18 Rev 2 2 10 31 94 This page is blank believe it or not ...
Page 48: ...4 20 Rev 2 2 10 31 94 Notes ...
Page 50: ...5 2 Rev 2 2 10 31 94 Notes ...
Page 70: ...7 16 Rev 2 2 10 31 94 Notes ...
Page 72: ...8 2 Rev 2 2 10 31 94 Notes ...
Page 74: ...9 2 Rev 2 2 10 31 94 Notes ...
Page 78: ...11 2 Rev 2 2 10 31 94 Notes ...
Page 126: ...D 12 Rev 2 2 10 31 94 Notes ...
Page 138: ...G 8 Rev 2 2 10 31 94 Notes ...
