Revision D • 8/05
HARRIS CORPORATION
A-7
Appendix A VMCC
di
ital
[chain]
This section allows one or more session files to
be automatically loaded on other consoles or racks
when the session is loaded. It is more often used
in macro files than in session files, but it works
equally well in either. The chain command entry
looks like this:
[chain]
call_1=remote_1.ses,9
This is most often used to route a return signal
(mix-minus, IFB) for a remote or for a shared two-
way device like an ISDN interface that connects
to another device. In the example, the KeyValue is
call_1= and the Entry Value is remote_1.ses
which is loaded on device 9.
[RouterCommand_1]
This section allows one or more routes to be set
when the session loads. Typical usage was shown
in the examples on signal numbering on the pre-
vious page.
Each take_x KeyValue, numbered sequentially
from 1, defines one route. Each EntryValue de-
fines the source and the destination for that route.
In take_1=161,241 signal 161 is the source and
signal 241 is the destination.
MACRO FILES
Macro files are text-only command files that
have a .mac suffix. They are created using a text-
only editor like Notepad®. Macro files contain ses-
sion file-type commands to perform one or more
tasks. A simple macro might consist of a couple
commands to route signals for setting up a live
remote.
A more complex macro could not only route
bidirectional signals, but could also command ses-
sion files to load on several community devices.
One use for this would be to setup a facility for
unattended overnight operation. When the morn-
ing show staff comes in, they would run another
macro to return the consoles back to standard day-
time operations.
Macros are loaded into a console or VistaMax
rack just like a session file: they can be run manu-
ally through using a file load FTP command; they
can be added to the Task Scheduler so they are
run at specified times; or they can be added to a
router channel for board operator selection and
loading.
Macro files are stored in the SesFiles folder. Since
they do not have a .ses suffix they do not show
up in the Session selector. If a board operator needs
to load a macro, the macro can be assigned as a
“source” on a router channel. The macro is ex-
ecuted when the operator selects the macro and
presses
Take
on the router channel. The only down-
side: adding a macro to a router channel means
that channel is exclusively set aside for macros—
no normal audio sources are displayed.
Here is part of an RMX
d
session file showing a
standard router definition and one set for loading
macros:
[Router_4]
include_1=257-287,321-335
Take=259
[Router_5]
macro_1=dallas
macro_2=chicago
macro_3=tucson
macro_4=bayonne,6
Router 4 is a typical router section with a chan-
nel-specific include list (to limit the sources dis-
played), and a take command that routes a signal
on the channel when the session file is taken.
Router 5 is set to display four macros in its
source list. Macros 1, 2 and 3 are on the local
device. Macro 4 (bayonne) is run on device 6. The
session file command syntax for assigning mac-
ros to a router channel is as follows:
[Router_x]
Macro_n=Filename,d
x is the channel ID of the router channel.
To Next Page
Loading...