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

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

Revision C • 10/07
H A R R I S C O R P O R A T I O N
A-11
Appendix A VMCC
When the operator dials through the available
sources, the macro names (remote, telco_norm,
request) appear in the list alphanumerically
along with the other signal sources included.
Fader Channel Macro Usage
When taking macros, the same rules apply as
for signals: if the channel is Off, taking a macro
causes it to execute immediately. While the chan-
nel is On, taking any macro—local or remote, will
show brackets around the name because the macro
is pending. It is then executed as soon as the chan-
nel is turned Off.
Macros listed on a fader channel using the 400-
series format causes the console automation to
check the local sesfiles folder to verify that the
macro file is actually present. If the macro file is
not found, the name is surrounded by arrows:
> Macro name <
when dialed up on a
fader channel. If this macro is subsequently taken,
the name is surrounded by square brackets,
[ Macro name ]
to indicate the macro is
pending since it was not found.
Note that this function only checks the local
device. When macro files from other devices are
listed it is assumed they execute as requested since
there is no indication the macro file did not load
as requested.
PHANTOM CHANNELS & BUSES
Each RMX digital includes four “phantom chan-
nels”—special-purpose input channels within the
KSU DSP, that can be used just like any other
input channel, albeit without any physical con-
trols. Any input slot covered by a blank panel (e.g.,
no Dual Fader panel is installed in that slot) means
there are two more phantom channels available
for each blank panel in the console.
Each RMX digital also includes several “phan-
tom buses” that can have any channel assigned to
them—including the phantom channels, from a
session or macro file. To use these phantom buses,
edit the session file by changing the channel entry
under the appropriate phantom bus header from
the default setting of
C h a n n e l _ x x = 0
to
Channel_xx=1
. This setting assigns the channel
to that bus. These bus signals are included in the
standard source signal list in VMCC. Here are the
phantom bus headers—which are always included
in each session file, and what each controls:
•
[Solo]
Assigns the channel to the solo
bus (since the signal is taken post switch
and post fader, this command is not very
useful on phantom channels).
•
[Send_2]
Assigns the channel to the Send
2 bus.
•
[Utl_1, Utl_2, Utl_3, Utl_4]
Assigns the channel to one or more Utility
buses.
•
[Send_2_PF, Utl_1_PF, Utl_2_PF,
Utl_3_PF, Utl_4_PF]
Sets the chan-
nel to feed a bus pre-fader. This setting does
nothing if the channel is not assigned to
the same bus.
•
[Send_1_PS, Utl_1_PS, Utl_2_PS,
Utl_3_PS, Utl_4_PS]
Sets the chan-
nel to feed a bus pre-switch. This setting
does nothing if the channel is not assigned
to the same bus.
To use the phantom buses, they must be routed
to a VistaMax destination. For example, if the Util-
ity 1 bus is being used, it can be routed to the
KSU digital output D by adding this route entry:
[RouterCommand_1]
take_1=229,255;UTL 1 > KSU digital D
If the Pre-Fader and/or Pre-Switch entries are
set to
=1
, then that channel’s signal is immedi-
ately applied, at unity gain, to the bus when the