beautypg.com

Expanding existing kaleido-x frames, Part 1 of 2 — merging databases, Expanding existing – Grass Valley Kaleido-X (7RU) v.7.70 User Manual

Page 62: Kaleido-x frames

background image

50

Kaleido-X (14RU) Expansion

Expanding EXISTING Kaleido-X Frames

Expanding EXISTING Kaleido-X Frames

There are two procedures that must completed to join two previously commissioned
(standalone) Kaleido-X frames in expansion mode:

• Merge the databases of the two standalone frames (see

Part 1 of 2 — Merging

Databases

below).

• Physically join and configure the frames (see

Part 2 of 2 — Joining & Configuring

Frames

, on page 59).

Part 1 of 2 — Merging Databases

If you are planning to join two existing Kaleido-X frames, it is likely that you will want to
keep their configurations (logical sources, levels, destinations, rooms, layouts, etc.) intact.
But when two separate frames become one expansion frame, they share a single database.

XEdit provides a tool for merging two databases into one, prior to the joining of the two
frames. This tool combines the configuration settings from both frames, modifying them
when necessary to avoid conflicts. For example, if a logical source name is the same on
Frame A and Frame B, it will be renamed.

When a database for Frame B is merged into a database for Frame A, most of the
information from Frame A is preserved, but only some of the information from Frame B. For
this reason, the standalone frame that has the most elaborate settings (rooms, layouts, logical
sources, etc.) should be designated
Frame A.

To merge two Kaleido-X databases

1 Open XEdit.

2 Import the database from Frame B (refer to Importing a Database, in the Kaleido-X

User’s Manual).

3 Create a backup of the Frame B database (refer to Creating a Backup, in the Kaleido-X

User’s Manual).

This is what will become the Frame B portion of the expansion database.

4 Import the database from Frame A.

It is important that you designate the most complete database (the one with the most
elaborate rooms, layouts, logical sources, etc.) as the Frame A database, since not all
data from the Frame B database is carried over during a merge.

IMPORTANT

You must merge databases before joining two existing frames in
expansion mode.

Type a name for
the backup here