Grass Valley Kalypso User Manual V.15.0 - Manual (Page 339)

Kalypso — User Manual 339
Resource Sharing
the touch of a single button. It is not necessary to know what all these spe-
cific resources are and acquire them manually.
For example, an evening newscast probably needs all the switcher's
resources. However, a noon cut-in might be switched with only M/E 3,
PGM-PST, one chroma keyer, and two TEs. The Suite Pref for the evening
newscast marks all resources as desired; while the noon cut-in Suite Pref
marks only M/E 3, Pgm-Pst, one chroma keyer and two TEs as desired.
Acquiring the resources necessary for these programs is then accomplished
by loading the Suite Pref and touching Acquire Desired in the Acquire
menu. The resources not acquired for the noon cut-in remain available for
use by operators in the other Kalypso suite.
Logical Aux Buses
Each suite has its own set of numbered Logical Aux buses. This means
effects built for one suite will run properly in the other as long as the phys-
ical connections for the same numbered logical Aux buses are similar. For
example, if Aux bus 5 in one suite is used to feed that studio’s monitor wall,
using Aux bus 5 in the other suite to also feed that studio’s monitor wall
will make effects compatible between the suites. Note that these Aux buses
have different internal paths and different physical connections, but share
the same logical Aux bus number.
When Aux buses have been associated with an external device, like a DPM,
when that external device is assigned to a suite the associated logical Aux
bus assignments follow. Only one instance of each of these DPM assigned
Aux bus numbers exist in the system, not two. Aux buses for DPMs are
used either in suite 1 or suite 2 and are not logically assigned.
Remote Aux Panels
Remote Aux panels are set up as part of a particular suite. They then
become another control surface of that suite, with functionality limited to
controlling only the Aux buses assigned to that suite.
External Control Points
Some types of Kalypso system control originate from an external location,
like an edit controller, or a GPI contact closure. The Resource Sharing
feature accommodates these control points differently.
A separate editor port can be assigned to each suite. An edit controller con-
nected to each port is considered part of only that suite, and controls only
the resources currently acquired by that suite.
GPI inputs themselves are not assigned t o individual suites. Each suite can
be configured to respond to particular GPI commands, with the other suite
ignoring these commands.