Belden Grass Valley Kayenne K-Frame, Инструкция по установке и обслуживанию

Страница: 183 / 288

KAYENNE K-FRAME — Installation & Service Manual 183
Multiple Suite Resource Sharing
same suite, permitting quick access to different sources appropriate for
each work location.
Control surfaces allow operators to collaborate on the same production
while providing isolation between the operators themselves. For example,
a smaller Control Panel set up in the studio for rehearsals will need access
to the same effects as a larger Control Panel in the control room, but may
need access to a specific set of sources. The smaller panel also requires a dif-
ferent button mapping. If a Menu Panel is associated with each Main panel,
the DPOP operations of one panel should affect its menu, not the other one.
Logical Aux Buses
Each suite can be configured to have 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 physical 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 phys-
ical connections, but share the same logical Aux bus number.
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 Kayenne K-Frame 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 to individual suites. Each suite can
be configured to respond to particular GPI commands, with the other suite
ignoring these commands.