Leviton MC24/48, Руководство пользователя

Страница: 275 / 294

Appendix D: MIDI Interface
Software Version 3.05
D-9
Link Stack.
Encore consoles use a "link stack" to facilitate iterative
looping and subroutine calls. Iterative looping occurs when a cue contains a
link to an earlier cue along with a link repetition count. Subroutine calls occur
when a cue contains a link to a later cue. MIDI commands that specify a cue
number cause the pre-existing Stage Cue to be "pushed" onto the top of the link
stack. Go commands invoke subroutines which then return to the original cue
sequence.
Go To Cue.
A "Go To Cue" command is used to "get to" the end look of a
cue out of sequence without initiating follow, effect, profile, or other assigned
cue parameters. The default time for a Go To Cue command is one second,
instead of the assigned cue fade time. The purpose of the Go To Cue command
is to bring channels to the levels they would have obtained if the cue was
invoked in sequence and allowed to finish. As a result, all channel levels are
changed to the end look of the cue, whether or not they are tracking levels in
the cue.
Testing the MIDI Ports
The MIDI I/O TEST window appears when you simultaneously press the blank
center key and the [PAGE DOWN] key on the Encore Position Keypad. In this
mode, no external MIDI commands are transmitted or received. The MIDI I/O
TEST window is strictly for viewing raw data streams.
?
E
XAMPLE
:
You can use the MIDI I/O TEST window to perform
the debug (loopback) test as follows:
1.
Connect a MIDI cable from the MIDI IN connector port to the MIDI
OUT port.
2.
Simultaneously press the blank center key and the [PAGE DOWN]
key on the Position Keypad.
3.
Press the [ENTER] key to start the test.
4. Press [CLEAR] to stop the test.
In this loopback test mode, data is continuously output and received, and then
the received data is compared to the transmitted data. As MIDI commands are
received, the hexadecimal code of the last received command appears in the
MIDI I/O TEST window. An error count is displayed in the window which
shows how many mismatches have occurred, if any.
The MIDI I/O TEST operation is independent of whether the MIDI Control
device interface is enabled, and independent of the Device # assignment. If
MIDI commands do not appear in the MIDI Command History window in the
Playback display when MIDI is enabled, the debug loopback test should be used
to confirm what data is actually being received.