Revision C • 10/07
H
A
R
R
I
S
C
O
R
P
O
R
A T
I
O
N
4-24
4 RMX
digital Server
and destinations. The section header
[Router
Command_1]
, is used in the
init.mac
file to set
up the default routing for the audio and assign-
able logic connections on the KSU and 8-Input
Expansion cards by ‘taking’ or routing each source
to a DSP destination.
A typical
[Router Command_1]
section on a
RMX
d-4 is shown below:
[RouterCommand_1]
take_1=65873,65745 ; KSU A ALG to KSU channel 1
take_2=65875,65747 ; KSU B ALG to KSU channel 2
take_3=65877,65749 ; KSU C ALG to KSU channel 3
take_4=65879,65751 ; KSU D ALG to KSU channel 4
take_5=65881,65753 ; KSU A DIG to phantom fader 29
take_6=65883,65755 ; KSU B DIG to phantom fader 30
take_7=65885,65757 ; KSU C DIG to phantom fader 31
take_8=65887,65759 ; KSU D DIG to phantom fader 32
Each Take command
(take_x=source,
destination)
must be listed in numerical or-
der and be on separate lines. Signals can be iden-
tified by their Global signal IDs, as shown above.
65873
identifies the signal as the KSU card A
analog left channel in the console assigned as de-
vice number 1. The
65745
identifies that it goes
to “input 1” of the DSP in the KSU card.
Up to sixty-four of these Take commands can
be listed in numeric order in any one session file
to route sources to destinations. This routing oc-
curs when the session file is loaded (unless a chan-
nel strip is On, in which case it is pending until
the channel is turned off).
Routes assigned by a session file are continu-
ously maintained until another session file is
loaded that changes the routing or until a new
source is selected on a channel strip, by using a
FTP command or by using an Edge Device. All
routes are held, even if the console is turned off or
loses power, by a “persistence file” that gets up-
dated after every route is taken.
In previous examples, one source has been
shown being routed to one destination, but any
one source can be routed to any number of desti-
nations by adding separate Take command lines
from that source to the other destinations.
Include Lists
A source can only be routed or selected on a
channel strip source selector if it’s a source listed
on the console’s Source Include List, which is
stored in the console’s
routers.ini
file. The
Source Include list (its header is
[srcinclude]
,
is created and maintained using VMCC. It must
list every signal that may be required to be routed
on a console.
Since this list could include every signal from
every device in the VistaMax community, the in-
clude list could have several hundred sources. This
would make finding the desired source very diffi-
cult for the board operator.
To limit the total number of sources shown on a
channel’s source selector, each channel can have a
channel-specific source list assigned by the ses-
sion file. It should include only those sources re-
quired for a particular daypart or application. In
most applications, some channels will keep all
sources available while others will have specific
subsets with only the required signals listed.
It should be noted that once a channel has been
assigned a channel-specific include list, that list
will be used for subsequent sessions, unless a dif-
ferent channel-specific include list is specified for
that channel. To return the list to the master in-
clude list, the channel-specific include list would
have this command:
include_1=all
.
The following is an example of the channel-
specific include lists for four channels set as Telcos.
In this example Telco 1 (channel ID 81) and Telco
2 (channel ID 82) are active, while the Telco 3
(channel ID 83) and 4 (channel ID 84) entries are
file placeholders since they are not assigned:
[Router_81]
Include_1=D1,65-96,161-192
Include_2=D2,257-272,337-352,
Take=65873
[Router_82]
Include_1=D1,65,67,69,71,73
Include_2=D2,257-272
Take=macro_2
Summary of Contents for RMXDIGITAL
Page 2: ...Revision C 10 07 H A R R I S C O R P O R A T I O N ii...
Page 90: ......
