Harris RMXDIGITAL, Руководство по эксплуатации и техническому обслуживанию

Страница: 114 / 118

Revision C • 10/07
H A R R I S C O R P O R A T I O N
A-14
Appendix A VMCC
In 400-series code, return logic routes were
manually created by using a macro file to route
the signal with logic to a channel and to then route
the logic from the fader channel back to the pe-
ripheral device.
This could be problematic if the console was
dayparted and one daypart had a CD player on
fader 15 while other dayparts had an Instant Re-
play and a VoxPro routed to the same fader. The
problem was that the return logic route would not
be affected when the source routed to the fader
channel was changed. Thus even though the CD
player was routed to the channel, the return logic
would remain tied to the previous peripheral. This
same problem would occur when multiple logic
controlled devices are selected on a single fader
channel.
To solve this issue, macros, instead of source
signals, are selected by the operator. Each macro
routes the desired signal to the fader, releases the
logic route going to the other devices with logic
available to that fader, and routes the logic to the
selected peripheral. Here’s a typical macro for rout-
ing return logic, required for 400-series code:
[RouterCommand_1]
Take_1=277,157 ;CD 2 to fader 15
Take_2=157,277 ;return logic to CD 2
Take_3=-1,339 ;cancel logic-VoxPro
Take_4=-1,343 ;cancel logic-InstRply
This macro routes CD 2 to fader 15 and routes
the channel 15 logic to the CD player, while also
routing silence (the
-1
source) to the VoxPro and
Instant Relay to ensure the channel 15 logic no
longer controls those devices. Similar macros
would be created for the VoxPro and Instant Re-
play to remove the logic from the other devices.
When 500-series code is sued, this same pro-
cess can be used, but in most cases it is far sim-
pler to assign return routing on most signals since
the net result is that signal source selection with
logic control is much easier than it ever has been
in the past since macro files do not have to cre-
ated to handle the return logic routing.
There are still some signals where using return
logic routing may not be desirable. That’s because
automatic return logic routing is made each time
that signal is routed to a fader. Thus, someone on
another console might dial up that source and steal
logic control away, removing control from the origi-
nal fader. If this occurs, simply retake the signal
to move return logic control back to the previous
channel.
Because of this, there may be some signals (like
digital playback channels that are dedicated to one
room) that should not have the reverse logic rout-
ing feature selected to ensure that the logic can-
not be accidentally routed from another fader
channel.