Grass Valley GV Orbit Client User Guide

Please refer to related GV Orbit documentation, see Related Documentation , on page 19. In

Domain IDs and IP Ports

A GV Orbit system employs ‘domains’ to segregate internal communications. Domains are specified with a Domain ID number (1 to 252) and each Domain uses separate IP ports.

(For further information about IP Ports and Domain IDs for the GV Orbit client and server, refer to the GV Orbit Release Notes

Note:

Domain ID numbers may be changed by the user. When using changed

Domain ID numbers, recalculate the IP port numbers; refer to the

GV Orbit Release Notes in

GV Orbit Services Requirements

Lite :

There are no GV Orbit servers in a GV Orbit Lite installation and, as a result, no GV Orbit services in a GV Orbit Lite system.

Professional and Enterprise :

GV Orbit Client requires at least one GV Orbit server running configured GV Orbit Services.

particular, for information on GV Orbit services, refer to the GV Orbit Admin Guide .

Introduction

In This Document

GV Orbit Client Version 2.0.0

User Guide

In This Document

This document describes some steps for getting started with GV Orbit Client and then proceeds to describe other features.

• Chapter 2, Getting Started Steps , on page 25.

• Chapter 3, Home Screen , on page 83.

• Chapter 4, Manage Users , on page 159.

• Chapter 5, Getting Started With GV Orbit Control Client , on page 189.

• Chapter 6, Configuration Tasks , on page 195

• Chapter 7, Special Device Configuration Tasks , on page 347

• Chapter 8, Monitoring Tasks , on page 447

• Chapter 9, Control Tasks , on page 461

• Chapter 10, Administration Tasks , on page 473

• Routing control panels:

• Chapter 11, Routing Control - Bulk Routing Panel , on page 487.

• Chapter 12, Routing Control - XY Routing Panel , on page 579.

• Clustered multiviewers (applications with multiple multiviewers):

• Chapter 13, Multiviewer Cluster , on page 645.

• Chapter 14, MV Cluster - Room Editor , on page 671.

• Chapter 15, MV Cluster - TSL Tally Configuration , on page 757.

• Chapter 16, Audio Bars Configuration , on page 785.

• IP configuration for IP routing:

• Chapter 17, IP Configuration , on page 795.

At the end of the document there is a handy

Glossary of Terms

Summary contents of this chapter:

Getting Started Steps

Step 1: Download, Install and Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Step 1.1: Download Client Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Step 1.2: Installation of GV Orbit Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Step 1.3: Installation of GV Orbit Control Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Step 1.4: Launch GV Orbit Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Step 2: GV Orbit Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Step 2.1: New Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Project Home Screens in GV Orbit Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Step 2.2: Save, Push, and Close a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Open and Pull a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Exit GV Orbit Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Step 3: Device Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Step 3.1: Direct Configuration of RollCall-protocol Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Step 3.2: Configuration of Densité and RollCall Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Step 3.3: Configuration of Other Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Step 4: Device Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Step 4.1: Upgrade RollCall-protocol Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Step 4.2: Upgrade Densité-protocol Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Change Functionality of a ‘Software-Defined Core’ Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Step 5: Adding Support for Further Densité Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Add or Update Densité Card Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Step 6: Multiviewer Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Simple Multiviewer Project Editing Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Step 7: Control and Monitoring Project Setup (Professional/Enterprise) . . . . . . . . . . . . . . . . 69

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Step 7.1: New C&M Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Step 7.2: C&M Setup Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Step 7.3: Further Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Step 7.4: Saving and Pushing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

The purpose of this chapter is to provide the minimum steps required to install, configure and get started with the GV Orbit Client application.

Getting Started Steps

Step 1: Download, Install and Launch

GV Orbit Client Version 2.0.0

User Guide

Step 1: Download, Install and Launch

Lite



Professional



Enterprise



This section describes how to download/install client installers and launch GV Orbit Client.

•

Step 1.1: Download Client Installers , on page 26.

•

Step 1.2: Installation of GV Orbit Client , on page 28.

•

Step 1.3: Installation of GV Orbit Control Client , on page 31.

•

Step 1.4: Launch GV Orbit Client , on page 33.

Step 1.1: Download Client Installers

Download Installer for GV Orbit Lite

On the client PC:

1 Go to https://community.grassvalley.com/support/s/productdownloads

The Grass Valley product downloads login web page is shown.

2 If you already have a Grass Valley support login user name and password, then click Login and login here.

3 If you require a Grass Valley support user name and password, then click Request Portal Access , fill in your details and click Send Request to request

Grass Valley portal access.

The GV Orbit Lite client installer has been downloaded.

Download Installers for GV Orbit Professional and Enterprise

GV Orbit Professional and Enterprise use one or more GV Orbit servers which are the source of client installers in GV Orbit Professional and Enterprise systems.

Note:

Downloading of the GV Orbit Client installer is separate from the downloading of the GV Orbit Control Client installer.

Download both the GV Orbit Client and the GV Orbit Control Client installer from the

GV Orbit server. (Thus, client versions are kept compatible.)

(For full download instructions, refer to the GV Orbit Admin Guide , see

Documentation , on page 19.)

On the client PC:

1 Enter the GV Orbit server‘s IP address into a browser. (Chrome recommended.)

The GV Orbit server Admin Login

screen appears. (See Figure 2-1.)

2 Click on each of the client installer download links to download the installers.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 1.1: Download Client Installers

Client installer download links

Fig. 2-1: GV Orbit Server Admin Login Screen

Note:

Client installers on the GV Orbit server are updated with a server update.

After a server update, download and reinstall the clients (recommended).

Getting Started Steps

Step 1.2: Installation of GV Orbit Client

GV Orbit Client Version 2.0.0

User Guide

Step 1.2: Installation of GV Orbit Client

Lite



Professional



Enterprise



Installation of GV Orbit Client and of GV Orbit Control Client is done separately.

This section covers GV Orbit Client installation, including some information about any existing, legacy Orbit installs.

(For GV Orbit Control

Client, see Step 1.3: Installation of GV Orbit Control Client , on page 31.)

Legacy Orbit Client Users

For users with the older, legacy ‘Orbit’ client already installed on the client PC, the following applies:

• GV Orbit Client may be installed on the same client PC as the legacy ‘Orbit’ client application.

• GV Orbit Client and the legacy ‘Orbit’ client may not be run together.

• At installation, GV Orbit Client inherits registry settings from any already-installed legacy ‘Orbit’ client (for example, multicast/unicast discovery setting, and ‘recent projects’ list).

Install GV Orbit Client

Note: GV Orbit Client installs into client PC’s ‘Program Files’ folder by default.

1 Run the downloaded installer file on the client PC.

Allow the installer to run by responding to any Windows TM dialogs accordingly.

The GV Orbit Client installer ‘Setup GV

Orbit’ screen is then shown.

2 Click Next> to begin the installation.

Fig. 2-2: GV Orbit Client’s Setup Screen

GV Orbit Client Version 2.0.0

User Guide

3 Accept the License Agreement in the following dialog and click Next> .

The installer will install into the folder of an existing installation of GV Orbit

Client.

Getting Started Steps

Step 1.2: Installation of GV Orbit Client

Fig. 2-3: GV Orbit Client’s Setup Screen

4 If no previous GV Orbit Client is found, then an installation folder is prompted for.

(Default folder location is C:\Program Files\Grass Valley\GV Orbit .)

5 Select a new folder, if required.

Click Next .

6 At the next dialog, click Install .

GV Orbit Client installation begins and a progress bar is shown.

7 When GV Orbit Client installation is complete, the GV Orbit Client setup

‘Completing’ screen is shown.

Fig. 2-4: GV Orbit Client Setup ‘Completing’ Screen

8 Click Finish and the GV Orbit Client application launches and shows its

initial screen. See Figure 2-6.

9 Close the GV Orbit Client application.GV Orbit Client is installed.

Note:

A shortcut is available from the

Windows TM Start menu.

(Start -> Grass Valley -> GV Orbit)

Fig. 2-5: GV Orbit Client Setup ‘Completing’ Screen

Getting Started Steps

Step 1.2: Installation of GV Orbit Client

GV Orbit Client Version 2.0.0

User Guide

Fig. 2-6: GV Orbit Client Initial Screen

Firewall

1 Check that the GV Orbit Client application is not blocked by your client PC’s firewall.

Note: Firewall:

‘orbit.exe’ should be on a list of allowed apps (or programs) that can communicate through the client PC’s firewall.

These PC settings may be controlled by your network administrator.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 1.3: Installation of GV Orbit Control Client

Lite Professional



Enterprise



This sub-section is applicable to GV Orbit Professional and Enterprise product versions.

Note:

The GV Orbit Control client installs into a user folder on the client PC. Thus it is normally only available to the user who carries out the installation.

1 Log into the client PC as the user who will be operating the GV Orbit clients.

2 Run the downloaded GV Orbit Control Client installer file.

Allow the file to run on the client PC by responding to any dialogs accordingly.

A splash screen is shown during installation:

3 When the installation is complete, the GV Orbit Control Client login screen appears.

Fig. 2-7: GV Orbit Control Client Login Screen

4 Enter ‘admin’ for both the User name and the Password .

5 Enter the IP address of the GV Orbit server in the Server text box.

6 Click Log in .

A blank GV Orbit Control Client screen appears.

Getting Started Steps

Step 1.3: Installation of GV Orbit Control Client

GV Orbit Client Version 2.0.0

User Guide

Fig. 2-8: GV Orbit Control Client Screen Example

7 Close GV Orbit Control Client.

GV Orbit Control Client installation is complete.

The installation folder is in the user folder, for example:

C:\Users\A_User\AppData\Roaming\JWrapper-GVOrbitControlClient\

CAUTION:

The GV Orbit Control Client is installed in a user folder and is therefore normally only available to the user who carried out the installation.

Note:

GV Orbit Control Client is not normally launched manually by the user.

Instead, it is launched by the GV Orbit Client application.

(Although a shortcut is available on the client PC desktop and from the

Windows TM Start menu: Start -> Grass Valley -> GV Orbit Control Client)

Firewall

1 Check that the installed application is not blocked by your client PC’s firewall.

Note: Firewall :

‘GVOrbitControlClient.exe’ should be on a list of allowed apps (or programs) that can communicate through the client PC’s firewall.

These PC settings may be controlled by your network administrator.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 1.4: Launch GV Orbit Client

1 GV Orbit Client may be launched from the Windows TM ‘Start’ button. (“GV Orbit”)

A splash screen is shown during start up:

And then the GV Orbit Client initial

screen is shown. See Figure 2-9.

Create New Project

Access a RollCall device control screen

Open a Network

Tree View

Information about the GV Orbit Client

Fig. 2-9: GV Orbit Client Initial Screen

Open existing Project

Open a Project recently-opened by

GV Orbit client

(Initially grayed-out)

Options

To GV Orbit documentation

To Grass Valley web site

Getting Started Steps

Step 2: GV Orbit Projects

GV Orbit Client Version 2.0.0

User Guide

Step 2: GV Orbit Projects

Lite



Professional



Enterprise



Introduction

This section describes how to open a project. GV Orbit project types are listed in Table 1-2 on page 22. Once a project is created in GV Orbit Client, it can be saved locally on the client

PC but it needs to be deployed for use by saving it (pushing it) to either:

• a multiviewer device (multiviewer projects; GV Orbit Lite , Enterprise and

Professional ); or to

• a GV Orbit server (C&M projects; GV Orbit Professional and Enterprise only).

Multiviewer project types are used to define a compatible multiviewer’s video wall. These are applicable to GV Orbit Lite , Enterprise and Professional .

The main project type for GV Orbit is a ‘Control and Monitoring’ project (C&M project) which is used for control and monitoring applications, and for routing control. This project type uses services running on a GV Orbit server and is applicable to GV Orbit Professional and Enterprise only.

•

Step 2.1: New Project , on page 35.

•

Project Home Screens in GV Orbit Client , on page 40.

•

Step 2.2: Save, Push, and Close a Project , on page 41.

•

Open and Pull a Project , on page 42.

GV Orbit Client Version 2.0.0

User Guide

Step 2.1: New Project

To Open a Project from the Initial Screen

1 Click New Project .

The New Project dialog is shown.

2 Select a project type.

Getting Started Steps

Step 2.1: New Project

Entered project name. Path to chosen folder. a) C&M project type selected b) Multiviewer project type selected

Fig. 2-10: New Project Dialogs

3 Click Browse and browse to a local folder on the client PC (or to a network folder accessible from the client PC) where the new project files will be placed.

Click Choose .

Note: The chosen folder is not on a GV Orbit server.

4 Enter a name for the new project.

5 Click OK / Next .

A sub-folder is created with the name of the project. It contains the new project files.

6 If prompted, answer Yes to create a directory (sub-folder).

• For a Multiviewer project, see

For a Multiviewer Project (GV Orbit Lite, Enterprise and Professional) , on page 36.

• For a C&M project, see

For a C&M Project (GV Orbit Enterprise and Professional) , on page 36.

Getting Started Steps

Step 2.1: New Project

GV Orbit Client Version 2.0.0

User Guide

For a Multiviewer Project

( GV Orbit Lite , Enterprise and Professional )

A dialog is shown for setting up the resolution of the multiviewer head display outputs.

7 Select the Output Size (1920x1080 or 1280x720).

8 Click OK .

The new multiviewer project is created and its GV Orbit Client project Home Screen is

shown. See Project Home Screens in GV Orbit Client , on page 40.

For a C&M Project

( GV Orbit Enterprise and Professional )

For a Control and Monitoring (C&M) project, a Setup dialog is shown.

(For more information about setting up a C&M project, see Step 7: Control and

Monitoring Project Setup (Professional/Enterprise) , on page 69.)

Server 1 IP

Fig. 2-11: C&M Project Setup Dialog

For the C&M project, in the Setup dialog:

1 Set Server 1 IP to the IP address of the GV Orbit server.

(For a GV Orbit Server Cluster system, still just enter the IP address of one server. The second server will be discovered automatically in the steps below.)

After the IP address is entered, GV Orbit Client carries out some basic system tests; it uses the current Setup dialog settings. System connectivity is checked and some basic system information is discovered from the GV Orbit server.

2 After these system tests are done, the results are listed in the dialog in a console pane.

See Figure 2-12.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 2.1: New Project

Green indicating GV Orbit Client’s server connection is OK.

Server 1 IP

Repository setting

Results of basic system tests in console pane.

(For more information, see

Step 7: Control and Monitoring Project Setup (Professional/Enterprise) , on page 69.)

Fig. 2-12: Example Basic System Test Results (Single Server Shown)

Note:

Some system test console items may be shown in ‘ red ’, indicating where discovered information disagrees with settings in the Setup dialog. In this case, settings in the dialog are then filled out automatically to be consistent with discovered settings.

A subsequent system re-test (performed below) will clear these red items.

Repository in Setup Dialog

For deployment, a C&M project is saved to the GV Orbit server in a Repository , one project per

Repository . This setting selects which Repository is used by the project.

1 For the Repository setting, click New .

The Create Repository dialog is shown:

2 Enter a name for the new repository and click OK .

System Re-Test

A system re-test will now remove any red items in the console pane. In the Setup dialog:

3 Click System Test .

This forces the GV Orbit Client to redo its basic system tests. The results are shown in the console. Any ‘red’ items from before should now be cleared.

Getting Started Steps

Step 2.1: New Project

GV Orbit Client Version 2.0.0

User Guide

Single GV Orbit server GV Orbit Cluster servers and Virtual IP Address

System Test clear output a) Single GV Orbit Server

Fig. 2-13: System Test Console Output: a) Single GV Orbit Server. b) GV Orbit Server Cluster.

b) GV Orbit Server Cluster

4 Click Apply .

The settings are applied to the project and a progress bar appears in the dialog.

5 A pop-up dialog may appear, asking if the local project should be updated from the chosen repository.

• Click Yes to update the local project (and lose any local changes made).

• Click No to keep the local project changes

(and not pull the project from the repository on the server).

The applying of settings continues and progress is shown in the progress bar:

6 A pop-up dialog box confirms when the ‘Applying’ is all done.

Click OK in the pop-up to proceed.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 2.1: New Project

7 In the Setup dialog, click Close .

The new C&M project is created in GV Orbit Client and its Home Screen is shown.

(See Project Home Screens in GV Orbit Client , on page 40.)

Note:

The Setup dialog can also be viewed when a C&M project is open by clicking

Connections -> GV Server in the main menu of GV Orbit Client.

Note:

Setting up and applying the GV Orbit server IP address for a project will automatically set up other comms settings for the project.

Getting Started Steps

Project Home Screens in GV Orbit Client

GV Orbit Client Version 2.0.0

User Guide

Project Home Screens in GV Orbit Client

The project’s Home Screen is shown and a new GV Orbit project has been created.

Note:

The Home Screen appearance varies according to project type and which

GV Orbit Client windows are enabled and being shown.

a) Example New Multiviewer Project Home Screen

Click icons to hide/show windows of project Home

Screen Project Window

Workflow Window

Network Window b) Example New C&M Project Home Screen (See

Project Home Screen

for Information)

Fig. 2-14: GV Orbit Home Screen Examples: a) Multiviewer Project; b) C&M Project.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 2.2: Save, Push, and Close a Project

Note: A GV Orbit ‘Multiviewer’ project type is typically for singlemultiviewer designs.

For video walls designs that are served by a cluster of multiviewers

(MV Cluster), then use the GV Orbit ‘Clustered Multiviewer’ project

type (described in Chapter 13, Multiviewer Cluster , on page 645).

Note: A C&M project type is for GV Orbit Professional and Enterprise only.

A C&M project can be created in GV Orbit Lite , but may not be used.

Step 2.2: Save, Push, and Close a Project

Step 2.2.1: Save a Project Locally

To locally save a project from GV Orbit Client:

1 Click Project -> Save Project in the main menu to save the project into the local folder on the client PC.

Step 2.2.2: Push Project (Save to Server)

To push an open project back into a repository (on the GV Orbit server, or on a multiviewer device):

1 Click Project -> Push in the main menu.

A Choose Projects dialog is shown.

Projects listed have been opened by the GV Orbit

Client before. These appear in the Project window on the client.

Fig. 2-15: Choose Projects Dialog

2 Select the project to be pushed. (More than one may be selected.)

Click OK .

The project is pushed to the repository.

Once a project is in a repository, it is deployed for use:

Getting Started Steps

Open and Pull a Project

GV Orbit Client Version 2.0.0

User Guide

• Multiviewer project - A project is pushed to a multiviewer which can then adopt the project’s video wall design.

• C&M project - A project is pushed to the GV Orbit server. Applications/services etc. on the server can then access the project. For example, the Web Renderer service can read the project and render its custom operator screens for viewing in a web browser.

Step 2.2.3: Close a Project

To close a project in GV Orbit Client:

• Click Project -> Close Project to close the project.

Open and Pull a Project

Open Existing Local Project

To open an existing local project from the GV Orbit Initial Screen :

1 Click the Open Project icon.

The Open dialog is shown:

2 Browse into the local project folder required and select the

‘configuration.prj’ file within it.

3 Click Open .

A login screen is shown.

4 For a new project, enter

User name ‘admin’ and

Password ‘admin’ and click Login .

The project’s Home Screen is shown.

Note: New GV Orbit projects have User name ‘admin’ , Password ‘admin.

Pull a Project (Load from Server)

To pull a project from a repository (on the GV Orbit server, or on a compatible multiviewer):

1 Click Project -> Pull in the main menu.

A Choose Projects

dialog is shown. (See Figure 2-15.)

2 Select the project to pull.

3 Click OK .

The project is pulled from the repository, stored locally on the client PC, and is opened by the GV Orbit Client.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Exit GV Orbit Client

Note: Pull and Push :

When connecting to a repository, the user may be prompted to Pull a project from a Repository . Pull a project in order to either:

• edit the project locally (any local project is overwritten); or

• run the project locally (for example, to run operator screens).

Do not Pull :

• if a local project has all been created or changed and which needs to be put into a Repository . (This requires a Push .)

Exit GV Orbit Client

Save the project locally and push it to be deployed, as required, before exiting GV Orbit

Client.

To exit and close the GV Orbit Client application:

1 Click Project -> Exit .

The application shuts down and exits.

Getting Started Steps

Step 3: Device Configuration

Lite



GV Orbit Client Version 2.0.0

User Guide

Professional



Enterprise



Introduction

This section describes how to access device control screens with GV Orbit Client. Devices can then be configured as required. RollCall- and Densité-protocol devices are covered.

•

Step 3.1: Direct Configuration of RollCall-protocol Devices , on page 44.

•

Step 3.2: Configuration of Densité and RollCall Devices , on page 45.

Step 3.1: Direct Configuration of RollCall-protocol Devices

RollCall-protocol devices can be configured directly from GV Orbit Client with the device’s

IP address from the GV Orbit Client Initial Screen :

1 Click the RollCall Control Screen icon, (or, with a project open, in the main menu click Connections -> RollCall -> RollCall Control Screen ).

The Open Template dialog is shown:

2 Enter the IP address of the target device.

3 Click OK .

The control screen is shown in a tab.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 3.2: Configuration of Densité and RollCall Devices

Click on x on tab to close device control screen

Fig. 2-16: Example Device Control Screen (RollCall-protocol Device shown)

4 When all device configuration changes are complete, close the control screen tab.

Step 3.2: Configuration of Densité and RollCall Devices

With a GV Orbit project open in GV Orbit Client, GV Orbit Professional and Enterprise can show RollCall-protocol and Densité-protocol devices with full status indication listed in a

Network window.

However, GV Orbit Lite can only list RollCall-protocol device items in the Network window and without any status indication.

Network Window Views

The Network window can show devices either in a tree-view or in a list-view. Toggle

between these views with the tool bar controls shown in Figure 2-17.

See

Network Window

for a description of the Network window.

Getting Started Steps

Step 3.2: Configuration of Densité and RollCall Devices

GV Orbit Client Version 2.0.0

Click to show List-View Click to show Tree-View

User Guide

46 a) Tree-View

Fig. 2-17: Network Window Views b) List-View

Note:

The Network window may already be showing system devices etc. for a C&M project open in GV Orbit Client if the GV Orbit services have been set up on the GV Orbit server, so no set up may be required here.

Initial set up of the Network window can be done in a project; this is done differently for

RollCall-protocol devices than for Densité-protocol devices and each is described below:

•

Step 3.2.1: Network Window Setup For RollCall Devices

•

Step 3.2.2: View a Device Control Screen - RollCall Devices

•

Step 3.2.3: Network Window Setup For Densité Devices

•

Step 3.2.4: View a Device Control Screen - Densité Devices

Step 3.2.1: Network Window Setup For RollCall Devices

RollCall device control screens can be viewed with GV Orbit Client via a GV Orbit server

(which runs a GV Orbit IP Proxy service).

To set up the Network window:

1 For GV Orbit:

• Lite From the GV Orbit Client Initial Screen , click the Network Map icon.

• Professional and Enterprise and with a C&M project open -

Click Connections -> RollCall -> Network Map in the main menu.

An Open Network

dialog is shown. (See Figure 2-18.)

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 3.2: Configuration of Densité and RollCall Devices a) Open Network Dialog

(after clicking on

Network Map in the GV Orbit

Client Initial Screen).

c) Redundant server case.

b) Open Network dialog

(after clicking on RollCall -> Network Map in GV Orbit Client’s main menu).

Fig. 2-18: Open Network Dialogs: a) After clicking Network Map icon in GV Orbit Client Initial Screen.

b) After clicking RollCall -> Network Map in GV Orbit Client main menu.

c) Redundant server case.

2 Select Enable Network Map Connection , if available in the dialog.

3 Enter an IP address for the Primary Address :

• GV Orbit Lite :

Enter the address of an IQ frame controller to be able to access all devices in the frame.

• GV Orbit Professional and Enterprise:

Enter the IP address of a GV Orbit server.

This will connect to the IP Proxy service running on the server and allow access to all devices connected to the IP Proxy service.

Note:

The IP address entered in the Open Network dialog may be for either:

• a GV Orbit server, which runs a IP Proxy service; or for

• a single device.

4 For redundant GV Orbit systems, select Enable Redundancy and enter the IP address of a second GV Orbit server.

Getting Started Steps

Step 3.2: Configuration of Densité and RollCall Devices

5 Click OK .

A Network window appears in the GV Orbit

Client:

This can be re-sized. It can show an expandable tree-view of all devices attached to the IP Proxy service.

GV Orbit Client Version 2.0.0

User Guide

Step 3.2.2: View a Device Control Screen - RollCall Devices

To view a RollCall device control screen from the Network window:

1 Locate the target device in the Network window ( tree-view or list-view).

Right-click on the item and select ‘Control’.

The control screen and its sub-menus are loaded and are then shown in a tab.

Click to close the device control screen tab

Fig. 2-19: Example Device Control Screen (RollCall-protocol Device Shown)

2 When all required user device configuration changes are done, close the control screen tab.

Right-click on any other device in the Network window to display/edit its control screen, as required.

Step 3.2.3: Network Window Setup For Densité Devices

Densité device control screens (card control panels) can be viewed with GV Orbit Client from the Network window via a GV Orbit server (which runs a GV Orbit Densité service). GV

Orbit Client must be configured to connect to the Densité server/service.

In a C&M project open in GV Orbit Client:

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 3.2: Configuration of Densité and RollCall Devices

1 Click Connections -> Densité in the main menu.

The Densité Configuration dialog is shown:

2 Enter the GV Orbit server IP address.

3 Select:

• ‘Lookup Service’; and

• ‘Densité REST’.

4 Enter the Username and Password (if not already set up) to access the

GV Orbit server (and hence the Densité service).

Note: These are not the same login credentials as those used when opening a GV Orbit project with GV Orbit Client.

Note: Densité service credentials are set up automatically if the Setup dialog ( Connections -> GV Server in main menu) was used when creating the C&M project.

5 Click OK .

GV Orbit Client connects to the Densité service on the GV Orbit server.

6 Add all Densité frames to the Densité service. (Refer to the Densité Manager service chapter in the GV Orbit Admin Guide in the

Step 3.2.4: View a Device Control Screen - Densité Devices

This step assumes that the Densité card is shown in the Network

window (see Step 3.2.3:

Network Window Setup For Densité Devices

Note: Densité cards can appear in the GV Orbit Client Network window if the card is:

• present in a Densité frame that has been added into the GV Orbit

Densité Manager service;

• supported by the GV Orbit server; and is

• accessible by the GV Orbit server over the network.

To add support for a card, see Step 5: Adding Support for Further

Densité Cards .

To access a Densité device control screen (device control panel) from the Network window:

1 Locate the target device in the Network window.

2 Right-click on the device and select ‘Control’.

Note: An informative message appears (bottom left of GV

Orbit Client) while the control screen is being accessed.

The Densité-protocol device’s control screen opens in a separate window (that is, not in the GV Orbit Client’s overall window) and may be obscured on your client PC’s screen. Check that this window is not behind the

GV Orbit Client window or other windows.

Click to close the

Densité device control panel.

Fig. 2-20: Example Densité Device Control Panel

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 3.3: Configuration of Other Devices

3 When all the required user device configuration is complete, close the control panel.

Right-click on any other device in the Network window to open its control screen, as required.

Step 3.3: Configuration of Other Devices

Devices in a GV Orbit system which may be configured via GV Orbit appear in the GV Orbit

Client Network window and present a ‘Control’ drop-down menu option:

• Right-click on such a device and select ‘Control’ to open their web page in GV Orbit.

Right-click on device and select ‘Control’

Fig. 2-21: Example GV Fabric Device Control Panel

Getting Started Steps

Step 4: Device Upgrade

GV Orbit Client Version 2.0.0

User Guide

Step 4: Device Upgrade

Lite



Professional



Enterprise



Introduction

This section describes how to upgrade software/firmware on a device using GV Orbit Client.

Upgrade packages for RollCall or Densité cards comprise a version of software and a version of firmware bundled together in a .zip file.

To upgrade a device (or unit), the Network window must be open and showing the system device to be upgraded. (See

Network Window Views , on page 45.)

Note:

Before starting, ensure that the upgrade package file is:

• accessible;

• for the correct RollCall or Densité card model; and is

• the correct version required.

Contact Grass Valley customer support for advice about upgrade packages.

•

Step 4.1: Upgrade RollCall-protocol Devices , on page 52.

•

Step 4.2: Upgrade Densité-protocol Devices , on page 56.

Also see

Change Functionality of a ‘Software-Defined Core’ Card , on page 59.

Step 4.1: Upgrade RollCall-protocol Devices

• Lite - Simple device upgrade is possible directly from GV Orbit Client.

• Professional and Enterprise - Simple device upgrade and advanced device upgrades are possible with the GVO-CFG-PRO option.

Simple Upgrade

Check the Current Software/Firmware Version

1 Open the Network window.

2 Locate the device to be upgraded, right-click on it and select Info .

A Details window is shown for the unit, displaying unit information which includes the device’s current version of software/firmware.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 4.1: Upgrade RollCall-protocol Devices

Device’s software/firmware version

Fig. 2-22: Unit Information in Details Window

3 Close the Details window.

Import Upgrade Packages

4 Right-click on the tree-view device item and select ‘Upgrade’.

The RollCall Upgrade window is shown. Any software/firmware upgrade packages that have been previously uploaded to the GV Orbit Client are shown listed on the left hand side. For a fresh install of GV Orbit Client, no packages are listed.

Fig. 2-23: RollCall Upgrade Window

5 Click Import Upgrade Package(s) and browse to the upgrade package to be uploaded. Select the package and click Open .

The package is imported into the GV Orbit Client.

After the package has been imported, it is listed under ‘Available Packages’ in the

RollCall Upgrade window.

Getting Started Steps

Step 4.1: Upgrade RollCall-protocol Devices

GV Orbit Client Version 2.0.0

User Guide

Upgrade the Device

6 Select a package in the ‘Available Packages’ list of the RollCall Upgrade window.

7 Select Upgrade All Files in the ‘Options’ pane to upgrade all files on the device, regardless of whether a file is the same on the device and in the upgrade package.

(Deselect Upgrade All Files for a quicker upgrade.)

Options pane

Fig. 2-24: RollCall Upgrade Window

8 Click the Upgrade button to start the upgrade of the device.

A message box appears informing you that the upgrade has started and will proceed in the background.

Click OK .

Note:

The user may continue using the GV Orbit Client project while the upgrade proceeds.

However, only one RollCall upgrade can be running at any one time .

The progress of the upgrade is reported bottom left in the GV Orbit Client window.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 4.1: Upgrade RollCall-protocol Devices

Bottom left

Messages as upgrade progresses

Final message

Fig. 2-25: Upgrade Progress Messages (Bottom left in GV Orbit Client window)

9 When the device has been upgraded, this is indicated by:

• a final message at the bottom of the GV Orbit Client window; and also by

• a pop-up notification message in the Windows TM system tray.

Check the Upgraded Software/Firmware Version

10 Right-click on the Network window upgraded-device item and select Info .

A Details window is shown displaying unit information.

11 Check that the device’s current (upgraded) version of software/firmware is correct.

Note:

If the Network window is being presented through an IP Proxy then a

GV Orbit server fail-over (in a GV Orbit Server cluster system) during an upgrade will cause a failed upgrade.

Getting Started Steps

Step 4.2: Upgrade Densité-protocol Devices

GV Orbit Client Version 2.0.0

User Guide

Step 4.2: Upgrade Densité-protocol Devices

• Lite - Simple device upgrade of Densité devices is not possible via the GV Orbit Client.

Note:

Densité modular devices may still be upgraded independently of GV Orbit

Client using Grass Valley’s iControl Solo product.

• Professional and Enterprise - Densité device upgrade is possible via GV Orbit Client with the GVO-CFG-PRO option, including upgrade of single and multiple Densité devices.

Device Upgrade (GV Orbit Professional and Enterprise only)

This sub-section assumes that the Densité card is shown in the Network window (see

Step

3.2.3: Network Window Setup For Densité Devices ).

Note: Densité cards can appear in the GV Orbit Client Network window if the card is:

• present in a Densité frame that has been added into the GV Orbit

Densité Manager service;

• supported by the GV Orbit server; and is

• accessible by the GV Orbit server over the network.

To add support for a card, see Step 5: Adding Support for Further

Densité Cards to be able to see the card to upgrade.

Check Current Device Software/Firmware Version

1 Open the Network window and locate the device to be upgraded.

2 Right-click on the device item to be upgraded and select Info .

A Details window is shown for the unit, displaying unit information which includes the device’s current version of software/firmware.

Device’s software/firmware version

Fig. 2-26: Unit Information in Details Window

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 4.2: Upgrade Densité-protocol Devices

3 Close the Details window.

Import Upgrade Packages

4 Right-click on the tree-view device item and select ‘Upgrade’.

The Densité Upgrade Manager window is shown.

Fig. 2-27: Densité Upgrade Manager

5 Click Upload Files...

and browse to the upgrade package to be uploaded.

Select the package and click Open .

A message window appears prompting the user to start the upload.

6 Click Upload in the Progress window.

Progress of the upload is shown in the window and the package is uploaded to the

Densité Upgrade Manager .

7 When complete, the Progress window shows 100% done,

‘Operation finished’:

Click Close .

8 Verify the uploaded package is present in the Densité

Fig. 2-28: Progress Window - Upgrade Package 100%

Upgrade Manager window by clicking in the ‘Available package’ column and looking in the drop-down list.

Getting Started Steps

Step 4.2: Upgrade Densité-protocol Devices

GV Orbit Client Version 2.0.0

User Guide

Note: After an upgrade package has been uploaded, it is available in a dropdown box in the ‘Available Package’ column, in all rows for Densité devices compatible with the newly-uploaded package.

For example, for an IPG-3901 package, check in any IPG-3901 device row.

Upgrade the Device

In the Densité Upgrade Manager window, in the row for the device to be upgraded:

9 Select an upgrade package in the ‘Available Package’ column’s drop-down list.

Fig. 2-29: Upgrade Window with Selected Upgrade Package

10 Click the Upgrade button to start the upgrade of the device.

An Upgrade Confirmation message box appears.

11 Click Yes to start the upgrade.

Progress is reported in the ‘Install

Progress’ column as a progress bar and a percentage (%):

When done, a ‘Finished 100%’ message appears in the ‘Install progress’ column.

Upgraded software/firmware version on device is shown

Fig. 2-30: Upgrade ‘Finished 100%’

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Change Functionality of a ‘Software-Defined Core’ Card

12 Close the Densité Upgrade Manager window.

Check Software/Firmware Version on Upgraded Device

13 In the Network window, right-click on the upgraded-device item and select Info .

A Details window is shown for the device/unit.

14 Check that the newly-upgraded device software/firmware version is correct.

Note: The Densité Upgrade Manager can upgrade multiple devices.

Change Functionality of a ‘Software-Defined Core’ Card

Grass Valley offer a range of cards which have a software-defined core, enabling a user to change the functionality of a card with core packages and licenses. GV Orbit Client enables a user to change such a ‘software-defined core’ card’s functionality.

Note: Supported software-defined core cards include:

• UCP-3901 and IQ-UCP cards, with various core packages, including Essence Processing (EP) cores and Multiviewer (MV) cores.

See the documentation on the respective cards for further information and instructions on how to add licenses etc.

Note: License a card first before loading a core package into the card.

If a core package is loaded but a card is not licensed, then default,

‘base’ functionality results. See the documentation on the respective card for information.

To change a card’s functionality, use the ‘upgrade’ mechanism in GV Orbit Client:

1 Locate the software-defined core card in the Network window.

Fig. 2-31: Software-Defined Core Device in Network Window

2 Right-click on the card item in the tree-view and select ‘Upgrade’.

The RollCall Upgrade window is shown for the card. The window shows:

• the core package currently in use by the card; and

• all available (imported) core packages.

Getting Started Steps

Change Functionality of a ‘Software-Defined Core’ Card

See Figure 2-32.

Available core packages

GV Orbit Client Version 2.0.0

User Guide

Current software-defined core being used by the card.

Fig. 2-32: RollCall Upgrade Window - Available Cores

To import further core packages:

3 Import the core package in a similar way to an upgrade package (see Step 4.1: Upgrade

RollCall-protocol Devices , on page 52).

To load an available (already-imported) core package into the card and change card functionality:

4 Select an available core package and click Upgrade . The procedure is similar to upgrading a card (see

Step 4.1: Upgrade RollCall-protocol Devices , on page 52).

The new core package is placed on the card; the card reboots and then adopts the functionality of the new core package if the card is licensed.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 5: Adding Support for Further Densité Cards

Lite Professional



Enterprise



Introduction

GV Orbit fully supports all Densité cards. GV Orbit Professional and Enterprise shi p with native support for many Densité cards; for other cards, support needs to be added to your

GV Orbit server. This section describes how to add support for Densité cards to your

GV Orbit server.

Support is added by uploading the requisite Densité card software package. Once uploaded, the GV Orbit server can recognize the cards and they may be integrated into the

Network window.

Carry out this procedure to add or to update support of a Densité card.

Add or Update Densité Card Support

Many Densité cards are automatically recognized by GV Orbit. However, some Densité cards may not show in the Network window, even though they are physically installed in a

Densité frame. For example, a frame’s controller card may be shown but one or more cards in the same frame are not shown (in the tree-view nor list-view). To make such cards available, the corresponding card software packages must be uploaded through the

Densité Upgrade Manager tool.

Note: Refer to GV Orbit release notes documentation for a list of natively supported Densité cards. See

Documentation , on page 19.)

Prerequisite:

• All Densité frames are added to the Densité Manager service on the GV Orbit server.

(Refer to the Densité Manager service chapter in the GV Orbit Admin Guide . See

• Software package are available for each Densité card type to be added/updated.

(See each separate card documentation for how to obtain each software package.)

The procedure is similar to upgrading Densité cards (see

Step 4.2: Upgrade Densitéprotocol Devices ):

1 Locate a Densité frame item in the Network window tree-view and expand it to show all available cards.

2 If one or more cards are not shown in the Network window tree-view, right-click on a fitted card item (for example, on the frame controller card item) and select ‘Upgrade’.

The Densité Upgrade Manager tool is opened showing all the cards in the Densité frame. Some cards may be grayed-out.

For each Densité card type for which support is to be added/updated:

Getting Started Steps

Add or Update Densité Card Support

GV Orbit Client Version 2.0.0

User Guide

3 Import the card’s software package.

(See Import Upgrade Packages for how to do this.)

4 Upgrade each card.

(See Upgrade the Device for how to do this).

After a card type has been upgraded, it should appear in the Densité Upgrade Manager tool and not be grayed-out.

Support for the card has now been added to the GV Orbit server.

When the support for all cards has been added:

5 Close the Densité Upgrade Manager window.

Support for the Densité cards has now been added to the GV Orbit server and the cards are displayed in the GV Orbit Client’s Network window.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 6: Multiviewer Project

Lite



Professional



Enterprise



Introduction

This section is applicable to GV Orbit Client and multiviewer applications with single multiviewers that use the GV Orbit ‘Multiviewer’ project type.

Note: A GV Orbit ‘Multiviewer’ project type is typically for singlemultiviewer designs.

For video walls designs that are served by a cluster of multiviewers

(MV Cluster), then use the GV Orbit ‘Clustered Multiviewer’ project

type (described in Chapter 13, Multiviewer Cluster , on page 645

onwards).

This section describes a simple edit to a GV Orbit (single-multiviewer) ‘Multiviewer’ project pulled from a multiviewer (MV-8 series or IQ-MV series multiviewer). The simple edit changes the appearance of the video wall and the project is pushed back to the device.

Note: GV Orbit ‘Multiviewer’ projects are pushed/pulled to/from a compatible (single) multiviewer device rather than to/from a GV Orbit server.

Simple Multiviewer Project Editing Example

Pull Project and Open

1 Open GV Orbit Client at the initial screen and click New Project .

The New Project dialog is shown.

2 Select Connected

Multiviewer Project type.

3 Browse into a new, empty folder (into which project information will be placed).

4 Click Choose .

5 Click Next .

A list of available multiviewers is shown.

Getting Started Steps

Simple Multiviewer Project Editing Example

GV Orbit Client Version 2.0.0

User Guide

Fig. 2-33: Select Multiviewer to Connect To

Note: The IP network used needs to support multicast for automatic discovery of devices to occur (for example, for listing available multiviewers).

6 Select the multiviewer to connect to and click OK .

GV Orbit Client connects to the multiviewer, pulls the GV Orbit project from it, attempts to open the project, and shows the login screen.

7 Enter the correct User name and Password for the accessing the GV Orbit project.

Note: The default login for new projects is ‘admin’ ‘admin’.

8 Click Login .

The project is opened and the multiviewer project Home Screen is shown.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Simple Multiviewer Project Editing Example

Folder path where project is stored on the client PC.

Name of GV Orbit project (pulled from multiviewer)

Fig. 2-34: Multiviewer Project Home Screen

The GV Orbit multiviewer project has been pulled from the target multiviewer device, locally stored on the client PC, and opened in GV Orbit Client.

The multiviewer video wall design may now be edited in GV Orbit Client.

Edit the Multiviewer Project

9 Click on the large Walls icon, and select one of the wall items that is shown listed.

The multiviewer video wall design is opened in a tab in the overall GV Orbit Client

window. See Figure 2-35.

Getting Started Steps

Simple Multiviewer Project Editing Example

GV Orbit Client Version 2.0.0

User Guide

Run Mode / Design Mode icon (GV Orbit Client is shown in Design Mode )

Wall tab

Video Wall design

Video tiles

Properties Box

Fig. 2-35: Example Video Wall Tab in Wall Editor

The Wall tab is the stage on which a Wall is:

• designed and edited (in GV Orbit Client Design mode); and

• may be run and viewed (in GV Orbit Client Run mode).

Although a video wall is fully deployed when running on a compatible multiviewer device.

10 Click the Run Mode / Design Mode tool bar icon to select ‘Design Mode’.

Note:

Clicking the Run Mode / Design Mode tool bar icon toggles between ‘Run’ and ‘Design’ modes of GV Orbit Client.

Click to exit Run Mode a) Icon appearance when in

Click to enter Run Mode

Run Mode b) Icon appearance when in Design Mode

Fig. 2-36: Run Mode / Design Mode Tool Bar Icon

Note:

• In Design Mode , a project may be edited (for example, a video wall may be modified).

• In Run Mode , a project monitors log and alarm data and generates display screens in real-time.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Simple Multiviewer Project Editing Example

This example edit will do a simple change to the video wall:

11 Click on one of the video tiles on the wall to select it. For example, the top-left video tile.

12 In the Properties Box , change the Preferences -> Type property value to ‘Analogue

Clock’ via the drop-down menu.

The selected tile changes to a round-faced clock within the Wall tab.

Selected video tile Round-faced, analogue clock tile Analogue clock type

Fig. 2-37: Edited Wall Design

13 Click Project -> Save Project to save the whole project locally, including the video wall design.

Push Project Back to Multiviewer

14 Click Project -> Push in the main menu.

The Choose Projects dialog is shown.

Getting Started Steps

Simple Multiviewer Project Editing Example

GV Orbit Client Version 2.0.0

User Guide

Project selected

Hint:

Hover on a Project item to see local folder path

Fig. 2-38: Choose Projects Dialog

15 Select just the project to push to the multiviewer.

16 Click OK .

The selected project is pushed back to the multiviewer.

The edited video wall is then used and shown by the multiviewer device.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 7: Control and Monitoring Project Setup (Professional/Enterprise)

Step 7: Control and Monitoring Project Setup

(Professional/Enterprise)

Lite Professional



Enterprise



Introduction

This section is applicable to GV Orbit Professional and Enterprise only. It describes setting up a new ‘Control and Monitoring’ project (C&M project), which is the main project type applicable to GV Orbit Professional and Enterprise . Following its setting up, a C&M project is ready for use. For example, custom graphical operator screens etc. can be designed, created and used.

All C&M projects are centrally stored in and used from repositories on the GV Orbit server

(one project per repository). The GV Orbit Client application needs to be configured to communicate with the GV Orbit server(s) (see

Step 7.2: C&M Setup Dialog , on page 70). A

project is loaded by GV Orbit Client from a server repository and stored locally on the client

PC.

Note:

GV Orbit Client requires network access to one or more GV Orbit servers running configured GV Orbit services.

•

Step 7.1: New C&M Project , on page 69.

•

Step 7.2: C&M Setup Dialog , on page 70.

•

Step 7.3: Further Setup , on page 76.

•

Step 7.4: Saving and Pushing a Project , on page 80.

Step 7.1: New C&M Project

From the GV Orbit Client Initial Screen :

1 Click New Project.

The New Project dialog is shown.

2 Select the C&M project type.

3 Click Browse and browse to a folder where the project will be placed.

Click Choose .

4 Enter a name for the new project.

5 Click OK .

And, if prompted, answer Yes to create a directory.

The Setup

dialog is shown. See Step

7.2: C&M Setup Dialog , on page 70.

Getting Started Steps

Step 7.2: C&M Setup Dialog

GV Orbit Client Version 2.0.0

User Guide

Fig. 2-39: C&M Project Setup Dialog

The C&M Setup dialog provides a quick way to enter key project parameters for a project.

The dialog is shown automatically when creating a new C&M project. And it can be accessed when an existing C&M project is open by clicking Connections -> GV Server in the main menu.

Note:

Some key project parameters are entered in the Setup dialog and used for the project settings. Some settings may be subsequently edited by the user,

if required. Refer to Step 7.3.1: Project Variables (Project -> Edit Variables) , on page 76.

Server IP Address(es)

1 Enter the IP address of the GV Orbit server into the Server 1 IP text box.

For a GV Orbit Server Cluster system, enter the IP address of one server. The second server’s address will be discovered automatically in the steps below.

Check the address is correct.

The GV Orbit Client attempts to connect to the server and performs some basic system tests.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 7.2: C&M Setup Dialog

Note: Basic System Tests : a. Connect to the GV Orbit server.

A good connection status is shown with a green light indicator. b. Find out other GV Orbit system information from the server.

c. Fill out settings in the Setup dialog.

For example:

• Client Domain number being used (default is 100).

• Available Repositories on the server.

• IP address of any second GV Orbit server; and any IP address being commonly used by the servers (‘Virtual IP’).

The resulting connection status from the basic system tests is indicated in a console

pane showing any system messages issued. See Figure 2-40a.

Getting Started Steps

Step 7.2: C&M Setup Dialog

Console pane

System messages from basic system tests.

a) Single GV Orbit Server

IP addresses automatically added

GV Orbit Client Version 2.0.0

User Guide

Green indicates GV

Orbit Client successfully connected to the

GV Orbit server.

Green indicates GV

Orbit Client successfully connected to the

GV Orbit servers and virtual IP address detected.

72 b) GV Orbit Server Cluster

Fig. 2-40: C&M Project Setup Dialog: a) Single GV Orbit Server; b) GV Orbit Server Cluster

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 7.2: C&M Setup Dialog

Select a Repository

Note: Repository :

Projects may be locally stored on the client PC but, for deployment, a C&M project must be saved to the GV Orbit server (Pushed) into a Repository , one project per Repository . Multiple clients can access the same project.

Note:

The Repository Manager service, running on the GV Orbit server, can be configured on the server and each repository may be set up from there.

Alternatively, a New repository may be created from the C&M Project’s Setup dialog.

Available Repositories are listed in a drop-down box in the Setup dialog.

Note:

Pull a project from a Repository to load the project from a server.

Push a project to a Repository to save it back to the GV Orbit server.

2 In the Setup dialog, click New .

The Create Repository dialog is shown:

3 Enter a name for the new repository and click OK .

Alternatively, to select an existing repository:

4 Select a Repository in the ‘Repository’ drop-down list in the Setup dialog.

The C&M project will use the project from this Repository .

Click New to create a new

Repository

Fig. 2-41: Select a Repository in Setup Dialog

System Re-Test

5 Click System Test to redo the basic system tests.

Getting Started Steps

Step 7.2: C&M Setup Dialog

GV Orbit Client Version 2.0.0

User Guide

For the basic system test, GV Orbit Client performs a:

• ping to each server;

• client-server communication check;

• services check on the server; and

• check of service Domain configurations (Monitoring and Log Server services).

The console pane in the Setup dialog may have shown some red messages which highlight differences between entered dialog settings and those of the GV Orbit system connected to. (For example, a Client Domain number difference.)

Re-do the basic system tests and the red messages should clear.

Single GV Orbit server GV Orbit servers and Virtual IP Address

System Test clear console output a) Single GV Orbit Server b) GV Orbit Server Cluster

Fig. 2-42: System Test Re-done and Console Output OK: a) Single GV Orbit Server. b) GV Orbit Server Cluster.

Apply Settings

6 In the Setup dialog, click Apply to apply these settings to the project.

Click OK to any pop-up message.

7 Click Close to close the dialog.

The GV Orbit pulls the project etc. from the repository and shows the Home Screen .

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 7.2: C&M Setup Dialog

Note:

When connecting to a Repository , the user may be prompted to Pull a project from a Repository , so as to retrieve a project from the server.

Pull a project in order to either:

• edit the project locally (any existing local project is overwritten); or

• run the project locally (for example, to run operator screens).

Do not Pull if a local project has been created/changed and it needs to be put into a Repository . This requires a Push to a repository.

Getting Started Steps

Step 7.3: Further Setup

GV Orbit Client Version 2.0.0

User Guide

Step 7.3: Further Setup

Following initial set up, a C&M project is ready for use. Project settings and variables are set up from the settings in a C&M Project’s Setup window.

This sub-section describes how to adjust the project settings (including project variables) further, if any parameters need changing for some reason.

Step 7.3.1: Project Variables (Project -> Edit Variables)

C&M projects have a set of project variables that are set up when using the C&M Project

Setup window to establish connection to a GV Orbit server. This done as part of creating a new C&M Project. (The Setup window is also accessed by selecting Connections -> GV

Server in the main menu.)

The Project Variables enable GV Orbit Client workflows, and other user graphical screens, to communicate with GV Orbit services and server(s).

Note:

Most Project Variables hold default values consistent with the default

GV Orbit server and GV Orbit services settings. Do not change the values of these variables unless the items have been changed from their default.

To access the project variables from the project Home Screen :

1 Click Project -> Edit Variables...

in the main menu.

A Variables window is shown for the C&M project.

Fig. 2-43: C&M Project Variables Window

Parameter

GVOC IP

GVOC Launcher

Description

Virtual IP address of the GV Orbit server cluster.

Path to launcher for GV Orbit Control Client.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 7.3: Further Setup

Parameter

IP Network

Routing Address

Server IP 1

Server IP 2

Show External IDs

Description

Network file name for IP endpoint configuration.

RollCall ‘Control’ address of Routing Service on GV Orbit server(s).

GV Orbit Server 1 IP address.

GV Orbit Server 2 IP address.

The GV Orbit Client uses the External IDs set in GV Orbit Control for router control. Certain control protocols require that the numbering of external IDs must be contiguous.

False: GV Orbit Client remaps the External ID's used by GV Orbit

Control into its own list of contiguous internal ID's. GV Orbit Client follows name changes to existing External ID's, however adding devices to GV Orbit or removing devices from GV Orbit may cause a shift in the internal ID numbering which can result in incorrect routing.

When this occurs, the ID shown in GV Orbit Client Routing Behaviors will no longer match those used in GV Orbit Client as there are two separate ID lists which are no longer coherent.

This is the default for a project migrated to GV Orbit version 2.0.0 and above, for backwards compatibility.

True: GV Orbit Client uses the GV Orbit Control External ID's. You can insert or remove devices without any impact on existing IDs. The GV

Orbit Client will follow name changes associated with External IDs.

Note: For a multiviewer project there are fewer variables.

2 Click OK when project-variable value changes have been done.

3 Click Project -> Save Project in the main menu to save the project locally to disk.

4 Push the project to the repository when all changes are done.

Custom Project Variables

The Variables window also allows a user to create custom project variables for their own use. For example, the RollCall addresses of system devices, a company name, the TV channel/studio name, etc. These may each be set up as custom project variables and used in custom control and monitoring screens. Custom project variables can be created and deleted.

CAUTION

Do not delete any of the C&M project variables presented here.

Step 7.3.2: Client Domain Number (Connections -> GVOP)

To configure the Client Domain for the GV Orbit Client to use for the project:

1 Click Connections -> GVOP in the main menu.

The GV Orchestration Protocol dialog is shown.

Getting Started Steps

Step 7.3: Further Setup

GV Orbit Client Version 2.0.0

User Guide

Set the Client Domain number for the project to use. (Default is100.)

Select for multicast discovery of server IP addresses.

(Default is unicast discovery.)

Click to add a new IP address (for unicast discovery).

Select/deselect IP interfaces of the client PC to be used by GV Orbit

Client.

Set multicast packet ‘Time to Live’

(TTL) - defines the number of “hops” that a network multicast message is allowed to do between IP network routers. The TTL value can limit the distance these messages travel within a network.

Fig. 2-44: GV Orchestration Protocol Dialog

2 Set the Domain number of the Client Domain that the C&M project will use. (Default is

100.)

3 Other project parameters can be changed in the dialog, see Figure 2-44.

4 Click OK to finish and close the dialog.

Step 7.3.3: Configure Network Window for RollCall-protocol Devices

5 Click Connections -> RollCall -> Network Map in the main menu.

The Open Network dialog is shown.

GV Orbit Client Version 2.0.0

User Guide

Getting Started Steps

Step 7.3: Further Setup

IP address of a server running a IP Proxy service, typically, a GV Orbit server.

Fig. 2-45: Open Network Dialog

6 Enter the IP address of the server running an IP Proxy service as ‘Primary Address’.

Typically, this is the IP address of a GV Orbit server.

7 For a GV Orbit Server Cluster system, select Enable Redundancy and enter the IP address of the second GV Orbit server.

8 Click OK to finish and close the dialog.

Step 7.3.4: Configure Network Window for Densité-protocol Devices

9 Click Connections -> Densité in the main menu.

The iControl/Densité Configuration dialog is shown.

Getting Started Steps

Step 7.4: Saving and Pushing a Project

GV Orbit Client Version 2.0.0

User Guide

IP address(es) of a server running a

Densité Manager service, typically, a

GV Orbit server.

Click Add to add a new IP address.

Fig. 2-46: iControl/Densité Configuration Dialog

10 Click Add and enter the IP address(es) of GV Orbit server(s) (which run a Densité

Manager service), or add the IP address of a server.

11 Select ‘Lookup Service’ and ‘Densité REST’.

12 Enter the Username and Password to access the Densité Manager service.

13 Click OK to finish and close the dialog.

Finally:

14 Click Project -> Save Project in the main menu to save the project locally.

15 Push the project to the repository when all changes are done. See

Step 7.4: Saving and

Pushing a Project , on page 80.

Step 7.4: Saving and Pushing a Project

Save Project (Locally)

To save a project locally to the folder on the client PC:

• Click Project -> Save Project in the main menu.

Push Project (Save to Server)

To push a project back into a repository (on the GV Orbit server):

• Click Project -> Push

. (See Step 2.2.2: Push Project (Save to Server) , on page 41.)

In the Choose Project dialog, select the project to be pushed and click OK .

Pull Project (Load from Server)

To pull a project from a repository (on the GV Orbit server):

• Click Project -> Pull in the main menu.

GV Orbit Client Version 2.0.0

User Guide

Close Project

To close a project that is open in GV Orbit Client:

• Click Project -> Close Project in the main menu.

Getting Started Steps

Step 7.4: Saving and Pushing a Project

Getting Started Steps

Step 7.4: Saving and Pushing a Project

GV Orbit Client Version 2.0.0

User Guide

Summary contents of this chapter:

Home Screen

Project Home Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Home Screen Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Project Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Network Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

History Window (Alarm History) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Workflow Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Network Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

What is the Network Window? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Network Window List-View Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Network Window Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Alarm List - Live Alarms/Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Alarm History for a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Alarm Masking (Professional and Enterprise) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

History Window (Alarm History) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

View Alarm History for System-wide Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Search Parameters Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Graphical Routing Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

(1) IP Configuration and Spreadsheet Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

(2) Logical Level Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

(3) Topology Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

(4) Logical Device Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

(5) Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

(6) Panel Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

(7) GPIO Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

(8) Bulk Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

(9) Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

(10) Router Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

(11) Alias Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

(12) System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

(13) Path Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Bulk Routing Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Open Bulk Routing Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Bulk Routing Panel - List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Bulk Routing Panel Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Routing Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Access Routing Service Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

To Take a Routing Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

To Recall a Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

GV Orbit Server Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Home Screen GV Orbit Client Version 2.0.0

User Guide

Login From GV Orbit Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Login from a Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Server Admin Login Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

GV Orbit Server Home Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Accessing Services Configuration Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

View Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Simple Custom Monitoring Screen Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Step 1: Create a New Monitoring Screen Schematic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Step 2: Add Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Step 3: Save and Push Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Step 4: Run Custom Monitoring Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Main Menu and Tool Bar Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Main Menu Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Main Tool Bar Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Common Operations in Graphic Editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Selection/De-Selection of Objects in Graphic Editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Select All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Selection Etc. in Groups of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Project Home Screen

Lite



Professional



Enterprise



Home Screen Windows

The appearance of the GV Orbit Client project Home Screen varies according to project type and according to which GV Orbit Client windows are enabled and being shown. Use tool bar icons to show/hide windows.

Some tool bar icons to show/hide windows in the Home Screen :

• Alarm History window icon

•

• Project window icon

Network window

•

Properties window (shown when a C&M screen tab is selected)

Workflow window

Workflow tab

History Window (Alarm History)

tab

C&M Screen tab

Project Window

Network Window

Graphical Routing Workflow tab selected and a graphical routing

workflow stage is shown.

Fig. 3-1: GV Orbit Client Project Home Screen Windows

Home Screen

Home Screen Windows

GV Orbit Client Version 2.0.0

User Guide

Table 3-1: Home Screen Windows

Window

Project

Description

A tree view of projects opened by the GV Orbit Client.

Allows users to access aspects of the current project, or to load another project.

Network A view of devices/frames/services etc. in a GV Orbit system, presented in a tree-view or a list-view. A user can access device information and alarms.

Alarm History A list of alarms that have occurred across the system over time.

Properties

Workflow

Shows the properties of the selected graphical widget when designing a graphical C&M project.

A graphical presentation of all the tasks and functions available in GV Orbit.

Click on an icon to access a task or a function.

See

Project Window , on page 87.

Network Window , on page 88.

History Window (Alarm History) , on page 112.

Properties Window , on page 92.

Graphical Routing Workflow , on page 116.

Close All Windows

To close all windows and just see a default workflow:

• Click Window -> Close All in the main menu.

GV Orbit Client Version 2.0.0

User Guide

Project Window

The Project window lists the project currently open and any projects previously opened by the GV Orbit Client on the client PC.

The currently-open project is expandable in a tree view to show the various project items.

The user can access and manage different aspects/functions of the project from this tree view item.

Currently-open project

Project is expanded

Home Screen

Project Window

Project Tree-Items

Project items seen when a project is expanded include: Fig. 3-2: Project Window

• Components - Graphical custom components that appear on GV Orbit Client graphical control and monitoring screens.

• Networks - IP End-point configuration files, used in IP routing control set up.

• Panels - Soft XY Router control panels, created with a wizard and user-customizable.

• Resources - Imported resource items used in the project (for example, logo images etc.).

• Screens - C&M project user-defined graphical control/monitoring screens.

• Themes - The appearance of each graphical element on a GV Orbit custom graphical screen (multiviewer video wall screen, or C&M project control and monitoring screen) can have a style applied to it. A theme is a set of styles that can be applied to a project.

• Workflows - Workflow screen.

• configuration.prj

- The GV Orbit project file. Select this file when opening an existing project in GV Orbit Client. Do not edit this file.

• db.users

- Project users, user roles and their associated permissions can be managed.

New user names and logins etc. can be set up.

• Grids - Imported tile-grid layouts for all multiviewer projects.

• Tiles - Video wall tile designs for all multiviewer projects.

• Rooms - Video wall designs for ‘Clustered Multiviewer’ projects.

• Walls - Video wall designs for ‘Multiviewer’ projects.

Note:

Some project items are also accessible via icons in the routing workflow window (see

Graphical Routing Workflow , on page 116

Note:

Some project items may be specific to certain project types.

Home Screen

Network Window

GV Orbit Client Version 2.0.0

User Guide

Project Window Actions

Right-click on a Project window tree-view item to open, import, or create a new item.

For example, right click on:

• Screens - Select New to create a new user screen in a C&M project.

• Walls - Select New to create a new video wall in a single-multiviewer project.

• Resources - Select Import File(s) to import an image file into a project.

• db.users

• Select Open to open the User Management window in a tab to set up users and roles.

• Select Import user database to import users from another project.

• < Project Name > - Select Rename project to rename the project.

Network Window

The Network window shows a tree-view or a list-view of devices/frames/services etc. in a

GV Orbit system. A user can access control screens, information and alarms about these

items from the window. For more information, see Network Window for more information.

Note:

To set up the Network

window for a project, see Network Window Views , on page 45 onwards.

Show/Hide Network Window

The Network

window may be shown/hidden using a main tool bar icon, see Figure 3-8.

Click icon to hide/show the Network window (toggles).

Fig. 3-3: Network Window Hide/Show

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Network Window a) Tree-View b) List-View

Fig. 3-4: Network Window Examples: a) Tree-View; b) List-View.

Network Window Actions

Locate a device in the Network window and right-click on the item. The following actions are possible in GV Orbit:

• Lite , Professional and Enterprise :

•

Device Information - View information about a device.

•

Card Parameters

- View Densité-protocol device parameters.

•

Device Control - View and change device configuration settings. (

Lite : RollCall devices only.)

•

Upgrade Device

- Upgrade (or downgrade) device software/firmware.

• And for Professional and Enterprise only:

•

Alarm List - Live Alarms/Status - View a list of a device’s live status and alarms.

•

Alarm History for a Device - View the alarm history of a device.

•

Alarm Masking (Professional and Enterprise) - Mask device alarms.

Home Screen

History Window (Alarm History)

GV Orbit Client Version 2.0.0

User Guide

History Window (Alarm History)

Lite Professional



Enterprise



The GV Orbit Client History window can show the history of system-wide alarms and status messages which are read from the Event Logging service on the GV Orbit server.

Note:

The History window is similar to the window shown for

Alarm History for a Device , on page 107 .

For more information, see

History Window (Alarm History) , on page 112.

View Alarm History for System-wide Alarms

To view the Alarm History for GV Orbit system-wide alarms:

1 Click the Alarm History icon in the main tool bar.

The History window appears in a tab.

Note: The tab shows no specific device address when showing system-wide alarms.

Select the History tab to view it.

GV Orbit Client Version 2.0.0

User Guide

Home Screen

History Window (Alarm History)

Fig. 3-5: Alarm History Window Example

Home Screen

Properties Window

GV Orbit Client Version 2.0.0

User Guide

Properties Window

Lite Professional



Enterprise



The Properties window shows the properties of a selected graphical widget or on-screen item when designing/editing a C&M screen in GV Orbit Client in ‘Design’ mode. The window may be shown when a C&M screen tab, or a multiviewer video wall, or other graphical GV Orbit project item is selected.

Run/Design Mode icon indicates GV Orbit Client is in ‘Design’ mode for graphical editing and design.

Properties Window

Selected (Alarm List) widget and its corresponding properties shown in Properties window a) Example C&M Screen Running in ‘Design’ mode in GV Orbit Client b) Example C&M Screen Running in GV Orbit Client

Alarm List widget showing live alarms in a system

Fig. 3-6: Properties Window Example: a) In Design Mode; b) In Run Mode.

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Workflow Window

Lite Professional



Enterprise



Note:

A Workflow window may be visible in GV Orbit Lite but it is not applicable to the GV Orbit Lite product version.

A workflow window shows a graphical representation of all the tasks and functions available in GV Orbit Professional and Enterprise systems. The Workflow window is the stage which presents all the tasks and functions the system has to offer to the GV Orbit

Client user. Click on a workflow icon for direct access to a task or a function.

View WorkFlow Stage

To view the Workflow stage:

1 Click the icon in the tool bar.

Workflow stage is then shown in a tab.

2 Select the workflow tab (if it is not already selected) to view it.

The workflow in Figure 3-7 is available to all new projects.

Workflow window icon workflow.wfl tab Workflow stage

Click on an icon to access a task item, see

Graphical Routing Workflow , on page 116.

Click on a server icon to access a GV Orbit server.

Click on an icon to access GV Orbit project functions in GV

Orbit Client, see

Project Window , on page 87.

Fig. 3-7: Graphical Routing Workflow Stage

Home Screen

Workflow Window

GV Orbit Client Version 2.0.0

User Guide

The graphical Workflow stage makes it easy to understand how tasks and functions are related and each icon provides direct access to the task/function it represents.

The workflow is optimized for carrying out the system configuration required:

• when re-purposing an existing routing infrastructure; or

• for the steps to set up a fresh, new routing environment.

Routing configuration and control is done via the GV Orbit Control application running on a

GV Orbit server, which supports Grass Valley NP0017 and SW-P-08 protocols. Both IP and

SDI routing etc. may be controlled. The GV Orbit Client communicates with the GV Orbit

Control service via the GV Orbit Control Client, launched automatically from the GV Orbit

Client.

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Network Window

What is the Network Window?

The Network window shows a tree-view or a list-view of devices/frames/services etc. in a

GV Orbit system. A user can access control screens, information and alarms about these items from the window.

Note:

To set up the Network

window for a project, see Network Window Views , on page 45 onwards.

(See Step 3.2.1: Network Window Setup For RollCall Devices , on page 46;

Step 3.2.2: View a Device Control Screen - RollCall Devices , on page 48; Step

3.2.3: Network Window Setup For Densité Devices

, on page 48; and Step

3.2.4: View a Device Control Screen - Densité Devices , on page 50.)

Note: Automatically discovered devices:

For devices that are automatically discoverable by a GV Orbit system, these are shown in the Network window. For example, GV Fabric IP switch.

Show/Hide Network Window

The Network

window may be shown/hidden using a main tool bar icon, see Figure 3-8.

Click icon to hide/show the Network window (toggles).

Fig. 3-8: Network Window Hide/Show

Tree-View and List-View

The tree-view and list-view forms of the Network

window are shown in Figure 3-9.

The tree-view presents a hierarchical view of system devices/units/frames/services. See

Figure 3-9a. The tree-view’s expand/collapse controls are presented in Figure 3-9a.

The list-view is a flattened view, listing all system devices/units/frames/services. See

Figure 3-9b. The list may be filtered, see Network Window List-View Filter

for a description of the list-view filter controls.

Home Screen

Network Window List-View Filter

GV Orbit Client Version 2.0.0

User Guide

Click to expand all of the tree-view.

Click to expand the selected part of the tree-view.

Click to collapse all of the tree-view.

Click to collapse the selected part of the tree-view.

Click to show List-View

Click to show Tree-View

List-view filter controls, see

Network Window List-View Filter

a) Tree-View b) List-View

Fig. 3-9: Network Window: a) Tree-View; b) List-View.

Network Window List-View Filter

In the Network window, the displaying of items in the list-view can be filtered. Filtering can be done:

• with a text string; and/or

• by card type; and/or

• by alarm state.

The filter controls are shown in Figure 3-10.

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Network Window List-View Filter

Filter text box

Filter icon

Filter drop-down menu

Filter on Device Type

Filter on Alarm State

Clear Filter text box filtering

Clear All Filtering

Fig. 3-10: List-View Filter Controls

Filter Example 1: Filter List Item Name

To filter the Network window list-view for a particular device by its name:

1 Enter a fragment of text in the Filter text box. For example, “UCP or “XIO”.

The displayed names are those containing the entered text. See Figure 3-11b or c.

a) Unfiltered.

b) Filtered on “UCP” c) Filtered on “XIO”

Fig. 3-11: List-View Filtered Names on Text

2 Click on the Filter icon and select ‘Clear Filter’.

Home Screen

Network Window List-View Filter

The text box is cleared and the text--box filtering is cleared.

Filter Example 2: Filter Device Type and then Alarm State

With all filters cleared, to filter on a device type and then their alarm states:

1 Click on the Filter icon and select ‘RollCall’.

RollCall-protocol devices are shown. See Figure 3-12a.

2 Click on the Filter icon and select ‘Minor.

‘Minor Warning’ RollCall-protocol devices are shown. See Figure 3-12c.

Filter icon indicates some filtering is active

GV Orbit Client Version 2.0.0

User Guide

98 a) Filter RollCall-protocol devices b) Select to Show Minor Warning

Alarm States

Fig. 3-12: Filter on Device Type and then Alarm State

To clear the alarms:

3 Click on the Filter icon and select ‘Clear All Filters’.

All filters are cleared and all devices are shown.

c) Minor Warning RollCallprotocol devices shown

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Network Window Actions

Locate a device in the Network window and right-click on the item.

The following actions are possible in GV Orbit:

• Lite , Professional and Enterprise :

•

Device Information - View information about a device.

•

Card Parameters

- View Densité-protocol device parameters.

•

Device Control - View and change device configuration settings. (

Lite : RollCall devices only.)

•

Upgrade Device

- Upgrade (or downgrade) device software/firmware.

• And for Professional and Enterprise only:

•

Alarm List - Live Alarms/Status - View a list of a devices’ live status and alarms.

•

Alarm History for a Device - View the alarm history of a device.

•

Alarm Masking (Professional and Enterprise) - Mask device alarms.

Device Information

To inspect device information from the Network window (tree-view or list-view):

1 Right-click on a device and select ‘Info’.

Device information is shown in a Details pop-up window.

Home Screen

Network Window Actions

GV Orbit Client Version 2.0.0

User Guide a) RollCall-protocol Device - Details window b) Densité-protocol Device - Details window

Fig. 3-13: Device Info - Details Pop-up Windows

Card Parameters

To view a Densité-protocol device’s parameter settings from the Network window:

1 Right-click on a Densité-protocol device and select ‘Card Parameters ’ .

A summary of the device’s parameter settings is shown in a tab. See Figure 3-14.

100

GV Orbit Client Version 2.0.0

User Guide

Right-click and select ‘Card Parameters’, a summary of card parameters is shown in a tab

Home Screen

Network Window Actions

Fig. 3-14: Card Parameters Tab

2 Click on a column heading to sort the listed parameters on a column.

3 Use the filter controls to restrict the shown listed items. See Figure 3-15.

Example: Filtering on parameter name containing ‘Resp’

Fig. 3-15: Example Filtered Card Parameters

4 Read/Write card parameters can be entered via the ‘Current Value’ column.

101

Home Screen

Network Window Actions

GV Orbit Client Version 2.0.0

User Guide

Device Control

To inspect a device’s configuration settings from the Network window:

1 Right-click on a device and select ‘Control ’

to view the device’s control screen. (See Step

3.2: Configuration of Densité and RollCall Devices , on page 45.)

Note: For GV Fabric IP Switch devices, the control screen that is opened in the GV Orbit Client window is the device’s web page.

Upgrade Device

To upgrade a device from the Network window:

1 Right-click on a device and select ‘Upgrade’ to open the device’s upgrade screen. (See

Step 4: Device Upgrade , on page 52.)

Alarms

See

Alarms

section for more information.

102

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Alarms

Note: Alarms in GV Orbit v1.2 onwards:

In GV Orbit systems, alarms are handled ‘behind the scenes’ with internal addresses. These addresses have changed for GV Orbit v1.2.0 onwards:

• v1.2.0 onwards : Alarm-addresses for Densité-protocol devices are now aligned with the respective device/card address.

• Earlier than v1.2.0

: Densité-protocol device alarm-addresses are separate and are not aligned to device addresses.

CAUTION

As a result of this alarm addressing change, when upgrading to GV Orbit v1.2.0 onwards, addresses specified for alarms must be changed. This applies to custom operator panels of C&M projects and to Alarm Behaviours.

Alarm List - Live Alarms/Status

Professional and Enterprise only.

Alarm List Window

To inspect live alarms and status of a device/frame/service from the Network window:

1 Right-click on a device item in the Network window and select ‘ Alarm List’ .

The live status and alarms reported by the device/frame/service are listed in an Alarm

List

window. See examples shown in Figure 3-16a and b, and Figure 3-17a and b.

103

Home Screen

Alarm List - Live Alarms/Status

GV Orbit Client Version 2.0.0

User Guide

Click to select sorting of listed alarms from drop-down menu.

Clear filters on all columns.

Filter on a column (Name or

Value or State).

a) Alarm List example for a system device, XIP device

104 b) Alarm List for an Auto-discovered GV Fabric IP Switch

Fig. 3-16: Example Alarm List Windows for: a) System Device (XIP shown); b) GV Fabric IP Switch.

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Alarm List - Live Alarms/Status a) Alarm List for a GV Orbit Server b) Alarm List for a GV Orbit Service

Fig. 3-17: Example Alarm List Windows for: a) GV Orbit Server; b) GV Orbit Service.

105

Home Screen

Alarm List - Live Alarms/Status

GV Orbit Client Version 2.0.0

User Guide

Alarm List Window Masking

In the Alarm List window, alarms can be masked:

• at a device-level; or

• individual alarms for a device can be masked ( alarm-level ).

Right-click on an item in the Alarm List

window to see masking options. See Alarm

Masking (Professional and Enterprise) , on page 109 for further information on masking.

Right-click options

Right-click options Alarm-level masking options

Fig. 3-18: Alarm List Window Right-Click Options

Device-level masking options

106

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Alarm History for a Device

Professional and Enterprise only.

Note:

The Alarm History window uses the following GV Orbit services:

IP Proxy, Log Server, Monitoring, Event Logging, and Densité Manager.

These services are all required for Alarm History .

To inspect the history of device status and alarms from the Network window:

1 Right-click on a device in the Network window and select ‘ Alarm History ’.

The status messages and alarms etc. reported by the device are listed in a new History window tab. The address of the device is shown in the window tab. See

Figure 3-19.

2 Click the search icon (

History window.

) in the

The Search Parameters dialog is shown.

3 Select a Log Data Source from the drop-down menu.

Note:

The Log Data Source dropdown menu lists the Event

Logging filters that are set up on the GV Orbit server’s Event

Logging service.

This selects an alarm data source to view in the window.

Note:

See

History Window (Alarm History) , on page 112

for further information on data sources and the controls in this tab window.

4 To close the Search Parameters dialog,

(re-)click on the search icon (or click somewhere else in the History window).

The selected data source is shown in the History window.

(See History Window (Alarm History) , on page 112 for further information.)

107

Home Screen

Alarm History for a Device

GV Orbit Client Version 2.0.0

User Guide

Address of device shown in tab Click to filter on a column (Name or Value or State)

108

(See History Window (Alarm History) , on page 112 for further information on the

History window.)

Fig. 3-19: Example History Window

Note: Masked alarms are shown “grayed-out” in the History window.

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Alarm Masking (Professional and Enterprise)

Alarm masking may be done on a device ( device-level masking), or it may be done on a an individual alarm from a device ( alarm-level masking):

• Device-level masking/unmasking can be done from the Network window, or from the

Alarm List window for a device.

• Alarm-level masking/unmasking may be done from a device’s the Alarm List window.

Device-level masking is applied separately and additionally to any alarm-level masking.

For example, if an alarm-level mask is applied to alarm A for a device and then a devicelevel mask is applied to the device, when the device-level mask is removed, the alarm-levelmask will still apply.

Apply a Device-Level Mask

To mask alarms associated with a device, from the Network window:

1 Right-click on a device, select ‘Alarm Masking’. See Figure 3-23.

‘Mask device until normal’ is grayed-out for devices with OK status.

Fig. 3-20: ‘Alarm Masking’ Menu Options

2 Select one masking option from:

• Mask Device - Mask all alarms from a device/unit/frame/service.

• Mask Device Until Normal - Mask alarms from a device/unit until alarm state is OK

(‘green’). For example, mask a device/unit until any fault/error is corrected.

Note: This menu item is grayed-out for devices with an OK Alarm state.

• Mask Device with Tag - Mask a device with a Masking Tag. See

Alarm Masking

Tags .

• Snooze Device - Mask alarms from a device/unit for a period of time. See

Alarm

Masking Snooze Times

• Unmask - Unmask a device or a set of tagged devices.

Note: Masking or unmasking menu options may be grayed-out in the menu.

Apply an Alarm-Level Mask

Mask an alarm from a device, from the device’s Alarm List

window. See Figure 3-18 on page

106.

109

Home Screen

Alarm Masking (Professional and Enterprise)

Alarm Masking Tags

A set of device(s) can be masked with a Masking Tag .

GV Orbit Client Version 2.0.0

User Guide

Fig. 3-21: Mask a Device with a Masking Tag

Masking Tags are created in the ‘Tools > Options > Monitoring’ dialog from the main menu and provide the user with a flexible, multiple and layered masking facility.

110

Masking Snooze Times defined

Masking Tags defined

Fig. 3-22: Tools > Options > Monitoring Dialog

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Alarm Masking (Professional and Enterprise)

Alarm Masking Snooze Times

Alarms for a device/unit/frame/service may be masked for a period of time.

Masking ‘Snooze’ times

Fig. 3-23: Masking Snooze Times

The selectable masking snooze times are configurable, see ‘Tools > Options > Monitoring’ in main menu in

Figure 3-22 on page 110.

111

Home Screen

History Window (Alarm History)

GV Orbit Client Version 2.0.0

User Guide

History Window (Alarm History)

Lite Professional



Enterprise



Introduction

The GV Orbit Client History window can show the history of system-wide alarms and status messages which are read from the Event Logging service on the GV Orbit server.

Note:

The History window is similar to the window shown for

Alarm History for a Device , on page 107 .

Note:

By default, the History window sources event log data from the event log store which is set up as default in the Event Logging service. For example, the event log for which the Default Index setting is selected.

A user can change the event log data source for an History window . For example, change Log Data Source in the Search Parameter dialog.

A GV Orbit Professional or Enterprise user can:

• Select an event log data-set to use from the event log store.

• Search for messages from a particular time period.

• Filter what is shown in the pages (for example, to just display minor alarms).

Note: Log Data Sources:

A History window sources log data from the GV Orbit system event log store.

All events are logged by an Event Logging service running on the GV Orbit

server (see Event Logs , on page 132). Depending on a log data-set’s

configuration, some and/or all events and alarms are logged. A store may be selected as the log data source for display in the History window.

View Alarm History for System-wide Alarms

To view the Alarm History for GV Orbit system-wide alarms:

1 Click the Alarm History icon in the main tool bar.

The History window appears in a tab.

Note: The tab shows no specific device address when showing system-wide alarms.

Select the History tab to view it.

112

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Search Parameters Dialog

The Search Parameters dialog appears in the History window for both system-wide alarms or for device alarms.

1 Click on the search icon ( ).

The Search Parameters

dialog is shown. See Figure 3-24.

2 Set Log Data Source to the log data-set to use from the event log store. a) Select Log Data Source to display.

b) Select Date and Start Time and End Time of messages to display.

c) Display only messages from the last hour.

Fig. 3-24: Search Parameters Dialog

113

Home Screen

Search Parameters Dialog

GV Orbit Client Version 2.0.0

User Guide

3 Select the date and time period to display.

This can be done by:

• setting Date , Start Time , and End Time ; or by

• selecting to see a last period ( Reset to last 30 minutes , or Reset to last hour ).

All event logs, including alarm messages, are listed in time stamp order, most recent

first. See Figure 3-25.

114

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Search Parameters Dialog

State alarm icons:

Click to:

• Clear column filter settings.

• Hide/show columns.

• Show Search Parameters dialog, to select log file and time period to display.

See Figure 3-24.)

• Refresh data in the table.

• Click in a column heading on to filter displayed data on a column.

Page navigation

Click to go to: • first page.

• previous page.

Alarms which are masked are shown “grayed-out”

• a page • next page.

• last page.

Fig. 3-25: Alarm History Window (History Tab Selected)

115

Home Screen

Graphical Routing Workflow

GV Orbit Client Version 2.0.0

User Guide

Graphical Routing Workflow

Lite Professional



Enterprise



Introduction

The factory-set Workflow stage shows a graphical workflow for routing system configuration and control with clickable icons to access tools via GV Orbit Control Client.

(1)

(4)

(10)

(8) (9)

(11)

(2) (3) (12) (13)

(6)

(5)

Click on icons (1) to (13) to access routing tools

(7)

Click on server icons to access landing pages for each GV Orbit server.

Each icon (1) to (13) is described in the

Steps for Graphical Routing Workflow Stage Icons table, on page 117

Fig. 3-26: Graphical Routing Workflow Stage - with Icons (1) to (13)

116

GV Orbit Client Version 2.0.0

User Guide

Home Screen

(1) IP Configuration and Spreadsheet Import

Table 3-2: Steps for Graphical Routing Workflow Stage Icons

Steps relating to icons in Figure 3-26 Graphical Routing Workflow Stage - with Icons (1) to (13) , on page 116

(1) IP Configuration and Spreadsheet Import

Access the IP Routing endpoint configuration editing tool and a new, default GV Orbit C&M

project (see Chapter 17 IP Configuration

for more information):

1 Click the Comms Setup button:

• Select Routing System controller type to be ‘GVC’, (to work with the GV Orbit server).

• Select Domain number for IP End-point setup (default

‘101’).

• Leave the GVC domain number at its default (105).

• Select the client PC network IP interfaces to use.

Click OK .

GV Orbit Client will discover IP End-points and list them.

2 Click on the Devices tab to see the listed devices.

3 Click Export to export the discovered IP end-point devices and their current settings. (A spreadsheet file, .xlsx file, is exported and this shows the spreadsheet file format. Settings include: device names, router port numbers, source/destination IP flows, and multi-cast IP addresses etc.)

4 Edit the spreadsheet file to change settings and/or add more IP end-point devices.

5 Click Import to import IP End-point device settings via a spreadsheet.

6 Project -> Save Project from the main menu. Close the IP Endpoint Editor tab.

IP Endpoint Editor tab

Device tab Export Import Comms Setup Button

Discovered devices are listed

Fig. 3-27: IP Endpoint Configuration Editor tab in GV Orbit Client (Device sub-tab shown)

This screen also allows:

• Manual configuration of end-points, if required.

• Review IP End-point settings, edit settings, validate settings, make engineering routes, if required.

• Monitor bandwidths at device interfaces, if required.

Note: SDI ‘end-point’ configuration etc. is set up via GV Orbit Control in the remaining controls on the routing workflow.

117

Home Screen

(2) Logical Level Editor

GV Orbit Client Version 2.0.0

User Guide

Table 3-2: Steps for Graphical Routing Workflow Stage Icons (continued)

Steps relating to icons in Figure 3-26 Graphical Routing Workflow Stage - with Icons (1) to (13) , on page 116

(2) Logical Level Editor

Access logical route editor tool in GV Orbit Control Client. For the target router:

• Define, review, edit logical routing levels. For example, levels for audio channel(s), video channels, SDI video, ancillary data etc.

See

Logical Level Editor

Tasks , on page 210

(3) Topology Configurator

Access router topology configurator tool in GV Orbit

Control Client:

• Define router topology with the logical levels. For example, how physical and logical devices are arranged in the broadcast facility.

• Select topology to use.

See Topology Configurator

Tasks , on page 219

(4) Logical Device Table

Access the logical devices editor tool in GV Orbit Control

Client:

• Define logical devices in a table.

• Configure levels and IP streams.

• Configure audio shuffled streams and break-away streams.

• Create virtual crosspoints and logical destinations devices.

See Logical Device Table

Tasks , on page 259

118

GV Orbit Client Version 2.0.0

User Guide

Home Screen

(5) Category

Table 3-2: Steps for Graphical Routing Workflow Stage Icons (continued)

Steps relating to icons in Figure 3-26 Graphical Routing Workflow Stage - with Icons (1) to (13) , on page 116

(5) Category

Access the Category

Configurator tool in GV Orbit

Control Client:

• Manage sources and destinations with groups (or categories) based on type or usage. This is useful when there are multiple resources.

Categories allow sources/destinations to be accessed quickly on a routing control panel.

See

Category Configurator

Tasks , on page 287

(6) Panel Configurator

Access the Panel Configurator tool in GV Orbit Control Client:

• Create soft router control panel designs.

• Add buttons and behaviors to a routing control panel.

• Push the design to soft or hard panels.

See

Panel Configurator Tasks , on page 294 .

(7) GPIO Configurator

Access the GPIO Configurator tool for GPIs and GPOs on supported panels (for example, GPI-1501) with

GV Orbit Control Client:

• Add rules for GPIs to trigger events such as a salvo or routing a source to a destination.

• Add rules for GPOs to activate on combinations of conditions.

See

GPIO Configurator Tasks , on page 329 .

119

Home Screen

(8) Bulk Routing

GV Orbit Client Version 2.0.0

User Guide

Table 3-2: Steps for Graphical Routing Workflow Stage Icons (continued)

Steps relating to icons in Figure 3-26 Graphical Routing Workflow Stage - with Icons (1) to (13) , on page 116

(8) Bulk Routing

Access the Bulk Routing

Control Panel tool in GV Orbit

Client:

• Make routes between sources and destinations.

• Form break-away routes and shuffled routes.

• Execute salvos.

For an introduction to the Bulk

Routing Control panel, see

Bulk Routing Control Panel , on page 122.

(9) Snapshots

Access the Snapshots tab of the GV Orbit Routing Service that runs on the GV Orbit server:

• Recall routing snapshots.

• Create and save new snapshots.

(10) Router Control

Access the Router Control

Panel tool in GV Orbit Control:

• Make routes between sources and destinations.

• Create and execute salvos.

See

Router Control Tasks

, on page 466

120

GV Orbit Client Version 2.0.0

User Guide

Home Screen

(11) Alias Editor

Table 3-2: Steps for Graphical Routing Workflow Stage Icons (continued)

Steps relating to icons in Figure 3-26 Graphical Routing Workflow Stage - with Icons (1) to (13) , on page 116

(11) Alias Editor

Access the Alias editor tool in

GV Orbit Control:

• Assign aliases to sources and destinations

(to support shorter length names, other languages, or different production staff needs).

See

Alias Editor Tasks , on page 462.

(12) System Status

Access the System Status screen of the GV Orbit

Control router controllers:

• Monitor the health of GV

Orbit Control router controller(s).

• View device health for a selected topology.

• Manual fail-over, if required.

See

System Status Task

, on page 455

(13) Path Manager

Access the Path Manager screen of GV Orbit Control:

• View source-destination paths of routed streams.

• View Tie-Line usage information, including % bandwidth used.

See Path Manager Tasks

, on page 448

121

Home Screen

Bulk Routing Control Panel

GV Orbit Client Version 2.0.0

User Guide

Bulk Routing Control Panel

Lite Professional



Enterprise



Introduction

The Bulk Routing Control Panel is a built-in router control panel accessible from GV Orbit

Client. It requires the GV Orbit Routing service to be running on GV Orbit server(s). IP routing or traditional (for example, SDI) routing may be controlled.

More Information on Bulk Routing Panel

For more information, see Chapter 12, Routing Control - XY Routing Panel , on page 579.

Open Bulk Routing Panel

1 Open an existing C&M project and set the GV Orbit Client window size to 1920x1080.

2 Click on the Bulk Routing icon in the

Graphical Routing Workflow stage.

A Bulk Routing Panel is shown in a window tab in the GV Orbit Client.

See Figure 3-28.

122

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Open Bulk Routing Panel

Filtering boxes to limit items shown,

see Filtering , on page 533

Router Control Pane

Source Grid Destination Grid

Salvos Pane

Source Levels Grid Destination Levels Grid

Fig. 3-28: Example Bulk Routing Panel

Troubleshooting

If problems are encountered when opening a Bulk Routing Panel, carry out the following checks:

1 Check that the project’s Client Domain is set for the GV Orbit system.

(Click Connections -> GVOP in the main menu.

Set Client Domain to be the system’s ‘Client Domain’ number.)

2 The project’s Routing Address project variable (a RollCall address) should be set to the

Routing service’s Logging Address . To verify this:

• To see the project variables, click Project -> Edit Variables in the main menu.

• To see the Routing service’s Logging Address :

Log into the GV Orbit server and access the Routing service’s ‘System’

configuration screen. (See GV Orbit Server Login , on page 129, and

Accessing

Services Configuration Screens , on page 131.)

123

Home Screen

Open Bulk Routing Panel

GV Orbit Client Version 2.0.0

User Guide

To save any changes made to the project settings:

3 Click Project -> Save Project in the main menu to save the project locally.

4 Click Project -> Push to push and save the project to the GV Orbit server.

Alternative Open Bulk Routing Panel (Network Window)

The Bulk Routing Panel may also be opened from the Network window in GV Orbit Client:

1 Display the Network window tree-view (click in the main tool bar to toggle displaying the window) and expand the tree-view.

2 In the Network window, locate the ‘ Routing service’ item.

(The item’s name is the Routing service’s

“Logging Name”.)

3 Right-click on the Routing service item and select Open Panel .

A Bulk Routing Panel is shown in a window tab

in the GV Orbit Client. See Figure 3-28 on page

123.

Note: A ‘ Routing service’ item appears in the GV Orbit Network window when a Routing service is running on the connected GV Orbit server and is configured to talk to a router controller.

Bulk Routing Panel ‘Source’ and ‘Destination’ buttons are annotated with router port names obtained through the Routing service.

124

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Bulk Routing Panel - List View

List View is a level-centric view of a Bulk Routing Panel, allowing a user to focus on routing to Destination Levels. List View presents all of the destinations in a ‘list’ format; each list item is a Destination with all of its Levels.

To access List View mode:

1 Open the Bulk Routing Panel and set the GV Orbit Client window size to 1920x1080.

2 In the Destination Grid’s tool bar, click on the List View icon.

This toggles between the normal Bulk

Routing Panel view and the List View mode.

The List View is shown.

See Figure 3-29.

List View

Destination Grid

icon

Click icon to toggle between List View and the normal view

Destination Levels Grid

Scrollable list of destinations

Fig. 3-29: Bulk Routing Panel - List View

Bulk Routing Panel Information

For further Bulk Routing Panel information, including about List View and about general

operation, please refer to Chapter 12, Routing Control - XY Routing Panel , on page 579.

125

Home Screen

Routing Snapshots

GV Orbit Client Version 2.0.0

User Guide

Routing Snapshots

Snapshots of all routes and crosspoints in a GV Orbit system can be taken and restored from the GV Orbit Client with the Routing service configuration screen.

Access Routing Service Screen

1 Go to the GV Orbit Client workflow.wfl Workflow window.

2 Click on the Snapshots icon.

The GV Orbit server window is shown in a tab.

3 Scroll down the server window on the left and locate the ‘Services’ section and select ‘Routing’.

The Routing service configuration screen is shown.

4 Select the ‘Snapshots’ side-tab on the left.

The Routing service’s Snapshots

screen is shown. See Figure 3-30.

126

Fig. 3-30: Routing Service Snapshots Configuration Screen

GV Orbit Client Version 2.0.0

User Guide

To Take a Routing Snapshot

In the Routing service Snapshots screen:

1 Enter a name for the new snapshot.

2 Click Create Snapshot .

Home Screen

To Take a Routing Snapshot

Fig. 3-31: Routing Service Snapshots Configuration Screen

A snapshot of all routes and crosspoints is taken. And the new snapshot appears in the list.

Fig. 3-32: New Snapshot Item in List

3 Click Save Changes .

127

Home Screen

To Recall a Snapshot

GV Orbit Client Version 2.0.0

User Guide

To Recall a Snapshot

In the Routing service Snapshots screen:

1 Find a snapshot in the list and click Recall .

The signal routing and crosspoint settings present when the snapshot was taken are restored.

Fig. 3-33: Recall Snapshot

128

GV Orbit Client Version 2.0.0

User Guide

Home Screen

GV Orbit Server Login

Lite Professional



Enterprise



This section describes how to log into a GV Orbit server from either the GV Orbit Client or with a web browser. When logged in, various configurations can be viewed, including settings for the GV Orbit services.

For more details, please refer to the GV Orbit Admin Guide in

screen is then shown. See Figure 3-35 on page 130.

Login From GV Orbit Client

With a GV Orbit C&M project open in GV Orbit Client, to open a GV Orbit server’s Home stage:

1 Either:

• click Project -> URLs in the main menu and select the GV Orbit server item; or

• click on a server icon in the Workflow stage (for example, Server 1 ).

Fig. 3-34: Click on Server Icon in Workflow Stage

The GV Orbit server Admin Login

Login from a Browser

To log into a GV Orbit server from a browser:

1 Enter the IP address of a GV Orbit server into a web browser (Chrome recommended).

129

Home Screen

Server Admin Login Screen

GV Orbit Client Version 2.0.0

User Guide

The GV Orbit server Admin Login

screen is shown. See Figure 3-35.

Server Admin Login Screen

For more details about the GV Orbit server and logging in, please refer to the GV Orbit

Admin Guide in

Fig. 3-35: GV Orbit Server Admin Login Screen

Note:

The GV Orbit Client and GV Orbit Control Client installers may also be downloaded from the GV Orbit server Admin Login screen.

1 Click Log in .

A login screen is shown.

2 Enter the User ID and Password (the default user ID is ‘admin’ with password ‘admin’).

Click Login .

The GV Orbit server Home stage is shown. See

Figure 3-36 on page 131.

130

GV Orbit Client Version 2.0.0

User Guide

GV Orbit Server Home Stage

Home Screen

GV Orbit Server Home Stage

Click Home to return to this screen.

Note: The GV Orbit Client and GV Orbit Control Client installers may also be downloaded via links.

Fig. 3-36: Example GV Orbit Server Home Stage

Accessing Services Configuration Screens

Services should be set up by the GV Orbit system administrator. Services running on the

GV Orbit server are configured via their configuration screens accessible from the GV Orbit server Home stage.

For information about the server and services, please refer to the GV Orbit Admin Guide . See

1 Log into a GV Orbit server. (See GV Orbit Server Login , on page 129.)

131

Home Screen

Logs

GV Orbit Client Version 2.0.0

User Guide

Logs

Lite Professional



Enterprise



Introduction

Logs are kept for system device status/alarm messages (events) and also for applications/services running on the GV Orbit server.

•

Event Logs

- In an operating GV Orbit system, GV Orbit device/service status, alarm messages and events are logged by a GV Orbit service running on a GV Orbit server.

Events etc. are logged to an event log data set. This is set up when configuring the

Event Logging service on the server.

• Server Application and Service Log Files - Each application/service running on the

GV Orbit server also has a set of log files.

Please refer to the GV Orbit Admin Guide

further information about the GV Orbit server and the available log files.

Event Logs

Instructions for quickly viewing event log files are presented here.

For full log file instructions, please refer to the GV Orbit Admin Guide .

A new GV Orbit system is set up with a default log file configuration. To set up custom event logging in the GV Orbit system, a new event log file configuration can be set up for the

Event Logging service. This can be done on the GV Orbit server:

And view the GV Orbit server Home stage.

132

Fig. 3-37: Select Event Logging from the GV Orbit Server Home Stage

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Event Logs

2 Select Event Logging . (Scroll down on the left-hand side, if required.)

The Event Logging service configuration screen on the GV Orbit server is shown.

3 Click on the Event Log Setup tab.

The Elastic Search Setup tab for the Event Logging service is shown.

Fig. 3-38: Event Logging Service - Search Setup Tab

New log data-sets can be created. For more information, refer the Event Logging service information in the GV Orbit Admin Guide

in Related Documentation , on page 19.

Example New Event Log

To quickly create a new event log:

1 Click New to view the Event Logging service dialog.

2 Enter a name (identifier) for a new event log file configuration (index). For example,

‘chan_001’. (The name acts as an identifier for the event log data-set to be created.)

Note: Event log naming rules:

3 Click OK in the dialog.

The Index name field shows the new event log file configuration name.

4 Select Enable this index .

5 At the bottom of the screen, set Delete Data After (days) to’ 7’.

Log data will be kept for 7 days.

Fig. 3-39: Event Logging Service - Search Setup Screen Controls

6 Set Recording Mode to ‘Everything’.

133

Home Screen

View Event Log

GV Orbit Client Version 2.0.0

User Guide

7 Click Save .

This has set up a new event log to record all events, alarms and log messages.

View Event Log

Event log data may be viewed from the:

•

Event Log Viewer (on GV Orbit Server) ; or

•

Alarm History Window (in GV Orbit Client) .

Event Log Viewer (on GV Orbit Server)

1 Select the Event Log Viewer tab for the Event Logging service.

A log viewer screen is shown. (See

Event Log Viewer Screen , on page 134.)

Alarm History Window (in GV Orbit Client)

1 Open a C&M project in the GV Orbit Client.

2 View the Alarm History window (click on the Alarm History window tool bar icon) and

select the required tab. (See History Window (Alarm History) , on page 112.)

This is a log viewer screen. (See Event Log Viewer Screen , on page 134.)

Event Log Viewer Screen

In the log viewer screen:

1 Click on the Search Parameters icon ( ).

The Search Parameters dialog is shown.

2 Set Log Data Source to the required event log name in the drop-down list.

3 Select Reset to last 30 minutes . (To show the last 30 minutes of log messages.)

4 Re-click on the Search Parameters icon ( and view the resulting logged data.

) to close the dialog

Note:

For information about viewing the event logs, please refer to the GV Orbit

Admin Guide in

Step 1: Create a New Monitoring Screen Schematic , on page 135.

134

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Simple Custom Monitoring Screen Example

Lite Professional



Enterprise



Introduction

A simple custom graphical operator screen is presented here. The example describes a monitoring screen using a C&M project; device status is monitored by the screen.

This requires:

• a configured C&M project;

• a configured GV Orbit server; and

• the following minimum GV Orbit services to be running:

• IP Proxy

• Log Server

• Monitoring

• Densité.

Steps:

•

•

Step 2: Add Monitoring , on page 138.

•

Step 3: Save and Push Project , on page 143.

•

Step 4: Run Custom Monitoring Screen , on page 143.

Step 1: Create a New Monitoring Screen Schematic

1 Open the C&M Project and show the Project window and the

Workflow window with the

Workflow stage.

2 On the workflow stage, click on the Screens icon.

The Screens dialog is shown.

135

Home Screen

Step 1: Create a New Monitoring Screen Schematic

GV Orbit Client Version 2.0.0

User Guide

Fig. 3-40: Screens Dialog

3 Click New Screen .

The New Screen dialog is shown.

4 Enter a name for the new screen schematic and click OK .

A new, blank custom screen schematic is created. The new, blank schematic is shown in

a window tab in GV Orbit Client. See Figure 3-41.

Note:

A custom screen schematic is shown in GV Orbit Client; this is the ‘stage’ on which the schematic is:

• designed when GV Orbit Client is in Design Mode ; and

• run and operated when GV Orbit Client is in Run Mode .

136

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Step 1: Create a New Monitoring Screen Schematic

Run Mode icon (Showing project is in Design Mode )

Schematic stage

Note: Drag ‘handle’ to the right to reveal more tool bar icons

Fig. 3-41: New, Blank Custom Schematic

5 Click the Run Mode tool bar icon to select GV Orbit Client Design Mode

. See Figure 3-

42.

Note: A project’s ‘mode’ toggles between Run Mode and Design Mode .

Click to exit Run Mode

Click to enter a) Icon appearance when in

Run Mode

Run Mode b) Icon appearance when in Design Mode

Fig. 3-42: Run Mode / Design Mode Tool Bar Icon

Note:

In Design Mode , a project may be edited

(for example, a video wall may be modified).

In Run Mode , a project monitors log and alarm data and displays updated custom operator screens in real-time.

137

Home Screen

Step 2: Add Monitoring

GV Orbit Client Version 2.0.0

User Guide

Step 2: Add Monitoring

A control and monitoring (C&M) screen will monitor items in a system with individual or aggregate alarms for a device (or collection of devices), or an individual alarm (or collection of alarms). This is quick and easy to achieve with GV Orbit Client.

Items to be monitored can be dragged onto a C&M screen either from the Network window or from an Alarm List window. One or more devices or device alarms can be monitored.

Add Monitoring of Devices

For a C&M screen schematic open in GV Orbit Client in Design Mode :

1 Expand the Network window to find a RollCall- or Densité-protocol device to monitor.

2 Drag a device onto the C&M screen schematic, and release.

At release, GV Orbit Client pops up a list of options. These control what will be created

from the drag. See Figure 3-43a.

(Figure 3-43b shows the resulting Run Mode screen appearance, see later steps.)

Project is in Design Mode

Pop-up Options

138

Selected device a) Drag on Devices

Drag on-screen

Project is in Run Mode b) Monitoring Example when in Run Mode

Fig. 3-43: Drag Device Monitoring onto the Schematic: a) Drag on Devices; b) Monitoring Shown when in Run Mode

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Step 2: Add Monitoring

3 Click ‘Create Single Tally’ in the pop-up options list.

GV Orbit Client then infers a default, graphical Tally widget on the schematic which is automatically set up to graphically indicate the overall status of the device when in Run

Mode.

4 Drag on more devices, as required.

(Figure 3-43b shows what the graphical items may look like in

Run Mode .)

This has quickly added simple device alarm state monitoring to the C&M project.

Note: Add Device:

Dragging a device onto the schematic and releasing it on top of an existing monitoring Tally widget will add the device to the screen widget, thus creating an aggregate alarm.

Add Monitoring of Alarms

Device alarm monitoring can also be added:

1 Expand the Network window to find a device to monitor.

Then right-click on the device item and select ‘Alarm List’.

The device’s alarms are all shown in a pop-up Alarm List window.

2 Select one or more alarms in the Alarm List window and drag them onto the C&M screen schematic, and release.

(To select more than one alarm item, click on an item to select it, and select more with

CTRL-click.)

At release, a list of options pops up which will control what will be created from the

drag. See Figure 3-44.

Note: Pop-up Options:

These pop-up options are described in

‘Drag-On’ Options , on page 141.

139

Home Screen

Step 2: Add Monitoring

Pop-up options:

Drag on screen

GV Orbit Client Version 2.0.0

User Guide

Alarm List window

Selected alarms

140

C&M project is in Design Mode

Fig. 3-44: Drag Alarm Monitoring onto the C&M Screen Schematic

3 Select the pop-up option required.

GV Orbit Client then infers graphical monitoring widget(s) on the schematic which are automatically set up to indicate the alarm status.

This has quickly added simple device alarm monitoring to the C&M project.

Note: Add an Alarm:

Dragging an alarm (from the same or from a different device) onto an existing monitoring widget will add the alarm to the screen widget.

Note: Right-click Drag:

Right-click dragging will use the last pop-up option selected and will avoid the user having to select the same pop-up option each time.

Note: Label Style Change:

A text label is difficult to see against a black background. In this case, change the label’s appearance by selecting it and changing its ‘Style’ property value, see

Text Label Style Change , on page 142.

When all monitoring widgets have been added, proceed to Step 3: Save and Push Project , on page 143.

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Step 2: Add Monitoring

‘Drag-On’ Options

The pop-up options for creating graphical, on-screen from the ‘drag-on’ item(s) are shown

in Table 3-3. Figure 3-45b and Figure 3-45c show the result of each option

Design Mode and in Run Mode respectively.

Table 3-3: ‘Drag-On Options

Option

Create multiple labels Creates a text label per item.

Description

B) Create multiple tallies

C) Create multiple ‘stateful’ labels

Creates a graphical Tally widget per item, to show the individual alarm state of each item.

Creates a colorful text label per item, where the text color indicates each individual alarm state.

D) Create single aggregate tally Creates one graphical Tally widget to show a combined, aggregate alarm state of all the dragged-on items.

These graphical items show alarm state.

A) A)

B) B)

C) C)

D) D) a) Result of options A), B), C), and D) in Design Mode b) Result of options A), B), C), and D) in Run Mode

Fig. 3-45: Dragged-on Monitoring Options A), B), C), and D) in: a) Design Mode; b) Run Mode.

141

Home Screen

Step 2: Add Monitoring

GV Orbit Client Version 2.0.0

User Guide

Text Label Style Change

When creating a text label with this ‘drag-on’ method, the resulting default label may be difficult to see (for example, if against a black background). In this case, change the

appearance of the text label by changing its ‘Style’ property value, see Figure 3-46a and

Figure 3-46b.

• Select the label(s) on the schematic.

In the Properties box, click on the Style’-

property’s value (see Figure 3-46a).

A drop-down menu is shown.

• Select a Style value from the drop-down menu, for example ‘Solid Caption’.

• Click ‘Yes’ in the dialog that is shown.

The label appearance has been changed (see

Figure 3-46b).

a) Selected Labels

142 b) New Text Label Style

Fig. 3-46: Changing Text Label Style Property

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Step 3: Save and Push Project

When all the required device/alarm monitoring is added to the C&M project screen:

1 Click Project -> Save Project in the main menu to save the project locally.

2 Click Project -> Push to push the project to the GV Orbit server repository.

Step 4: Run Custom Monitoring Screen

1 Click the Design/Run Mode tool bar icon to take GV Orbit

Client out of ‘Design Mode’ and into ‘Run Mode’:

GV Orbit Client runs the C&M project and gets device status information to display on the custom monitoring screen’s

Lamp widgets, which illuminate red/yellow/green to show

device status. See Figure 3-47.

Icon when in Run Mode

Project in Run Mode

Device status shown in Network window is reflected in the custom monitoring screen

Fig. 3-47: Simple Custom Monitor Example Running in GV Orbit Client

Note: Tally Widget graphics:

The graphics shown by these Tally widgets are:

Shape

Green circle

Alarm Status

143

Home Screen

Step 4: Run Custom Monitoring Screen

Yellow/amber triangle

GV Orbit Client Version 2.0.0

User Guide

Minor Warning

Orange inverted triangle Major Warning

Red square

Blue diamond

Failure/Error

Unknown

2 To go back to ‘Design Mode’, click the Design/Run Mode icon again.

3 To save the project locally, click Project -> Save Project from the main menu.

4 To push the project back to the GV Orbit server:

• click Project -> Push from the main menu;

• select the project name in the list (it may already be selected/highlighted); and

• click OK .

5 To close the project, click Project -> Close Project .

6 To close the GV Orbit Client application, click Project -> Exit .

144

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Main Menu and Tool Bar Items

This section describes the Home Screen ’s main menu items and main tool bar items:

•

Main Menu Items

•

Main Tool Bar Items

And:

•

Common Operations in Graphic Editors

Main Menu Items

Note: The main menu items shown depend on the type of GV Orbit project open in GV Orbit Client.

Project Menu

Fig. 3-48: Project Menu

Table 3-4: Project Menu Items

Menu Item

New Project

Open Project

Click to create a new project.

Description

Click to open an existing, locally-stored project.

Recent Projects

Save Project

Click to see a list of recently opened projects.

Click to locally save the current project with all recent changes.

145

Home Screen

Main Menu Items

GV Orbit Client Version 2.0.0

User Guide

Table 3-4: Project Menu Items (continued)

Menu Item

Rename Project

Close Project

Description

Click to rename the open project.

Click to close the open project.

Pull

Push

Click to pull a project from a repository (on a GV Orbit server).

Click to push a project to a repository (on a GV Orbit server).

Recent Files

Save File

Save File As

Set Home

Edit Variables

URLs

Exit

Click to see a list of recently opened files.

Click to locally save the open file.

Click to locally save the open file as a new file.

Click to close the open file.

Click to set the currently open schematic to be the home schematic.

Click to see and edit project variables.

Click to see and access URLs defined in the project.

Click to close any project and exit GV Orbit Client.

Connections Menu

Fig. 3-49: Connections Menu

Note: Setting up GV Orbit server IP address:

When the GV Orbit server IP address is set up

(either at the start of a project, or in the ‘Connections > GV Server ‘menu) then the ‘RollCall-, ‘Densité-, and ‘GVOP-Connections’ > menu item settings are automatically filled out and applied.

Table 3-5: Connections Menu Items

Menu Item

GV Server

Description

Click to set up project connection to GV Orbit server.

Note: Setting this up will automatically cause the other settings in the

‘Connections’ menu to be set up and applied.

RollCall Click to set up RollCall connection settings and options.

146

GV Orbit Client Version 2.0.0

User Guide

Table 3-5: Connections Menu Items (continued)

Menu Item

Densité

Description

Click to configure Densité connection settings.

GVOP Click to set up GV Orchestration Protocol settings.

Home Screen

Main Menu Items

Tools Menu

Fig. 3-50: Tools Menu

Table 3-6: Connections Menu Items

Menu Item

Options

Description

Click to set up options in GV Orbit Client, including:

• App lication - Graphical grid settings and font settings.

• Video - Real time video rendering options.

• Launch - Project launch options.

• Remotes - Remote access options.

• Links - Set URLs in project

• Pop-ups - Name, size and position of any pop-up windows in project.

• Monitoring - Alarm Masking options.

• Map View - Options for C&M project MapView screens, including built-in links and alarm state colors.

Fig. 3-51: Tools > Options Dialog from Main Menu

147

Home Screen

Main Menu Items

GV Orbit Client Version 2.0.0

User Guide

Window Menu

These menu items apply when more than one window (tab) is open in GV Orbit Client.

Menu options may be grayed-out if they do not apply.

Fig. 3-52: Window Menu

Table 3-7: Window Menu Items

Menu Item

Next Tab

Description

Click to go to the next open window tab.

Alternatively, press CTRL-Tab.

Previous Tab Click to go to the previous open window tab.

Alternatively, press CTRL-SHIFT-Tab.

Click to close all window tabs.

Close All

List of open tabs Radio-button list:

Click on a list item to go to that windows tab.

Multiviewer Menu Items

Multiviewer Menu (Single-Multiviewer Project)

This menu appear for non -clustered, single multiviewer cases.

Fig. 3-53: Multiviewer Menu

148

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Main Menu Items

Table 3-8: Multiviewer Menu Items

Menu Item

Properties

Description

Click to see multiviewer device information.

Input Alarms Click to enable and configure alarms on each multiviewer input.

Alarms include video alarms and audio alarms.

Unit Alarms Click to enable and configure specific alarms for the multiviewer device. For example, ‘genlock state’.

Input Audio Set up input audio related settings, including: ‘audio metering type’, digital audio reference level, audio loudness and phase engines.

Note: The ‘audio metering type’ setting defines:

• the ballistics of all audio metering data generated by the device; and

• the default audio meter scale for graphical Audio Bars widgets on the multiviewer’s video wall.

Output Audio

Units

Download Logs

CAUTION The audio metering data ballistics set up here applies globally for the multiviewer device. All audio metering data generated by the device will have the same ballistics.

A GV Orbit multiviewer project may change an audio meter type locally on a video wall tile/schematic which locally changes the meter scale only; the audio metering data used will still have the global ballistics type.

Set up the audio sources for each of the audio channels in each of the multiviewer outputs. Up to eight stereo channels are embedded in each output.

Select the units published by a Grass Valley Log Server that a multiviewer may view.

Obtain logs from a multiviewer unit.

Note: The Alarm items are described in the user manual for the MV-8 Series multiviewer devices.

See the MV-8 Series Core Multiviewer User Manual .

149

Home Screen

Main Menu Items

Multiviewer Menu (Clustered Multiviewer Project)

This menu appears for clustered multiviewer cases.

GV Orbit Client Version 2.0.0

User Guide

Fig. 3-54: Multiviewer Menu

Table 3-9: Multiviewer Menu Items

Menu Item

Multiviewer

Cluster

Description

Click to see multiviewer cluster information.

See Chapter 13 Multiviewer Cluster , on page 645.

Help Menu

Fig. 3-55: Help Menu

Table 3-10: Help Menu Items

Menu Item

About GV Orbit

Client

Description

Click to see information about GV Orbit Client software.

Grass Valley Home

Page

Click to go to the Grass Valley web page.

GV Orbit Manual Click to go to the GV Orbit documentation web page.

150

GV Orbit Client Version 2.0.0

User Guide

Main Tool Bar Items

Tool bar icons implement some main menu functions.

• Pull

• Push

Home Screen

Main Tool Bar Items

• New Project

• Open Project

• Save Project

• Save File

• Save File As

• Alarm History

Fig. 3-56: Main Tool Bar Items

Window

• Project Window

• Network Window

(Toggle the display of windows in the GV Orbit Client)

• Tools > Options

• Lock/Unlock the client window

• URL

URLs

- Go to project

• Home - Go to schematic

Home

The tool icons shown depend on the type of project open in GV Orbit Client and on the editing function being carried out. For example, further Tool Bar items are shown when a

multiviewer video wall is open. See Main Tool Bar with a Graphic Editor Open

Main Tool Bar with a Graphic Editor Open

Additional tool bar icons are shown here. See

Main Tool Bar Items

for the other icons.

Display drawing grid

DeSelect All

Select All

Properties window

Set the active window to full-screen mode

Dock/Undock the active window

Go back/forward a step

Options

(Tools > Options in main menu)

Cut Copy Paste Delete

Graphic Object Alignment Controls

Graphic object layer

Design Mode / Run Mode

(shown in Design mode)

Zoom stage screen in/out

Fig. 3-57: Main Tool Bar with a Graphic Editor Screen Open

151

Home Screen

Main Tool Bar Items

GV Orbit Client Version 2.0.0

User Guide

Note: Object selection/deselection operations used in graphic editors in GV

Orbit Client are described

Selection/De-Selection of Objects in

Graphic Editors , on page 156.

Design Mode / Run Mode

Clicking on the Run Mode / Design Mode tool bar icon toggles between ‘Run’ and ‘Design’ modes of GV Orbit Client.

Click to exit Run Mode

Click to enter a) Icon appearance when

Run Mode in Run Mode b) Icon appearance when in Design Mode

Fig. 3-58: Run Mode / Design Mode Tool Bar Icon

Note:

• In Design Mode , a project may be edited (for example, a video wall may be modified).

• In Run Mode , a project monitors log and alarm data and generates display screens in real-time.

Note: The Design Mode / Run Mode tool bar icon may not be shown if changing between these modes is not applicable in the screen mode of the GV Orbit project shown.

Full-Screen View

The graphical stage area can be viewed in full-screen mode. There are two ways to do this,

To Enter/Leave Full Screen Mode - Short Cut

To enter or to leave the full screen mode, when in a graphical screen:

• Press ALT-Enter.

This toggles full-screen mode on/off.

To View Full-screen

1 Click the Full Screen button ( ).

Set the active window to full-screen mode

Fig. 3-59: Main Tool Bar with a Graphic Editor Screen Open

152

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Main Tool Bar Items

To Exit Full-Screen Mode

1 Right-click on the (full) screen and select ‘Full screen’ in the pop-up menu to exit full screen mode.

Fig. 3-60: Main Tool Bar with a Graphic Editor Screen Open

Graphic Object Alignment Controls

The graphic object controls are used in most graphical editing screens in GV Orbit Client.

The controls are grayed out where they are not used.

Layer controls: Send selected object(s):

• to the front; or

• to the back.

Align on a Grid

Align Controls

Place selected object(s) in a central position of the stage area.

Fig. 3-61: Graphic Object Alignment Tool Bar Controls

Align Controls

Note: Object selection/deselection operations used in graphic editors in GV

Orbit Client are described

Selection/De-Selection of Objects in

Graphic Editors , on page 156.

To use an align control in one of the GV Orbit Client’s graphical editor tools:

1 Select a graphical object. (See Figure 3-62a.)

This will be the object that will be aligned to.

2 SHIFT-select one or more further graphical objects. (See Figure 3-62b.)

3 Click on an align control in the main tool bar.

The alignment is done to the first object selected. (See Figure 3-62c.)

153

Home Screen

Main Tool Bar Items

GV Orbit Client Version 2.0.0

User Guide a) Select an object to align to.

b) SHIFT-Select further objects. c) Objects aligned.

Fig. 3-62: Alignment Example

Align on a Grid

Use this control to arrange selected objects (see Figure 3-63a) in a grid arrangement.

In one of the GV Orbit Client’s graphical editor tools:

1 Select all of the graphical objects to be arranged in a grid. (See Figure 3-63b.)

2 Click on the Align to Grid

tool icon. (See Figure 3-63b.)

‘Align to Grid’ controls are shown in the Properties

box. (See Figure 3-63c.)

3 Set the following ‘Align to Grid’ control values:

• Num Rows - number of rows required in the resulting grid of objects.

(For example, = 3.)

• Row Spacing - number of pixels between rows of the resulting grid.

(For example, = 50.)

• Col Spacing - number of pixels between columns of objects in the resulting grid.

(For example, =20.)

4 Click Apply

. (See Figure 3-63c.)

The object alignment is done to the specified grid. (See Figure 3-62d and Figure 3-62e.)

154

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Main Tool Bar Items a) Objects

Click Align to Grid

Selected objects b) Select objects. Click Align to Grid icon.

c) Align to Grid settings in Properties box d) Objects aligned to a grid.

Fig. 3-63: Align to Grid Example e) Objects (deselected) aligned to a grid.

155

Home Screen

Common Operations in Graphic Editors

•

Selection/De-Selection of Objects in Graphic Editors

•

Selection Etc. in Groups of Objects

•

Selection/De-Selection of Objects in Graphic Editors

GV Orbit Client Version 2.0.0

User Guide

Selection/De-Selection of Objects in Graphic Editors

This section outlines actions to select and de-select objects in general in any of the graphic editors in GV Orbit Client. For example, in the Wall, Room, Tile, or Screen Editor tools.

Table 3-11: Object Selection / De-selection in a Graphic Editor

Action

Click outside the schematic stage area.

Description

ESC

Click ‘ Deselect All ’ in main tool bar.

CTRL-A

Click ‘ Select All ’ in the main tool bar

Click on an item.

ALT-Click on an item.

Deselect All

Select All

Select

SHIFT-Click on an item.

CTRL-Click on an item.

SHIFT-ALT-Click on an item.

Select an alternative item from a layer-stack of items.

Or:

Select the group of objects that an item belongs to.

(For information on groups of objects, see

Selection Etc. in Groups of Objects , on page 157.)

Add an item to the current selection.

Note: When in a router control panel,

SHIFT-click selects a contiguous range of sources are destination. For example, in the

Routing Control - XY Routing Panel , in the

Routing Control - XY Routing Panel , or in the

XY Routing Sources screen of the

MV Cluster -

Room Editor .

Add an item to the current selection when in a Room Editor XY Routing Sources screen.

Add another item to the current selection from a layer-stack of items.

156

GV Orbit Client Version 2.0.0

User Guide

Home Screen

Select All

Table 3-11: Object Selection / De-selection in a Graphic Editor

Action

SHIFT-Click on an already-selected item.

Description

Remove an item from the current selection

SHIFT-drag-cursor on screen to describe a rectangular area.

Select objects within a rectangular area.

All objects wholly or partly within the area are selected.

Select All

Select All is accomplished via CTRL-A or by clicking a Select All button when in a graphic editor in GV Orbit Client.

General Select All

The Select All operation generally selects all objects on a wall or tile etc.

Select All in Some Screens of the Room Editor

However, in the Room Editor there is some flexibility built into Select All when in either the:

• Design Layout mode; or

• X/Y Routing mode.

In these Room Editor modes, then Select All is slightly modified:

• if nothing is selected, then

Select All will select all multiviewer outputs of the video wall.

• if a video tile is selected in a multiviewer output, then

Select All will select all tiles just belonging to that multiviewer output.

Selection Etc. in Groups of Objects

Grouping Objects Together

Graphical objects can be grouped together:

1 Select the objects. (‘Select’, and ‘SHIFT-select’ to add objects to selection.)

2 Right-click on the selected objects and select ‘Group’. (See Figure 3-64a.)

The objects are grouped together. (See Figure 3-64b.)

157

Home Screen

Selection Etc. in Groups of Objects

Selected objects Right-click and select ‘Group’

GV Orbit Client Version 2.0.0

User Guide

158 a) Selected objects

Fig. 3-64: Grouping Objects

Un-Grouping Objects

Graphical objects can be un-grouped:

1 Select the group of objects.

2 Right-click and select ‘Un-Group’.

Operations on Groups

Table 3-12: Operations on Groups of Objects

Action

Select an object.

Hold down Left-click and start to drag, and then additionally hold down SHIFT to drag into a Group.

ALT-click to select an object in a group, and then hold Left-click and drag out of group.

b) Grouped objects

Description

Add an object to a Group.

(Drag into a group.)

Remove an object from a group.

(Drag out of a group.)

Summary contents of this chapter:

Manage Users

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Accessing the Manage Users Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

From the Workflow Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

From the Project Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

From the Project Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Manage Users Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Changes to User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Change Logged-in User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Roles Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Pre-defined User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Role Permissions (Permissions Pane) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Assign Users to Roles (Membership Pane) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

How to Delete Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

How to Add a Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Users Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Pre-defined Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

How to Change a User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

How to Add a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

How to Delete a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Permissions Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Custom User Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Using a Custom User Permission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Permission Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Access Control Example - MapView C&M Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

159

Manage Users

Introduction

GV Orbit Client Version 2.0.0

User Guide

Introduction

GV Orbit Client provides user access control to GV Orbit projects. This controls who can open a GV Orbit project in GV Orbit Client and what editing or operational actions they may perform. Users of a project will require different access to aspects of a project depending on their role.

The GV Orbit Client Manage Users screen enables project user roles and levels of user access to be set up and managed.

When opening a project, a user is prompted for a user name and a password when accessing a GV Orbit project.

Default Admin Username and Password

By default, only an ‘admin’ user is initially configured in a new project. The ‘admin’ user has full permissions.

Default username = admin

Default password = admin

Note: The ‘admin’ user has administrator role permissions which enable all operations within GV Orbit Client to be carried out.

The default ‘admin’ user password should be changed as soon as you

Note: Administrator user passwords should be recorded and kept secure.

Note: The ‘Users’ described here in this chapter are GV Orbit Client users.

These are not users for the GV Orbit Control application in GV Orbit, which utilizes a separate users and user setup - described in the

GV Orbit Control User Guide

160

GV Orbit Client Version 2.0.0

User Guide

Manage Users

Accessing the Manage Users Tab

The Manage Users tab is accessible in several ways:

•

From the Workflow Screen

•

From the Project Home Page

•

From the Project Window .

From the Workflow Screen

To access the Manage Users screen from the GV Orbit Dynamic System Orchestrator workflow screen:

1 Click on the ‘User Management’ icon. See Figure 4-1.

The Manage Users

tab is opened. See Figure 4-2 on page 162.

Fig. 4-1: Workflow User Management Icon

Click User Management icon

161

Manage Users

From the Project Home Page

GV Orbit Client Version 2.0.0

User Guide

From the Project Home Page

The Manage Users tab is accessible from a GV Orbit Project Home screen (for example, in a multiviewer project):

1 Start the GV Orbit Client application.

2 Open a (multiviewer) project and log in as an ‘admin’ user.

The GV Orbit Project Home screen is displayed.

3 Click on the large Manage Users

icon. See Figure 4-2.

The Manage Users

tab is shown. See Figure 4-4 on page 163.

Manage Users Icon

Fig. 4-2: Manage Users icon on Home Screen

From the Project Window

The Manage Users tab is accessible from the GV Orbit Client Project window:

1 Start the GV Orbit Client application.

2 Open a (multiviewer) project and log in as an ‘admin’ user.

3 Clicking on the icon in the main tool bar ( ) toggles showing the Project window.

In the Project window:

4 Locate the name of the current project and expand the item.

5 Right-click on the ‘db.users’ item and select ‘Open’. See Figure 4-3.

The Manage Users

tab is shown. See Figure 4-4 on page 163.

Click to expand/collapse current project item

Project window icon selected.

Current project item, expanded in Project window.

Right-click on

‘db.users’ item and select ‘Open’.

Fig. 4-3: Open Manage Users Tab from Project Window

162

GV Orbit Client Version 2.0.0

User Guide

Manage Users

Manage Users Tab

Note: Managing users:

Ensure that you are logged into the GV Orbit project with administrator permissions when managing users.

Note: The logged-in User name is shown in the main tool bar of each GV

Orbit Client screen.

Manage Users tab db.users tab name, click x to close tab

Click to log out of project and change user

User name shown

Fig. 4-4: Manage Users Tab (‘Roles’ Tab shown)

The Manage Users tab is labeled ‘db.users’ and contains the following ‘sub-tabs’:

• Roles .

• Users .

• Permissions .

A file with the name “db.users” appears in the Project

window, see Figure 4-4.

This file contains encrypted project information, including user name and password details.

163

Manage Users

Changes to User Information

If a change has been made to settings in any of the Manage Users tabs, an asterisk (*) is appended to the “ db.users

” label.

Save changes by:

1 Clicking the Save File icon in the GV Orbit Client main tool bar.

Change Logged-in User

When logged into a project as a user, it is possible to quickly log out and log back in as another user.

1 Start the GV Orbit Client application, open a project and log in.

The project opens in GV Orbit Client and the currently logged-in User name is shown in the main tool bar.

In the main tool bar:

2 Click the Change User icon ( ).

A Change User

dialog is shown. See Figure 4-5.

3 Click Yes to log out and log in (as another user).

Click Change User icon to log out and change user

Current logged-in User name

GV Orbit Client Version 2.0.0

User Guide

Fig. 4-5: User Name and Change Users Icon in Main Tool Bar

164

GV Orbit Client Version 2.0.0

User Guide

Roles Tab

To display the Roles tab in the Manage Users tab:

1 Click on the Roles tab.

The Roles tab lists the defined user roles for the GV Orbit project with a brief description of each,

see Figure 4-6.

Select a listed Role for full role details.

List of defined User roles Full details for selected Role

Manage Users

Roles Tab

Permissions pane

Membership pane

Fig. 4-6: Roles Tab

The Roles tab allows the roles to be viewed, created and edited; it is used to:

• Add and delete roles - New roles can be created and roles can also be deleted.

See

Roles Tab , on page 165.

• Edit permissions for each role - This defines which operations may be carried out in a role with the Permissions pane.

See

Edit Role Permissions , on page 170.

165

Manage Users

Pre-defined User Roles

GV Orbit Client Version 2.0.0

User Guide

• Edit user roles - This assigns a role to each user name.

See

Roles Tab , on page 165.

Pre-defined User Roles

The following user Roles are configured by default in a new GV Orbit project:

• Administrator - role with all default permissions.

• Supervisor - role as administrator, but no user management role.

• Operator - role limited to read-only access to projects.

The permissions for each of these roles are listed in Figure 4-7.

166

GV Orbit Client Version 2.0.0

User Guide

Manage Users

Role Permissions (Permissions Pane) a) Administrator b) Supervisor c) Operator

Fig. 4-7: Predefined User Role Permissions (Multiviewer project shown): a) Administrator; b) Supervisor; c) Operator.

Role Permissions (Permissions Pane)

A role’s permissions are set up in the Permissions pane.

Permissions are operations that can be carried out on a GV Orbit project in the GV Orbit

Client application. When applied to a user, they form the user’s privileges, that is, what each user is allowed to do.

167

Manage Users

Role Permissions (Permissions Pane)

GV Orbit Client Version 2.0.0

User Guide

Note: A default new project’s ‘administrator’ role has permissions to add/edit users.

1 Select the Role in the list in the Roles tab.

Permissions information for the selected Role is shown in the Permissions pane.

Permissions that are ‘allowed’ for the role and others that are ‘available’ are listed in the

Permissions

pane. See Figure 4-8.

Note: The list of all permissions varies between GV Orbit project types.

Fig. 4-8: Permissions (Supervisor Role in a Multiviewer Project Shown)

Purge ALL

Export ALL

Table 4-1: Permissions - GV Orbit project types Multiviewer (MV)/ IP Routing (IP))

Permission

Change multicast options

Change flow options

Assign device ports

Assign ALL ports

The ability to...

Purge all off-line devices.

Change automatic multicast assignment options.

Export settings for all devices.

Change the options used for automatic flow enabling.

Project

Type

MV IP

Assign ports for a device.

Assign ports for all devices.

168

GV Orbit Client Version 2.0.0

User Guide

Manage Users

Role Permissions (Permissions Pane)

Table 4-1: Permissions - GV Orbit project types Multiviewer (MV)/ IP Routing (IP))

Permission The ability to...

Edit source multicast

Enable flows for source device

Edit port number

Edit device name

Import ALL

Assign multicast for dest device

Edit individual multicast settings for a source flow.

Enable flows for a source device.

Edit a port number for a spigot.

Edit a device name.

Import settings for all devices.

Disable flows for source device

Edit port name

Enable source flow

Export device

Disable flows for a source device.

Edit a port name for a spigot.

Enable/disable individual source flows.

Export settings for a device.

Enable flows for all source devices

Import device

Enable flows for all source devices.

Import settings for a device.

Clear multicast for source device Clear multicast settings for a device.

Clear multicast for all source devices Clear multicast settings for all source devices.

Assign multicast for source device Assign multicast settings for a source device.

Assign multicast for all dest devices Set 1:1 or 1:All routes for all destination devices.

Clear multicast for all dest devices

Transfer device

Clear multicast settings for all destination devices.

Transfer settings from one device to another.

Edit schematics

Import user database

Clear device ports

Disable flows for all source device

Clear multicast for dest device

Edit destination multicast

Modify video wall and tile designs.

Import a user database

Clear ports for a device.

Disable flows for all source devices.

Clear multicast settings for a destination device.

Edit individual multicast settings for a destination flow.

Set 1:1 or 1:All routes for a destination device.

Project

Type

MV IP

MV IP

169

Manage Users

Role Permissions (Permissions Pane)

GV Orbit Client Version 2.0.0

User Guide

Table 4-1: Permissions - GV Orbit project types Multiviewer (MV)/ IP Routing (IP))

Permission

Assign multicast for all source devices

Change comms settings

Purge device

Pull from repository

Import layouts

The ability to...

Assign multicast settings for all source devices.

Change network domain and change IP interfaces.

Purge an off-line device.

Move a project from a product unit to GV Orbit Client.

For example, pulling a project from a multiviewer.

Push to repository Move a project from GV Orbit Client to a product unit.

For example, pushing a project to a multiviewer.

Add/rename/delete files or folders Manage project files and folders.

Edit multiviewer properties Edit properties for video wall themes, tiles and walls.

Create and delete alarms.

MV Edit multiviewer alarms

Add/edit users

Import themes

Manage users and roles.

Import themes into a project from another GV Orbit

Client project.

Import walls MV Import walls into a project from another GV Orbit

Client project.

Import wall layouts into a project from an GV Orbit

Client project.

Project

Type

MV IP

Import settings MV

Import tiles

Import grids

Import project settings from another GV Orbit Client project.

Import tiles into a project from another GV Orbit

Client project.

Import grids into a project from another GV Orbit

Client project.

Edit Role Permissions

To edit the permissions for a Role :

1 Select a permission on the Permissions

pane. See Figure 4-9.

2 Click > or < in the pane to move the selected Permission to/from the set of

‘allowed’/’available’ permissions for the role.

170

GV Orbit Client Version 2.0.0

User Guide

Manage Users

Assign Users to Roles (Membership Pane)

3 Add/remove permissions as required.

When done:

4 Click Save File icon in the main menu to save changes.

Fig. 4-9: Edit Role Permissions

Assign Users to Roles (Membership Pane)

The Membership pane displays the following for the selected Role :

• User names assigned in the role - These are listed in the “ Users in Role ” list.

• User names not assigned in the role - These are listed in the “ Users not in Role ” list.

To assign a role to a user, in the Roles tab,

1 Select a Role in the list.

This selects a role to be edited. (See Figure 4-10.)

171

Manage Users

Assign Users to Roles (Membership Pane)

GV Orbit Client Version 2.0.0

User Guide

Selected Role and corresponding Membership pane

Fig. 4-10: Selected Role and Membership Pane

To assign a user into a role:

2 Click on the user name item in the “ Users not in Role” list to select an user.

(More than one user may be selected. To deselect an item, click on the selected item.)

3 Click on the

<

button to add the selected user name(s) to the “ Users in Role” list.

The selected user(s) move from the “ Users not in Role” list to the “ Users in Role” list.

To remove a user from a role:

4 Select the user name item in the “ Users in Role” list.

5 Click on the

>

button to remove it from the “ Users in Role” list.

The selected user name moves to the “ Users not in Role” list.

Lastly:

6 Save any changes by clicking on the Save File icon in the main menu.

172

GV Orbit Client Version 2.0.0

User Guide

Manage Users

How to Delete Roles

Note: A user will lose permissions if they are assigned to a role when the role is deleted. Ensure that no users are assigned in any role to be deleted.

To delete a Role , in the Roles tab:

1 Select the Role to be deleted.

Fig. 4-11: Select a Role for Deletion

2 Review the Role ’s user details in the Membership Pane .

Before deleting a Role , there should be no users assigned to that Role .

3 Remove any users from the role using the Membership Pane .

173

Manage Users

How to Delete Roles

Fig. 4-12: Remove All Users from the Role

4 Click on the Delete Role

button, see Figure 4-13.

A confirmation Delete Role dialog box will appear.

GV Orbit Client Version 2.0.0

User Guide

174

Fig. 4-13: Delete Role

5 Read the message in the dialog.

If you wish to proceed, click “ Yes ” to confirm that the role should be deleted, otherwise, click “ No ”.

The Role is deleted from the Roles tab.

GV Orbit Client Version 2.0.0

User Guide

Manage Users

How to Delete Roles

Fig. 4-14: Deleted Role

6 Save any changes by clicking Save File icon in the main tool bar.

175

Manage Users

How to Add a Role

GV Orbit Client Version 2.0.0

User Guide

How to Add a Role

New roles can be added. In the Roles tab:

1 Click Add New Role .

A new blank role item is added to the bottom of the roles list in the Roles tab.

New blank role item

176

Fig. 4-15: Adding Role

On the right-hand side of the screen:

2 Enter a name for the new role in the Role name text box. Use a short, descriptive name.

(Use characters ‘a’ to ‘z’, ‘A’ to ‘Z’, ‘space’ and ‘0’ to ‘9’.)

3 Enter a brief description of the role in the Description text box.

The new role’s name and description are shown in the list of roles.

4 With the new role highlighted, add the permissions required

- see Role Permissions (Permissions Pane) , on page 167.

5 With the new role still highlighted, assign any users

- see Assign Users to Roles (Membership Pane) , on page 171.

GV Orbit Client Version 2.0.0

User Guide

6 Save any changes by clicking Save File icon in the main tool bar.

A finished new role screen is shown in Figure 4-16.

Manage Users

How to Add a Role

Fig. 4-16: New Role Added

177

Manage Users

Users Tab

GV Orbit Client Version 2.0.0

User Guide

Users Tab

Click on the Users tab at the top of the Manager Users tab to display the Users Tab tab,

see Figure 4-17. The users of a GV Orbit project can be viewed, edited and created.

Users are listed in the main screen area in a graphical Users List - a list of icons.

The Users tab is used to:

• Change the password of an existing user, see

How to Change a User Password .

• Add a new user, see

How to Add a User .

• Delete an existing user, see

How to Delete a User .

Users tab Users List (Icons) User Name Change Password button

User Roles list

Fig. 4-17: Users Tab

Pre-defined Users

Initially, in a new GV Orbit project, a user named ‘admin’ is already defined with full administrator role permissions. This enables all operations within GV Orbit Client to be carried out.

Default username - admin

Default password - admin

The default password for user ‘admin’ should be changed as soon as you log into a new

project, see section .

Record the user names and passwords somewhere safe and secure.

Note: Keep a record of the administrator user name and password used.

178

GV Orbit Client Version 2.0.0

User Guide

Manage Users

How to Change a User Password

In the Users tab:

1 Click on a user icon in the Users List .

This selects the user to be edited.

2 Click on the Change button, located below the User name text box.

The change password dialog is displayed. See Figure 4-18.

a) Add Password for a new user b) Change Password for a user

Fig. 4-18: Change Password Dialogs

3 Enter the original password in the Old password text box, if this is shown.

Enter the new password in both the New password text box and also in the Confirm password text box.

4 Click OK to change the password or click Cancel to abandon the change.

If a new password has been set, a “Password changed successfully” message is displayed; click OK

. See Figure 4-19.

Fig. 4-19: Password Changed Successfully Message

5 Save any changes by clicking Save File icon in the main tool bar.

How to Add a User

In the Users tab:

1 Click Add User .

A new User Icon appears in the graphical Users List

. See Figure 4-20.

179

Manage Users

How to Add a User

GV Orbit Client Version 2.0.0

User Guide

User name text box

New User Icon

Set/change password button

180

Fig. 4-20: Adding a New User

Control External Id

2 Enter a name for the new user in the User name text box.

(Use characters ‘a’ to ‘z’, ‘A’ to ‘Z’, ‘space’ and ‘0’ to ‘9’.)

3 Click on the Change button below the User name text box.

The Set New Password dialog is displayed.

4 Enter a new password in the New password text box and re-enter it in the Confirm password text box.

5 Click OK to set the password, or click Cancel to abandon the change.

If a new password has been set, a “Password changed successfully” message is displayed; click OK .

6 Set the Control External Id :

• If this user is to have a User ID when using the GV Orbit Routing service, set the

Control External Id that they are to use in their NP0017 router control protocol communications with GV Orbit Control.

• So that users with different Control External Id s cannot release a destination locked by another user or panel user; in GV Orbit Client, each user can be assigned a Control External Id . Users with a different Control External Id cannot release a destination locked by another with a different Control External Id . The admin user or a user with an Control External Id set to 0 can override locks set by any other user.

In all cases, you must ensure that the User IDs are coherent between GV Orbit Client and

GV Orbit Control Client.

To do this, see Setting a User ID for Lock, Protect, and Release with NDAC NP0016 / NP0017 Northbound Interfaces , on page 483.

GV Orbit Client Version 2.0.0

User Guide

Manage Users

How to Delete a User

7 Save any changes by clicking Save File icon in the main tool bar.

A new, empty user has been created.

To assign the user to Role

(s), see Assign Users to Roles (Membership Pane) , on page 171.

How to Delete a User

In the Users tab:

1 Click on a User Icon in the Users List to select the user to be deleted.

2 Click on the Delete user button.

A confirmation message dialog box appears.

3 Click Yes to confirm user deletion, or click No to abandon deleting the user.

If the user is deleted, the corresponding user icon disappears from the Users List .

4 Save any changes by clicking Save File icon in the main tool bar.

181

Manage Users

Permissions Tab

GV Orbit Client Version 2.0.0

User Guide

Permissions Tab

The Permissions tab lists the available Permissions with a brief description of each.

Permission types:

• Built-in - By default, a project has built-in Permissions, which are project-typedependent.

• User - Additionally, a user can create custom Permissions for use.

To see the Permissions tab:

1 Click on the Permissions tab in the Manage Users tab to display the Permissions tab.

Fig. 4-21: Permissions Tab

Custom User Permissions

Custom ‘user’ permissions can be created alongside the existing ‘built-in’ permissions and they can be assigned to roles. These allow user access/privileges to be tailored to operational needs.

A custom user Permission is automatically given to the ‘administrator’ Role .

Access-control to GV Orbit Client project screens or to on-screen graphical widgets can be designed into an GV Orbit Client project using custom ‘user’ permissions.

182

GV Orbit Client Version 2.0.0

User Guide

Manage Users

Custom User Permissions

Add Custom User Permission

In the Permissions tab:

1 Click Add Permission .

A new item is added to the list.

2 Enter a name and enter a brief description for the new custom Permission . See

Figure 4-22.

3 Save any changes by clicking Save File icon in the main tool bar.

Fig. 4-22: New Custom User Permission

See

Using a Custom User Permission

183

Manage Users

Using a Custom User Permission

GV Orbit Client Version 2.0.0

User Guide

Using a Custom User Permission

Permission Properties

In a GV Orbit Client project, a GV Orbit control and monitoring screen can be designed to implement access control for:

• GV Orbit Client project screens; or for

• on-screen graphical widgets (for example, buttons).

This is accomplished by utilizing a screen’s or a widget’s ‘Permission’ properties. See

Figure 4-23.

184

Button Widget and its ‘Permissions’ properties

Fig. 4-23: Permission Properties (Widget shown)

Table 4-2: Widget Permissions Properties

Property

General > Permission

Description

Specify the Permission required by the widget user. Select from:

• <none> - no Permission required. No access control.

• <inherit> - use the Permission of the parent MapView screen/component/widget.

• built-in permissions - list of all built-in Permissions .

• user permissions - list of all custom user Permissions .

General > Permission Type Set how the on-screen widget is affected if logged-in user does not have specified Permission :

• Disable - Widget on-screen control is disabled.

• Hidden - Widget is hidden from view.

A user’s ‘ Role ’, which will include or exclude various permissions, can determine whether a logged-in user:

GV Orbit Client Version 2.0.0

User Guide

Manage Users

Access Control Example - MapView C&M Screen

• may use a widget or access screens in a running GV Orbit Client project; and

• how a widget appears on-screen (disabled or hidden).

This facility could, for example, control access to a MapView screen with certain operationally-sensitive controls and limit them to logged-in users whose role includes a certain (custom) permission.

Access Control Example - MapView C&M Screen

This is a simple, contrived example on a C&M ‘MapView’ screen to demonstrate controlled access to a Button widget.

In our example:

1 A custom ‘user’ Permission has been defined (‘My Custom Permission’).

2 Four Button widgets have been configured to turn a Lamp

widget on/off (see Figure 4-

24):

• Two (green-colored) Buttons control the Lamp widget on/off green.

The Button widgets do not have any specific Permissions properties set.

• Two (red-colored) Buttons control the same Lamp widget on/off red.

These Button widgets require a logged-in user to have a specific, ‘user’ Permission set up.

3 There are two Users

set up for this example (see Figure 4-25):

• User ‘admin’ has an administrator Role , which includes all Permissions , ‘built-in’ and ‘user’.

• User ‘supervisor 1’ has a supervisor Role which does not include a custom user

Permission.

When this C&M project is run, the resulting on-screen behavior is shown in Figure 4-26. A

user without the custom ‘user’ Permission only sees some grayed-out buttons and is unable to access them.

185

Manage Users

Access Control Example - MapView C&M Screen

GV Orbit Client Version 2.0.0

User Guide

Button widgets without any specific Permission set.

Button widgets with a specific, custom ‘user’ Permission set up.

Fig. 4-24: C&M Screen Widget Access Control Example - Buttons

186

GV Orbit Client Version 2.0.0

User Guide

Manage Users

Access Control Example - MapView C&M Screen a) supervisor Role , without custom Permission b) administrator Role , with custom ‘user’ Permission

Fig. 4-25: C&M Screen Widget Access Control Example - Users: a) Supervisor; b) Administrator.

187

Manage Users

Access Control Example - MapView C&M Screen

GV Orbit Client Version 2.0.0

User Guide

All Buttons are accessible to the user.

a) Project run when logged in with ‘administrator’ role b) Project run when logged in with ‘supervisor’ role

188

Buttons ‘grayed-out’, user ‘supervisor 1’ has no access to these Buttons .

Fig. 4-26: C&M Screen Widget Access Control Example - Running: a) Logged in as ‘administrator’ role; b) logged in as ‘supervisor’ role.

Client

This chapter describes the following tasks:

•

Launching GV Orbit Control Client , on page 189

•

Logging in to GV Orbit Control Client , on page 189

•

Navigating Back to Stage , on page 190

•

Switching User Profiles , on page 191

•

Viewing Notifications , on page 193

Launching GV Orbit Control Client

Once GV Orbit Control Client is installed on your computer, the shortcut icon appears on your desktop.

For details on installing GV Orbit Control Client for the first time, refer to the GV Orbit Admin

Guide .

Logging in to GV Orbit Control Client

Tip: Before logging in to GV Orbit Control Client ensure that you have a valid user name and password , as well as the Management IP address of GV Orbit Client Admin.

To log in to GV Orbit Control Client

1 Click the GV Orbit Control Client icon on your PC.

The GV Orbit Control Client login screen appears.

2 Enter your user name and password in the User name and password text boxes.

189

Getting Started With GV Orbit Control Client

Client Server Version Check Warning

GV Orbit Client Version 2.0.0

User Guide

3 Enter the Management IP address of the GV Orbit Client Admin in the Server text box.

4 Click Log in .

Client Server Version Check Warning

A warning is displayed if the GV Orbit Control Client’s software version is different from the software version currently running on the connected server. In this case, it is strongly recommended that you download and reinstall the GV Orbit Control Client’s software from the server so that the client and server software versions will match: for details on installing

GV Orbit Control Client, refer to the GV Orbit Admin Guide .

If both client and server software versions are the same, no warning will be displayed and the GV Orbit Control Client opens normally.

Click OK to continue to run the client application regardlessly: this can result in software crashes, database corruption, or other unexpected behavior. Running mismatched software versions is untested and unsupported. Click Cancel to go back to the login screen and then close and upgrade your GV Orbit Control Client.

Navigating Back to Stage

The Stage is the main entry point to configure GV Orbit Client. At any time, you can return to the Stage view.

To navigate back to Stage

1 Open GV Orbit Control Client to any task.

2 Do one of the following:

• Click the Stage tab at the bottom or the UI.

• Click the plus button at the bottom of the UI.

Tip : The second option is useful, if you have a lot of tasks open.

190

GV Orbit Client Version 2.0.0

User Guide

Getting Started With GV Orbit Control Client

Switching User Profiles

The home or Stage view appears.

Switching User Profiles

From the Stage or any open task, you can change to another user profile.

Note: Before switching to another user profile, ensure that you have the required user name, password, and Management IP address.

To switch to another user profile

1 Click on the user profile name at the top right of GV Orbit Control Client.

191

Getting Started With GV Orbit Control Client

Switching User Profiles

GV Orbit Client Version 2.0.0

User Guide

A confirmation message appears.

2 Click Log out to continue.

The Log in screen appears.

192

GV Orbit Client Version 2.0.0

User Guide

Getting Started With GV Orbit Control Client

Viewing Notifications

3 Enter your login credentials in the User name and Password text boxes.

4 Enter the Management IP address of the GV Orbit Client server you are connecting to in the Server field.

5 Click Log in .

GV Orbit Control Client opens to the view applicable to the user.

Note : Access permissions vary according to the permissions granted to the user’s role. For further information, see

Administration Tasks , on page 473.

Viewing Notifications

A notification is an indicator that an event has occurred.

To view your notifications

1 Log in to GV Orbit Control Client.

193

Getting Started With GV Orbit Control Client

Viewing Notifications

GV Orbit Client Version 2.0.0

User Guide

2 Click on the up arrow in the top right corner of the UI.

The Notification window appears.

3 Expand the System list. The list of new events appears.

4 Click on a listed event on the right to view it in the UI.

194

The Configuration tasks in GV Orbit Control Client are used for creating and maintaining areas, topologies, categories, and panels.

The Configuration Tasks are described under the following headings:

•

Area Configurator Tasks , on page 197

•

Logical Level Editor Tasks , on page 210

•

Topology Configurator Tasks , on page 219

•

Logical Device Table Tasks , on page 259

•

Category Configurator Tasks , on page 287

•

Panel Configurator Tasks , on page 294

•

GPIO Configurator Tasks , on page 329

•

Stream Configurator Tasks , on page 339

195

Configuration Tasks

Required Permissions

GV Orbit Client Version 2.0.0

User Guide

Required Permissions

Only users who are assigned to the Administrators role have View, Edit, and Delete permissions in the Area task. All other configuration tasks are accessible to users with either

Administrator or Engineer rights only. For more information, see Viewing Permissions by

Role , on page 480.

196

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Area Configurator Tasks

The Area Configurator task is used for configuring the Areas and controllers in GV Orbit

Client.

An Area is container that is used for grouping together a subset of resources within a system. Typically, these resources are closely related, by physical location, functionality, ownership, and/or logical organization. An area is managed by a single controller group, which is made up of:

• a single controller

• or optionally, two redundant controllers to provide 1:1 fail-over protection

This section describes the following:

•

Accessing Areas in the GV Orbit Control Client , on page 197

•

Adding an Area , on page 198

•

Configuring a Controller Group , on page 199

•

Selecting an Area , on page 203

•

Deleting an Area , on page 204

Accessing Areas in the GV Orbit Control Client

All configuration in GV Orbit Control Client begins by creating one or more areas. Once you have the areas defined, you can add the logical levels, the topologies, and so on.

To configure the area in GV Orbit Control Client

1 Open GV Orbit Control Client Stage. See

2 Select Configuration > Area Configurator .

197

Configuration Tasks

Adding an Area

The Area Graph appears.

GV Orbit Client Version 2.0.0

User Guide

By default, there is one area, called Area. Use the Property Editor on the right to rename it and make it easy to identify within your system.

3 Select the Area to access the Property Editor .

You are automatically in Edit mode. Edit is highlighted in the bar at the top.

4 Enter the required information in the Name , Short Name , Description , and External

ID fields to identify the area.

5 Repeat the procedure for each area in your system.

Adding an Area

You can create multiple areas for your system. This can facilitate configuration and control tasks. Smaller subsets are easier to bring into focus and manage.

To add an area

1 Open GV Orbit Control Client Stage. See

Accessing Areas in the GV Orbit

2 Select Configuration > Area Configurator . See

Control Client , on page 197.

198

GV Orbit Client Version 2.0.0

User Guide

This opens the Area Graph.

Configuration Tasks

Configuring a Controller Group

3 Select the area tile on the left.

4 Drag it to the Area Graph.

5 Repeat the procedure as many times as required to add all the areas you require.

Note: Currently, GV Orbit Client supports one Area. Area inter-connectivity and multiple areas (Incoming Feeds, Master Control, Remote Site, Studio, and

Transmission) are not supported.

Configuring a Controller Group

By default, there is one area and one System Controller group on the Area Configurator

Device Graph.

A controller group can have one or more areas. The controller is a physical or virtual server that runs the GV Orbit Client software.

A Controller group can be made up of either one or two controllers. You need two controllers to implement redundancy or failover protection. In the redundant configuration, one controller is active and the other is on standby. If there is a problem, such as a network connection loss, the standby controller becomes the active controller, automatically. In addition, you can force the standby controller to become the active controller by performing a manual failover operation, at any time.

To configure a controller group

1 Open GV Orbit Control Client Stage. See

Accessing Areas in the GV Orbit

2 Select Configuration > Area Configurator . See

Control Client , on page 197.

199

Configuration Tasks

Configuring a Controller Group

By default, there is one controller and one area on the graph.

GV Orbit Client Version 2.0.0

User Guide

3 Select the bubble for the System Controller you are configuring.

4 Select the System Controller Group Properties .

200

The following properties can be configured for the panel. See also

Description of Common

Client’s NMOS registry, see To configure GV Orbit Client for use with

Parameter

Name

# Controllers

Description

Description

The name or identifier for this system controller group.

Enter 2 in the field if you are setting up redundancy. Otherwise, enter

1 . You can only have one or two system controllers in a group.

An optional description for this system controller group.

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Configuring a Controller Group

Parameter

Virtual IP Address

Description

This is the virtual IP address to communicate with the active server in a

GV Orbit Client server cluster (when a redundant configuration is used). If a GV Orbit Client server cluster is not being used, use the GV

Orbit Client server administration IP address for devices instead of this

IP Address.

For example, in a cluster configuration, a soft panel can be configured to point to this virtual IP address. When a failover happens, control is maintained through the panel using this virtual IP address.

server clusters and failover.

Reference IP

NMOS Discovery DNS GV Orbit Client can automatically discover an NMOS registry through

NMOS Discovery

Search Domain

DNS-SD when the NMOS Discovery DNS and NMOS Discovery Search

Domain parameters are set.

For more information about how to configure and use GV Orbit

NMOS , on page 394.

NMOS Registry

Set the IP of a machine that is always on. After a failover the server that can connect first to this IP will become the master.

This shows the current NMOS Registry Query API URL (hostname / IP address and port number).

For more information about how to configure and use GV Orbit

Client’s NMOS registry, see To configure GV Orbit Client for use with

NMOS , on page 394.

Domain IDs for IP

Routing

Only applications / devices that use the same Domain IDs can communicate with each other on the network. For a list of such devices, see

GVOP Devices , on page 226.

This is a comma separated list of domain IDs on which you want to discover devices and communicate with them. The default value for

Grass Valley equipment is 101 .

Valid range: 0 to 232 .

Domain IDs for Data

Import

This is for future use.

5 Select the Properties tab.

6 Select 1 under System Controller to configure the first controller.

201

Configuration Tasks

Configuring a Controller Group

GV Orbit Client Version 2.0.0

User Guide

The following properties can be configured for the individual system controller that form

the system controller group. See also Description of Common Device Properties , on page 348.

Parameter

Name

Description

Short Name

IP Address

Description

The name or identifier for this system controller instance.

An optional description for this system controller instance.

A nickname used wherever the controller is specified. This name should be limited to 8 characters or less in length. This requirement is important if you are using NVISION panels as they use the Short Name to display device names and NVISION hardware can display a maximum of 8 characters for a device name. Otherwise, a longer nickname can be used.

The network IP address for this system controller instance.

This field for S ystem Controller 1 is populated automatically with this system controller’s Management IP address. This cannot be changed.

When system controller redundancy is used ( System Controller 2 is available), set the network IP address for System Controller 2.

7 Select tab 2 under System Controller to configure the second controller.

8 Update the identification fields for the second controller and set the network IP address for System Controller 2: see the table above.

A confirmation message is displayed:

202

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Selecting an Area

9 Click OK to continue.

Notes

When redundancy has been configured, System Controller 2 joins the Controller group automatically as the standby controller. It becomes the active controller in the event of an automatic or manual failover.

When you click OK, the database from Controller 1 is copied to Controller 2

You can view the health of both controllers on the System Status task. The System Status

Task page will show the status of the controllers at all times, and the right hand section shows the health of devices specific to a topology. However, you must create your areas and topologies first. See

Selecting an Area

You must select an area before you can create or maintain a topology within it. Only one area can be selected at a time.

To switch from one selected area to another

1 Open GV Orbit Control Client Stage. See

Area active first. See Selecting an Area , on page 203.

The currently selected Area is displayed at the top of the interface.

Note: You can perform this procedure from Stage or from any open task. You can always select an area.

2 Click on this area.

A secondary window appears.

3 Click on the area that you to select.

203

Configuration Tasks

Deleting an Area

GV Orbit Client Version 2.0.0

User Guide

In the screen shot above, this is Studio A.

4 Click Select Area at the top of the window.

Deleting an Area

Note: You cannot delete the currently selected Area. If necessary, make another

To delete an area

1 Select another Area other than the one you are going to delete. See

2 Open GV Orbit Control Client Stage. See

Accessing Areas in the GV Orbit

3 Select Configuration > Area Configurator . See

Control Client , on page 197.

4 Click on the Area you want to delete.

5 Click Delete at the top of the logical level editor.

6 A confirmation message appears. It lists the topologies created in the Area.

7 Click OK to continue.

Selecting a Graph

In the Area Configurator, you define the various Areas in your system. Within each Area, you can create multiple Graphs, and each Graph contains a Topology . Each topology shows a part of how the various physical and logical devices are arranged and interconnected within the broadcast facility.

To work on a topology, you first need to select the Graph in which the Topology is held. You can work on only one topology at a time.

To select a Graph

Note: A Graph must be created in an area. Then, it is available only in the area where it was created.

204

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Selecting a Graph

1 Select the required Area. See Selecting an Area , on page 203.

2 Click the Graph icon that holds the currently active topology at the top left of

GV Orbit Control Client.

This opens the graphs window. It shows the currently-available graphs for the selected

Area. Each Graph contains a Topology.

3 Double-click the Graph you want to update or select the Graph you want to update and then click Load .

Now, any configuration work you carry out will be on this selected Graph.

If the topology is new, the Graph is blank. The next step is to begin adding devices. See

Adding Devices to a Topology , on page 224.

205

Configuration Tasks

Creating a new Graph for a Topology

GV Orbit Client Version 2.0.0

User Guide

Creating a new Graph for a Topology

To create a new topology

1 Open GV Orbit Control Client Stage. See

2 Select the required Area. See Selecting an Area , on page 203.

3 Click the Graph icon that holds the currently active topology at the top left of

GV Orbit Control Client.

This opens a secondary window.

206

4 Click Add .

GV Orbit Client Version 2.0.0

User Guide

The Create New Graph window appears.

Configuration Tasks

Creating a new Graph for a Topology

5 Enter a name for the new topology and enter meaningful text in the Summary and

Description fields for easy identification.

6 Click Add on the Create New Graph window.

The new topology appears in the list box with the existing topologies.

7 Select the new topology and click Load . Or double-click the topology.

207

Configuration Tasks

Deleting a Graph

The selected topology is opened.

GV Orbit Client Version 2.0.0

User Guide

If the topology is new, the Topology is blank. The next step is to begin adding devices.

See

Adding Devices to a Topology , on page 224.

Deleting a Graph

Only inactive graphs / topologies can be deleted. See Making an Active Topology Inactive , on page 254. You cannot delete all graphs from GV Orbit Client; at least one graph must

always be present.

To delete a Graph

1 Select the required Area. See Selecting an Area , on page 203.

2 If you are deleting the active topology, you must first make it inactive. See

Making an

Active Topology Inactive , on page 254.

3 Click the Graph icon that holds the currently active topology at the top left of

GV Orbit Control Client.

This opens the graphs window. It shows the currently-available graphs for the selected

Area.

208

GV Orbit Client Version 2.0.0

User Guide

4 Select the Graph you want to delete and then click Delete .

Configuration Tasks

Deleting a Graph

Deleting the last Graph

You cannot delete all graphs from GV Orbit Client; at least one graph must always be present. To delete the last graph, proceed as follows.

1 Create a new graph (see

Creating a new Graph for a Topology , on page 206)

2 Make the new graph active (

Logical Device Table Tasks , on page 259). This allows GV Orbit Client’ s routing system to

3 Delete the previous graph.

209

Configuration Tasks

Logical Level Editor Tasks

GV Orbit Client Version 2.0.0

User Guide

Logical Level Editor Tasks

Logical levels allow for the definition of compatibility and shuffling rules. This presents the user with complete control of the path definition to prevent routing of incompatible levels.

For example, Logical levels are used to identify a stream’s video resolution, the number of audio channels, ancillary data, and so on.

Every unique type of stream format in your facility should have a unique Logical Level.

These levels are then assigned to sources and destinations (in the Logical Device Table; see

make takes between sources and destinations with signal types that are compatible with each other, and with the underlying hardware, so that takes can be successfully made in the real world.

This section describes the following:

•

Accessing the Logical Level Editor , on page 210

•

Viewing the Default Logical Levels , on page 212

•

Duplicating a Logical Level , on page 213

•

Editing a Logical Level , on page 215

•

Deleting a Logical Level , on page 216

•

Configuring a New Logical Level , on page 216

•

Configuring the Logical Levels for the Devices in a Topology , on page 217

Accessing the Logical Level Editor

Use the Logical Level Editor to define new logical levels and to view the compatibility of the default levels.

To access the Logical Level Editor Task

1 Open GV Orbit Control Client Stage. See

2 Select an area.

3 Select Configuration > Logical Level Editor .

210

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Accessing the Logical Level Editor

The Logical Level Editor appears.

Note: Only users who are assigned to the Administrators or Engineers role in the selected area have View, Edit, and Delete permissions in the Logical Level Editor task.

See

which. See Creating Logical Devices with Shuffled Audio , on page 274.

Note: Before you can open the Logical Level Editor, you must open an Area and a

Topology. Logical levels are defined specifically for each topology.

The Logical Level Editor has two columns:

• The first column contains tiles for all default logical levels along with the logical levels you have added.

• The second column has three tabs: compatible with , contains and shuffle with . The shuffle with allows a user to configure which audio levels can be shuffled with

Logical Level Editor Menu

The Logical Level Editor menu has the following menu options.

Icon

Edit

Duplicate

Delete

Description

Edit a logical level’s properties. See

Editing a Logical Level , on page 215.

Make a copy of the currently-selected logical level. See

Duplicating a

Logical Level , on page 213.

Remove the currently-selected logical level. See Deleting a Logical

Level , on page 216.

211

Configuration Tasks

Viewing the Default Logical Levels

GV Orbit Client Version 2.0.0

User Guide

Viewing the Default Logical Levels

The default logical levels are represented by the first tiles displayed in the Logical Level

Editor column, beginning with video, then audio, ancillary, and finally AES67. When you create new logical levels, they are added after these ones.

You can change the Short Label and Level ID of a default Logical Level, but not the Name.

Click Edit to do so. Also, you cannot delete a default level.

The Audio Live device uses AES67 audio levels. See Logical Levels that specifically support

Audio Live , on page 440 for more information.

Verifying the Compatibility of the Default Logical Levels

Compatibility defines which Logical Levels are compatible when making a take. This is shown in the Compatible with tab shown below. When a source and destination use the same Logical Level, or the two Logical Levels are compatible with each other, then a take is possible between the source and destination.

Certain default Logical Levels are compatible with other Logical Levels. For example,

AES67 16 is compatible with SDI audio . That is to say, a take between an AES67 16 source and an SDI audio destination is allowed by the router system.

When you create a Logical Level, you always modify the compatibility between these

Logical Levels according to the required source / destination signal types.

To verify the compatibility of Logical Levels

1 Open GV Orbit Control Client Stage. See

. See Accessing the Logical Level Editor , on page 210.

2 Select Configuration > Logical Level Editor

The Logical Level Editor appears.

212

3 Select a logical level tile on the left.

The tiles for the logical levels it is compatible with are highlighted in the right column.

Note: A logical level is always compatible with itself.

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Duplicating a Logical Level

Verifying the Component Signal Types of the Default Logical Levels

Like the compatibility, the signal types of the default logical levels is predefined and cannot be changed. When you create a Logical Level, you always modify the signal type components.

To verify the signal types of the default logical levels

1 Follow the procedure under

Verifying the Component Signal Types of the Default

Logical Levels , on page 213.

2 When you select a tile for a logical level in Logical Level Editor , the compatibility is highlighted in the Contains tab.

Duplicating a Logical Level

A pre-existing logical level can be copied to reuse that logical level’s configuration properties and then you only need to modify the necessary logical level properties as required for the new application.

Notes

Logical levels are specific to topologies. In another topology, you won’t see the logical levels you create in the currently selected topology.

Only SDI and TICO levels can be duplicated.

To duplicate a logical level

1 Open GV Orbit Control Client Stage. See

. See Accessing the Logical Level Editor , on page 210.

2 Select Configuration > Logical Level Editor

3 Select a pre-existing level on the left-hand panel that you want to duplicate.

4 Click Duplicate at the top of the interface.

213

Configuration Tasks

Creating the Logical Levels for a UHD 4K Routing Setup

The Logical Level configuration window opens.

GV Orbit Client Version 2.0.0

User Guide

5 Enter meaningful names to identify the level in the Name Prefix , Name Suffix , Short

Label Prefix , and Short Label Suffix text boxes.

6 Enter a unique identifier in the Starting Level ID text box.

7 Click OK .

A tile for your new logical level is displayed in the left hand column.

See

Configuring the Logical Levels for the Devices in a Topology , on page 217.

Creating the Logical Levels for a UHD 4K Routing Setup

For an example of how to create the logical levels for UHD routing when a quad-link signal path is used, see:

•

Configuring UHD 4K Two-Sample Interleave Division IP Streams for use with an IQMix,

IQUCP, or IPVU Device , on page 371.

•

Configuring UHD 4K Quad-Link SDI Streams for use with an IQMix, IQUCP, or IPVU

Device , on page 376.

214

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Editing a Logical Level

Use the following procedure to modify a logical level’s identification information. The

Audio setting marks that the level is an audio level.

To edit a logical level

1 Open GV Orbit Control Client Stage. See

. See Accessing the Logical Level Editor , on page 210.

2 Select Configuration > Logical Level Editor

3 Select a level on the left-hand panel that you want to edit.

Note: For the default logical levels, you can modify the Short Label and Level ID. You cannot modify the Name.

4 Click Edit at the top of the logical level editor.

5 Modify the properties as required.

Parameter

Name

Short Label

Level ID

Audio

# Channels

Description

The level’s name.

A shortened name for the level.

A unique identifier for this level.

When set, this level will appear in the Shuffle with tab of the right

pane for shuffling rules. See Creating Logical Devices with Shuffled

Audio , on page 274.

When available, this shows the number of audio channels supported by this level. The Audio Live device uses a range of levels, each one supporting a different number of audio channels. See

Configuring a

Device that Supports Audio Breakaway/Shuffling such as Audio Live , on page 437.

6 Click OK .

215

Configuration Tasks

Deleting a Logical Level

GV Orbit Client Version 2.0.0

User Guide

Deleting a Logical Level

Use the following procedure to delete a logical level you have created that is no longer required in the selected topology.

Note: You cannot delete the default logical levels. The Delete button is disabled when you click on these levels.

To delete a logical level

1 Open GV Orbit Control Client Stage. See

. See Accessing the Logical Level Editor , on page 210.

2 Select Configuration > Logical Level Editor

3 Select the tile for the logical level you want to delete.

4 Click Delete at the top of the logical level editor.

Note: There is no confirmation for the deletion.

Configuring a New Logical Level

Use the following procedure to configure a new logical level. This determines which signal types are compatible with this level.

To configure a new logical level

1 Open GV Orbit Control Client Stage. See

. See Accessing the Logical Level Editor , on page 210.

2 Select Configuration > Logical Level Editor

216

GV Orbit Client Version 2.0.0

User Guide

3 Select the tile for the logical level you want to configure.

Configuration Tasks

Configuring the Logical Levels for the Devices in a Topology

The tile for your new logical level is automatically highlighted in the right hand column.

4 Select the tiles for the signal types in the right hand column that are compatible. Click a tile a second time to deselect it.

Configuring the Logical Levels for the Devices in a Topology

Use the following procedure to set the logical levels for the device’s sources and destinations in your topology. Logical levels can be used to define the type of signal carried on a physical connection between physical devices. If compatibility is not an issue, the default logical levels may be utilized.

To configuring an area in GV Orbit Control Client

1 Select the required topology in the area. See Accessing the Topology Configurator , on page 219.

2 Select the device for which you want to configure its logical level.

In the above example, the camera bubble is selected. SDI is the default logical level for cameras.

217

Configuration Tasks

Configuring the Logical Levels for the Devices in a Topology

3 Select Device Group Properties.

4 Select the Logical Level parameter in the Property Editor .

This opens the Logical Level list.

GV Orbit Client Version 2.0.0

User Guide

5 Select the required logical level for the device group.

218

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Topology Configurator Tasks

In the Area Configurator, you define the various Areas in your system. Within each Area, you can create multiple Graphs, and each Graph contains a Topology . The topologies show how the various physical and logical devices are arranged and interconnected within the broadcasting facility. See

Area Configurator Tasks , on page 197 and

Accessing the Topology Configurator , on page 219

These sections describes the following:

•

•

Selecting a Graph , on page 204

•

Refreshing the Topology , on page 222

•

Creating a new Graph for a Topology , on page 206

•

Adding Devices to a Topology , on page 224

•

Methods to Link Devices in a Topology , on page 239

•

Defining Device Properties , on page 247

•

Deleting a Device From a Topology , on page 252

•

Activating a Topology , on page 253

•

Making an Active Topology Inactive , on page 254

•

Unlocking / Relocking a Topology , on page 256

•

Locking an Unlocked Topology , on page 257

Certain devices require a detailed procedure to configure them; see Special Device

Configuration Tasks , on page 347 for more information about these devices.

Accessing the Topology Configurator

You can access the Topology Configurator from Stage or from any open task. Access permissions are required. See also

To access the Topology Configurator from Stage

1 Open GV Orbit Control Client Stage. See

from anywhere in GV Orbit Control Client. See Selecting an Area , on page 203.

2 Select Configuration > Topology Configurator .

219

Configuration Tasks

Accessing the Topology Configurator

GV Orbit Client Version 2.0.0

User Guide

The Topology Configurator appears. The Topology Configurator comprises three sections. The left hand column has a list of bubbles, representing the device groups, such as cameras, routers, and monitors. You drag these onto to the Topology (middle column) and create connections between them. Then, you can configure the properties for the Device Groups in the Property Editor (right-hand column).

220

If an Area is open, the Topology Configurator opens in that area. You can switch areas

Access Permissions

Access permissions to the Topology Configurator vary according to role. Only users who are assigned to the Administrators or Engineers role can View, Edit, and Delete topologies and device properties. Operators have the right to view topologies and device properties.

Maintenance staff and Guests have no access. See

properties. See Defining Device Properties , on page 247.

Topology Configurator Menu

The Topology Configurator has the following menu options.

Icon

Edit

Select

Description

Use this editing mode to select a device on the topology to edit its

Use this editing mode to select one or more devices on the topology

(by drawing a square with your mouse cursor) to move the selected devices around on the topology as a group, or to delete them. Press the <Ctrl> key to temporarily enable this option.

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Accessing the Topology Configurator

Icon

Link

Refresh

Description

Use this editing mode to connect a device’s sources to the destinations

of another device. See Methods to Link Devices in a Topology , on page 239.

This editing mode is also used to break the connection between two

devices. See Deleting the Connection Between Device Groups , on page 246.

Reloads the Topology’s contents. See

Refreshing the Topology , on page 222.

Delete

Remove the currently-selected device from the topology. See Deleting a Device From a Topology , on page 252.

Quick Connect This automatically connects the unconnected ports of devices on the

topology. See Methods to Link Devices in a Topology , on page 239 and

Using Quick Connect to Link all Devices in a Topology , on page 239.

Quick Config

Deactivate / Active Activating a topology makes GV Orbit Client connect to and activate all drivers to devices in the topology. This is important for GV Orbit

Client to learn a device’s current configuration.

See

Activating a Topology , on page 253 and

Making an Active

Topology Inactive , on page 254.

Lock / Unlock

This sets the configuration of the selected devices on the topology.

See

Using Quick Config , on page 236.

Lock a Topology to prevent you from inadvertently making edits on an active topology. See

Unlocking / Relocking a Topology , on page 256

and

Locking an Unlocked Topology , on page 257.

How to Identify if a Device Bubble is Selected or Not

A device bubble has the following selection states.

Description Device Bubble State

Gray, no white circle Not selected

Gray with white circle Selected

Blue with white circle Selected

Device properties are shown in the

Property Editor



221

Configuration Tasks

Refreshing the Topology

GV Orbit Client Version 2.0.0

User Guide

Refreshing the Topology

If you have added a lot of devices to a topology or made many modifications to it, you may need to refresh the Topology. You can refresh topology regardless of whether it is active or inactive.

To refresh the Topology

1 Open a topology in the Topology Configurator.

2 Click the Refresh button at the top of the interface.

The topology is inaccessible during the brief time it takes to refresh the window.

Viewing the Topology in Full Screen Mode

By default, the selected topology is displayed in the center of the Topology Configurator task. The devices are displayed on the left and the Property Editor is displayed on the right.

To view the topology in fullscreen mode

1 Open GV Orbit Control Client Stage. See

2 Select the required Area. See Selecting an Area , on page 203.

222

GV Orbit Client Version 2.0.0

User Guide

3 Select the required topology. See Selecting a Graph , on page 204.

Configuration Tasks

Viewing the Topology in Full Screen Mode

4 Click the Fullscreen toggle button at the top of the interface.

The Topology expands across all three columns in the Topology Configurator.

TIP

To zoom and center the topology view:

• click the Refresh button.

• double-click an empty space.

To return to default mode

1 When the Topology is in fullscreen mode, click Fullscreen to toggle the display back to the default mode.

223

Configuration Tasks

Adding Devices to a Topology

GV Orbit Client Version 2.0.0

User Guide

Adding Devices to a Topology

By adding devices to a topology, you are making a representation in GV Orbit Client of the real world equipment you are using, and the physical interconnections made between this equipment.

There are two types of devices in GV Orbit Client.

• Virtual Devices: These are devices that GV Orbit Client does not need to know any of the device’s configuration parameters in order to use the device. Therefore, the device can be offline when configuring it in GV Orbit Client. See

To add a Virtual Device to a topology , on page 224. Certain devices may require advanced configuration

procedures; see

Special Device Configuration Tasks , on page 347.

• Discovered: These are devices that GV Orbit Client needs to know the device’s configuration parameters in order to know which of the device’s spigots have been configured as sources or destinations, the levels, and so on. These devices must be online when configuring them in GV Orbit Client. For more information about discovered devices, see

About Discovered Devices , on page 225.

To add a Virtual Device to a topology

Certain Virtual Devices require advanced configuration procedures; see

Special Device

Configuration Tasks , on page 347 for more information about the specific device you are

adding to the Graph, if necessary.

1 Select the required Area. See Selecting an Area , on page 203.

2 Select the required topology. See Selecting a Graph , on page 204.

3 The topology must be currently:

• Activated (see

• Unlocked (see

a bubble is a device group that can represent one or more devices. See To name a device and set the number of devices in the group , on page 225.

4 From the Device Library , Virtual Device on the left, select Virtual Devices from the drop-down list.

224

5 From the Device Library , Virtual Device , find the device that represents a piece of equipment you want to control: select the device bubble and drag it into position on the Topology and release the mouse button.

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Adding Devices to a Topology

Initially, the device bubble represents a single device, such as a single camera. However,

6 Repeat step 5 to and the following procedure (

To name a device and set the number of devices in the group , on page 225) until you have added all the required devices to the

topology.

To name a device and set the number of devices in the group

A device group is a collection of devices of the same type that can be configured together.

All bubbles in a Topology are automatically device groups with the exception of the following devices: IPVU, IPG-3901 / IPG-4901, IQMIX / IQUCP25, MV-820-IP, Kahuna-IP,

NMOS devices, Audio Live, IQAMD, Network Switch, Router, and GV Node.

1 Click on the name of the device underneath the bubble to create a device group.

The Device Group configuration window appears.

2 Enter meaningful names to identify the device group in the Name and Short Name fields.

In this case, the Camera device group is named CAM1 to identify the cameras controlled by Controller 1. These parameters can also be set in the Property Editor .

3 Use the plus and minus buttons to enter the number of device instances are in the device group.

4 Click OK .

Each device instance is shown and can be individually configured in the Property

Editor , under Devices , by clicking an instance.

In the above example, five monitors, two IPGs, two network switches, and five cameras have been added to the Topology.

About Discovered Devices

There are two different types of discovered devices:

• NMOS devices discovered with IS-04, that can be senders, receivers or both. For more

information, see Adding NMOS Devices to a Topology , on page 394.

• Grass Valley devices discovered with GVOP; see below for a list of these devices.

225

Configuration Tasks

Adding Devices to a Topology

GV Orbit Client Version 2.0.0

User Guide

GVOP Devices

In order to use discovered GVOP devices in GV Orbit Client, the discovered devices must first be configured through GV Orbit Client. GV Orbit Client needs to know the device’s configuration parameters in order to know which of the device’s spigots have been configured as sources or destinations, the levels, and so on. These devices must be online when configuring them in GV Orbit Client.

The following Devices Use GVOP to be discovered by GV Orbit Control.

Discovered Device

Type For more information, see

IPG-3901 / IPG-4901

Configuring an IPG 3901 / IPG 4901 Device , on page 360

IPVU

IQMIX

IQUCP

Configuring an IPVU Device , on page 366

Configuring an IQMix or IQUCP25 Device , on page 369

MV-820-IP

Kahuna-IP

Audio Live

IQAMD

Other devices that use

GVOP for

Configuration

Configuring an MV-820-IP Multiviewer Device , on page 380

Configuring a Kahuna IP Production Switcher Device , on page 384

Configuring a Device that Supports Audio Breakaway/Shuffling such as Audio Live , on page 437

Configuring an IQAMD40 Device , on page 444

These are device that can be configured through GV Orbit Client.

When the IP Friendly Name service is running on the GV Orbit Server, and the device uses

GVOP for Configuration:

• In GV Orbit Control, GVOP device properties are automatically filled in from when the devices were configured through GV Orbit Client. Changes to those devices’ properties

in GV Orbit Client are updated in GV Orbit Control in real time. See Synchronization of

Discovered GVOP Devices, Source, Destination, and Spigot Names made in GV Orbit

Client , on page 229 for more information.

• The device’s current source and destination configuration is read in real time and is updated in the Logical Device Table’s Multilevel Table when the Automatic Sources and Destinations

parameter is set in the device’s properties. See Logical Device Table

Tasks , on page 259,

About Automatic Sources or Destinations , on page 264,

Device

Properties Definitions

, on page 250, and Synchronization of Discovered GVOP Devices,

Source, Destination, and Spigot Names made in GV Orbit Client , on page 229.

• There is no need to use Camera and Monitor devices to create the logical sources/destinations for these devices. Furthermore, Camera and Monitor devices are not created anymore when using the Quick Connect tool. See

Using Quick Connect to

Link all Devices in a Topology , on page 239.

To add a Discovered device to a Topology, see below.

226

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Adding Devices to a Topology

To add a Discovered Device to a Topology

Discovered devices typically require advanced configuration procedures; see Special

Device Configuration Tasks , on page 347 for more configuration information about the

specific device you are adding to the Graph.

Adding a discovered device to a topology

1 Select the required Area. See Selecting an Area , on page 203.

2 Select the required topology. See Selecting a Graph , on page 204.

3 The topology must be currently:

• Activated (see

• Unlocked (see

configured has changed. To identify a device that uses GVOP, see GVOP Devices , on page 226. These changes bring powerful new features such as:

4 From the Device Library , on the left, select Discovered from the drop-down list. In the example below, an IQMix was discovered on the network.

5 From the Device Library , Discovered find the device that you want to control: select the device bubble and drag it into position on the Topology and release the mouse button.

The device pulled from the Device Library , Discovered becomes grayed out and another instance of the same device instance cannot be added again to the Topology.

However, multiple device instances found in the Device Library can be used to create a device group.

227

Configuration Tasks

Adding Devices to a Topology

GV Orbit Client Version 2.0.0

User Guide

6 To create a device group: a From the Device Library , Discovered , find the device that you want to control: select the device bubble and drag it into position on the Topology and release the mouse button. b From the Device Library , Discovered , find another identical device that you want to control: select the device bubble and drag it on top of the first device instance already on the Topology and release the mouse button.

The two device instances are shown and can be individually configured in the Property

Editor , under Devices , by clicking an instance.

7 Click on the name of the device underneath the bubble to name the device or device group.

These parameters can also be set in the Property Editor when the device bubble is selected.

228

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Adding Devices to a Topology

Using GVOP Devices

As of GV Orbit Control Client version 2.8.0 or higher, the way devices that use GVOP are

• Tighter integration with GV Orbit Client to:

• Automatically synchronize certain configuration parameters in GV Orbit Control.

• Allow a spreadsheet import to set many GVOP device parameters in bulk in both

GV Orbit Client and GV Orbit Control.

See

Synchronization of Discovered GVOP Devices, Source, Destination, and Spigot

Names made in GV Orbit Client , on page 229.

• Devices that Use GVOP for Configuration no longer use the SDI camera/monitor bubble.

• Logical sources/destinations related to those GVOP devices will be automatically created using the spigot name (Port Name), once the configured device is added to the topology, even before making the appropriate connections. Those logical sources/destinations are created using the appropriate streams. For gateway devices, the SDI streams will be used and for IP devices, the IP streams will be used.

• The operating method of any GVOP device configured in GV Orbit Control Client version 2.7.X or earlier will remain unchanged after project migration to version 2.8.0 or higher. However, GVOP devices can be migrated to use this new function model of

operation. See To migrate GVOP Devices for IP routing , on page 235.

Synchronization of Discovered GVOP Devices, Source, Destination, and Spigot

Names made in GV Orbit Client

When the IP Friendly Name service is running on the GV Orbit Server, this service pushes certain configuration parameters made in GV Orbit Client to the same discovered GVOP device in GV Orbit Control. Changes to configuration parameters can result from having

used the spreadsheet import feature in GV Orbit Client. See also GVOP Devices , on page 226.

This service uses a common device identifier, the device’s GUID. A device’s GUID is like a serial number that uniquely identifies individual GVOP devices. Through a device’s GUID, the IP Friendly Name service:

• Provides persistence to the GV Orbit system for the naming of discovered GVOP devices. If the IP Friendly Name service is not running, Device and Spigot values from the configuration will not be available to GV Orbit Control and in such a case, GV Orbit

Control will use the default values for device, spigot and logical source/destination labels. See

Troubleshooting , on page 236.

• Updates made to GVOP devices in GV Orbit Client are dynamically reflected to those same devices in GV Orbit Client topology.

For example, by setting the device name in GV Orbit Client, the device name of the same

GVOP device in GV Orbit Control will be updated in real time.

The intended workflow is to first configure the device in GV Orbit Client and then integrate the device for routing in GV Orbit Control.

229

Configuration Tasks

Adding Devices to a Topology

GV Orbit Client Version 2.0.0

User Guide

When a discovered GVOP device is added to a Topology in GV Orbit Control, and the device’s name is subsequently updated in GV Orbit Client, the device name and the Device

Group name will also be automatically updated. However, once a second or more discovered devices have been added to this Device Group, then the name of the Device

Group will no longer be updated due to changes made in GV Orbit to the name of any device found in the Device Group. The names of the individual devices, regardless of how many of them are in a device group, will always be updated.

Likewise, the device’s current source and destination configuration is read in real time and is automatically updated in the Logical Device Table’s Multilevel Table when the Automatic

Sources and Destinations parameter is set in the device’s properties. For more information,

see About Automatic Sources or Destinations

, on page 264 and Device Properties Definitions , on page 250.

Logical sources and destinations are created using the appropriate streams. For gateway devices, the SDI streams will be used and for IP devices, the IP streams will be used.

You can still manually create custom logical sources / destinations using the streams of your choice; see

Configuring Streams for New Sources , on page 267.

230

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Adding Devices to a Topology

For gateway devices, the Stream Configurator allows you to expose any stream of your choice, including the device’s IP streams. In such a case, the logical sources / destinations created using the SDI streams from the same spigot as the exposed IP streams will not be reachable anymore by GV Orbit Control’s pathfinding, since the newly exposed IP streams

become the device’s edge. See Stream Configurator Tasks , on page 339. The following

diagram shows that when IP streams are exposed, the SDI streams are no longer reachable.

Camera Gateway

2022-6

2110-20

2110-30

2110-40

2022-6

2110-20

2110-30

2110-40

Gateway Monitor

SDI SDI IP IP SDI SDI

Note: When replacing a failed GVOP device, you will have to replace the device with the new one in the Topology of GV Orbit Control. The swapping of a GVOP device for a replacement one is not supported.

GV Orbit Control

Device Property

(read only)

Name

GV Orbit Client

Parameter

Device Name

Network Host Name Host Name

Description

To Configure Device Information in GV Orbit Client

The following device parameter values are pushed from GV Orbit Client Client to GV Orbit

Control. As a result, in GV Orbit, these parameters are read only. The IP Friendly Name service persists this data in the GV Orbit Server. For more information, see

About Automatic

Sources or Destinations , on page 264 and

Device Properties Definitions , on page 250.

Description

Comment

This is the device’s Friendly Name . If no friendly name has been set, the device type

(product's model number) is shown.

This is also the Friendly Name value. If the

Description value is set in GV Orbit Client, then this value is used as the description in

GV Orbit Control. Otherwise, if no friendly description has been set in GV Orbit Client, the device's product model number is shown.

See

To Configure Device

Information in

GV Orbit Client , on page 231

231

Configuration Tasks

Adding Devices to a Topology

GV Orbit Client Version 2.0.0

User Guide

GV Orbit Control

Device Property

(read only)

Short Name

GV Orbit Client

Parameter

Short Name

Source and

Destination

For example, found in the Sources /

Destinations tab of the Multilevel Table in the Logical

Device Table . See

Logical Device Table

Tasks , on page 259.

The Logical Source /

Destination gets its name as follows:

• The spigot port name (if this value has been set in GV

Orbit Client), OR

• The device’s short name plus “ . “ plus spigot number.

Comment

If a friendly short name is set in the GV Orbit

Client, then this is the value set as the short name in GV Orbit Control. If no friendly short name is set, then the value for this

GV Orbit Control will be derived from the

Name parameter.

When the Automatic Sources and

Destinations property is set for a GVOP device (this is the default setting, see

GVOP

Devices , on page 226), the name of the

spigot’s source or destination set in GV Orbit

Client is applied, when the topology is

activated (see Activating a Topology , on page 253).

See

—

To Configure Source and Destination

Information in

GV Orbit Client , on page 233

Proceed as follows.

1 In GV Orbit Client, open the Devices tab.

2 Identify the device you want to configure.

3 Set the Device Name , Short Name , Host name , and Description parameters for the device.

232

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Adding Devices to a Topology

GV Orbit Control

Spigot Property

(read only)

Name

Short name

Port Number

This information is immediately updated for the same device in GV Orbit Control.

To Configure Source and Destination Information in GV Orbit Client

The following source and destination spigot parameter values are pushed from GV Orbit

Client to GV Orbit Control. As a result, in GV Orbit Client, these parameters are read only.

The IP Friendly Name service persists this data in the GV Orbit Server. For more information,

see About Automatic Sources or Destinations

, on page 264 and Device Properties Definitions , on page 250.

GV Orbit

Client

Parameter

Port Name

Comment

The name or identifier for this input or output port.

The Port Name in GV Orbit Client is used as the label to generate sources and destinations. If no value is specified in GV Orbit Client, GV Orbit

Control will use a combination of device name plus spigot number for the sources and destinations.

Short Name This is the spigot name commonly used in the

GV Orbit Control interface.

Port Number Uniquely identifies any source or destination across all devices. A source and a destination can have the same port number. However, two sources

/ destinations cannot have the same port number.

See

These values can be assigned automatically; see To Automatically Assign Port Numbers,

Short Names, and Port names in GV Orbit Client , on page 234. Proceed as follows.

1 In GV Orbit Client, open the Devices tab.

2 Select the device you want to configure.

3 Select the Spigots tab.

4 Identify the device’s source ( Src ) and destination ( Dst ) spigots in Mode . This reflects the device’s current configuration.

5 Set the Port Number , Short Name , and Port Name parameter for the spigot.

Enter the Port Number FIRST before entering other values. If you try to set a Short

Name or Port Name parameter for a spigot that doesn't have a Port Number , then the value you enter is not saved.

233

Configuration Tasks

Adding Devices to a Topology

GV Orbit Client Version 2.0.0

User Guide

This information is immediately updated for the same device in GV Orbit Control.

To Automatically Assign Port Numbers, Short Names, and Port names in GV Orbit Client

1 Select the Spigots tab.

2 Right-click the device’s name and select Assign Ports . Or click Assign Ports above the table to assign ports to all devices.

3 Set the following parameters in the Assign Port Mappings screen.

234

Parameter

Spigot Selection

Description

Select the scope of this screen.

Sources and Destinations: Apply automatic assignment changes to both sources and destinations.

Sources: Apply automatic assignment changes to sources only.

Destinations: Apply automatic assignment changes to destinations only.

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Adding Devices to a Topology

Parameter

Source Ports / Base port number

Destination Ports /

Base port number

Assignment Mode

Description

This tool uses a counter to assign a number to a port. This setting allows you to individually set the starting number for the first source and destination port from which the count will start.

Options

Select the way port numbers are assigned:

Synchronize source and dest assignments in discrete blocks: Assign port numbers such that the next highest available number is used to start numbering the first source and destination ports together in unison.

Ad hoc - use next free source or destination port: Separately assign port numbers, individually to sources and destinations, in sequence such that the next available port number is always used.

Automatically generate the parameter values for port and short names.

Create default port names: Set to automatically generate the value in the Port Name column as follows: [device name] + [S = source, D = destination] + [Port Number]

Create default short names: Set to automatically generate the value in the Short Name column as follows: [Port Number] + [S = source, D = destination] + [Port Number]

4 Click OK .

This information is immediately updated for the same device in GV Orbit Control.

To migrate GVOP Devices for IP routing

As of GV Orbit Control Client version 2.8.0 or higher:

• GVOP devices newly added to a Topology will no longer need to be connected to

Camera and Monitor devices and the logical sources/destinations will be automatically created when: the device is added to the topology, the topology is activated, and the status of the device’s control port is Online.

• The spigots of these devices can be re-named in GV Orbit Client. See Synchronization of Discovered GVOP Devices, Source, Destination, and Spigot Names made in GV Orbit

Client , on page 229.

GVOP devices configured in GV Orbit Control Client version 2.7.X or earlier are not automatically updated to use this new routing method when a project is migrated to

GV Orbit Control Client version 2.8.0 or higher. If you want to use the new behavior available to GV Orbit Control Client version 2.8.0 or higher, then you must manually migrate the devices.

235

Configuration Tasks

Using Quick Config

GV Orbit Client Version 2.0.0

User Guide

To migrate GVOP for IP routing, choose one of the following methods.

• Delete The Camera and Monitor linked to the GVOP device and then set the Automatic

Sources and Destinations parameter in the device’s properties. See

Device Properties

Definitions , on page 250.

• Delete the GVOP device, the associated Camera and Monitor devices and then add only the GVOP device back to the Topology.

Troubleshooting

Verify that the IP Friendly Name service is running; if:

• A device’s friendly name disappears from the GV Orbit Client.

• The device Name, Short Name and Network Host Name show the device’s primary IP address.

Ensure the IP Friendly Name service is installed and running on the GV Orbit Server. Refer to

Application Maintenance in the GV Orbit Admin Guide. See Related Documentation , on page 19.

Using Quick Config

Quick Config is used to make bulk configuration changes to the selected devices. See How to Identify if a Device Bubble is Selected or Not , on page 221. It can:

• Change a device’s logical level.

• Expose or un-expose the device’s streams.

Switches allow the changes to apply only to IP streams, SDI streams, inputs, or outputs. For example, Quick Config can be used multiple times: the first time to set the logical level for the device’s inputs, and then a second time to set another logical level for the device’s outputs.

To set the Quick Config options for the selected devices

1 Select the devices on the Topology you want to configure.

2 Click in the Topology Configurator’s toolbar.

236

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Using Quick Config

3 Set the following options.

Parameter

Logical level family

Description

Select the logical level to assign to the device’s source and destination streams. See also

Duplicating a Logical Level , on page 213.

Keep current level : leaves the device’s currently-assigned source and destination logical levels untouched.

Expose streams un-expose streams

Only certain devices support this property. When Expose Stream is set, it displays the streams for this device in the Logical Device Table. See

Logical Device Table Tasks , on page 259.

Set port redundancy Certain third-party devices that support port redundancy are not automatically recognized by GV Orbit Client to support redundancy.

When devices have been configured with two or more ports, set this

option to make the ports redundant in GV Orbit Client. See Setting

Port Redundancy for Many Devices at Once , on page 237.

Apply to IP streams Set to apply the above settings to IP network connections between devices.

Apply to SDI

Apply to Inputs/Rx

Set to apply the above settings to SDI connections between devices.

Set to apply the above settings to device destinations.

Apply to Outputs/Tx Set to apply the above settings to device sources.

4 Click OK .

Setting Port Redundancy for Many Devices at Once

Redundancy associates a port with another port to create a redundant network traffic flow path for failover protection. The associated port will not be available to carry other traffic.

For example, this is a requirement of a SMPTE ST 2022-7 network topology. See also

Configuring Network Switch Redundancy to Support SMPTE ST 2022 7 , on page 415.

Note: This feature is to only be used with third-party devices.

Certain third-party devices that support port redundancy are not automatically recognized by GV Orbit Client to support redundancy. For such devices, once they have been configured with two or more input / output connectors, use the Set port redundancy option in Quick Config (see

Using Quick Config , on page 236) to make the ports redundant

in GV Orbit Client. When completed, the Redundancy Port parameter in the Device

Properties for in / out 1 is in / out 2 and the Redundancy Port parameter for in / out 2 is in / out 1 . If there are 4 ports, then the Redundancy Port parameter for in / out 3 is in / out 4 and the Redundancy Port parameter for in / out 4 is in / out 3 and so on.

For more information about Device Properties, see

Defining Device Properties , on page 247.

237

Configuration Tasks

Using Quick Config

GV Orbit Client Version 2.0.0

User Guide

Use other Quick Config options to focus the redundancy on the required ports and port direction. For example, to make the selected device’s output IP streams redundant, set the

Quick Config as shown below.

238

Once these devices have been configured, use the Stream Configurator to set the IP

address for a large number of devices in an efficient way. See Stream Configurator Tasks , on page 339.

Example of how to set port redundancy for many devices at once

This procedure is an example for the following scenario:

• 100 IP analog-to-digital audio devices have been connected to the network switches with redundant connections.

• Each audio device supplies IP outputs for 16 channels of AES67 audio.

This example makes the IP output connections 1 and 2 redundant for each audio device in a device group of 100 generic IP Devices.

1 Open the Topology Configurator. See

Accessing the Topology Configurator , on page 219.

2 From the Device Library, drag an IP Device

onto the Topology Configurator. See To add a Virtual Device to a topology , on page 224.

3 Select the IP Device

. See How to Identify if a Device Bubble is Selected or Not , on page 221.

4 Set the device group’s properties as follows (see

Defining Device Properties , on page 247 and

Device Properties Definitions , on page 250):

• Set the number of output connections in # Output Connections to 2 .

• Set the logical levels for the device in Logical Level to AES67-16 .

• For a SMPTE ST 2110 device with three output streams, set the number of streams in # Streams Per Output to 3 .

• Set the logical levels for each of these streams to video, audio, and ancillary found under the individual stream properties.

• Set the IP address for each stream (video, audio, and ancillary) found under the individual stream properties.

5 Set the number of IP Device instances to 100 and set a name for the devices. See

To name a device and set the number of devices in the group , on page 225.

6 Click in the Topology Configurator’s toolbar while the device group is selected. See

To set the Quick Config options for the selected devices , on page 236.

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Methods to Link Devices in a Topology

7 Set the following Quick Config options:

• Set port redundancy

• Apply to IP streams

• Apply to outputs / Tx

8 Click OK .

When complete, the Redundancy Port parameter in the Device Properties for out 1 is out 2 and the Redundancy Port parameter for out 2 is out 1 for all device instances. The IP

address for these devices can be efficiently set with the Stream Configurator. See Stream

Configurator Tasks , on page 339.

Methods to Link Devices in a Topology

Once two or more devices have been added to the Topology Configurator (see Adding

Devices to a Topology , on page 224), devices can be linked together using the following

methods. Using one method does not prevent you from using another method in the future.

Linking Method Description

Quick Connect Automatically connects all unconnected ports of devices currently in the Topology

Configurator. Quick Connect options can limit automatic connections by stream, source, or destination type.

Manual Linking Create the links between devices manually. Manual linking allows precise control over link parameters.

You must also set the link’s physical connection parameters (sources and destinations) for each link.

See Procedure

Using Quick Connect to Link all

Devices in a Topology , on page 239.

Manually Linking the Devices in a Topology , on page 241.

Manually Setting the Link’s

Physical Connection

Parameters (Sources and

Destinations) , on page 243.

Using Quick Connect to Link all Devices in a Topology

Quick Connect automatically connects all unconnected ports of:

• All devices currently in the Topology Configurator when no devices are selected.

• The currently selected devices in the Topology Configurator.

See

How to Identify if a Device Bubble is Selected or Not , on page 221.

When necessary, it reads the device’s configuration to learn:

• Which ports / spigots have been configured as sources or destinations.

• The available IP ports, including control and management ports.

If a NMOS node has been added to the topology and has been configured and is working

(see

Adding NMOS Devices to a Topology , on page 394), Quick Connect will connect the

NMOS node’s management ports.

Quick connect also automatically connects the link’s physical connection parameters

(sources and destinations) for each link.

239

Configuration Tasks

Methods to Link Devices in a Topology

GV Orbit Client Version 2.0.0

User Guide

Once more devices have been added to the topology, or if a link has been cut, Quick

Connect can be run again to automatically connect those devices. Quick Connect will ignore pre-existing connections between devices.

Quick Connect has an option to automatically create sources and destinations for SDI inputs and outputs. SDI inputs are connected to Camera device groups, and outputs are connected to Monitor device groups. As a result, these SDI Camera and Monitor devices become available in the Logical Device Table as the device’s inputs and outputs. See

Logical

Device Table Tasks , on page 259.

However, as of GV Orbit Control Client version 2.8.0 or higher, for devices that use GVOP

(see

GVOP Devices , on page 226), the sources and destinations of such a device newly

added to a Topology will no longer be connected to Camera and Monitor devices by Quick

Connect. The sources and destinations of the GVOP device become immediately available in the Logical Device Table when it is added to the Topology and the topology is activated.

See

Synchronization of Discovered GVOP Devices, Source, Destination, and Spigot Names made in GV Orbit Client , on page 229 for more information.

Quick Connect is found in the Topology Configurator’s toolbar.

PREREQUISITES: The following must have been configured:

• If the system requires physical IP connections to be made, make sure you have at least one network switch device in your topology. If your network uses a second network switch to support redundancy (for example, to support SMPTE ST 2022-7), then you must have at least two network switch devices in your topology. See also

Network Switch Redundancy to Support SMPTE ST 2022 7 , on page 415.

• Ensure that core devices such as those listed in

Special Device Configuration Tasks , on page 347 have been added to the topology using drag-and-drop from the Virtual or

Discovered devices libraries and have been configured before using this tool. For example, GV Nodes, IPG-X901, IQMix / IQUCP25 cards, Audio Live, and Routers. See

Special Device Configuration Tasks , on page 347 for specific configuration information

about these devices.

• Add the remaining devices to the topology. See Adding Devices to a Topology , on page 224.

• The topology must be currently:

• Activated (see

• Unlocked (see

• All devices must be currently online. That is, no device should be shown in red in the

System Status. See

• The required logical levels have been created. See Accessing the Logical Level Editor , on page 210.

Using Quick Connect

Set the Quick Connect options before using Quick Connect. See Using Quick Config , on page 236.

240

GV Orbit Client Version 2.0.0

User Guide

1 Click in the Topology Configurator’s toolbar.

Configuration Tasks

Methods to Link Devices in a Topology

2 Set the following options.

Parameter

Do IP connections

Main network

Backup network

Description

Set to automatically create IP network connections between devices.

Select the name of the primary switch in your network.

If your network uses two network switches to support redundancy (for example, to support SMPTE ST 2022-7), then select the name of the

secondary switch in your network. See also Configuring Network

Switch Redundancy to Support SMPTE ST 2022 7 , on page 415.

Do SDI connections Set to automatically create SDI connections between devices.

As of GV Orbit Control Client version 2.8.0 or higher, this option no longer applies to devices that use GVOP (see

GVOP Devices , on page 226). See

Synchronization of Discovered GVOP Devices, Source,

Destination, and Spigot Names made in GV Orbit Client , on page 229

for more information. Topologies created in a previous GV Orbit Client version will not be changed to reflect this new behavior, unless the device is added again to the Topology.

3 Click OK .

Manually Linking the Devices in a Topology

Once the device groups are added to the Topology, the next step is to create links between them using the Link mode which allows you to link bubbles with a touch-based device.

Otherwise, if you are using a mouse and keyboard interface, you can link devices together using the following procedure while in the Edit mode as well.

To link devices or device groups in a topology

Open the required topology.

1 Select the required Area. See Selecting an Area , on page 203.

241

Configuration Tasks

Methods to Link Devices in a Topology

GV Orbit Client Version 2.0.0

2 Select the required topology. See Selecting a Graph , on page 204.

User Guide

3 Click the Link button at the top of the interface.

4 Select the first bubble in the pair you want to connect.

When the bubble is selected, the device is highlighted in blue and both the bubble’s input and outputs ports become available. Input ports are on the left side of the bubble. Output ports are on the right side of the bubble.

5 Select an input or output port on the bubble.

If the input port was selected, the output ports of all the available devices appear. If the output port was selected, the input ports of all the available devices appear.

6 Draw a line, with your mouse, between the ports of the two devices to make the connection between them. Or if you are using a touch-based device, the Link mode allows you to link bubbles together by dragging a bubble over others so that the connectors touch each other and then pull them apart to their final position.

242

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Methods to Link Devices in a Topology

Manually Setting the Link’s Physical Connection Parameters (Sources and

Destinations)

When a link is selected, the Physical Connection Table appears. It is in this table where you create the connections between device ports. When you add devices to a Topology and you then link two devices, you are indicating that the two devices in two groups are virtually connected. Therefore, you need a place to specify how these devices are actually

(physically) connected. This is achieved through the Physical Connections Table. It is in this table where you will actually specify that port1 of device1 that is part of group1 is connected physically with port1 of device1 of group2, for example.

To make a connection, you must start in the Builder tab, and then complete the action in the Candidate tab.

The Physical Connection Table uses connection icons as follows.

Icon State (status)

The stream is ready to be connected as it has been selected in the Builder tab.

The stream is connected.

Action

—

Connect: make the connection between the source and destination devices.

Disconnect: break the connection between the source and destination devices.

The Physical Connection Table uses port type icons as follows. A source’s output port type must be linked to the same input port type at the destination.

Port Type

Icon Description

The connection type is SDI.

The connection type is IP.

The connection type is MADI.

243

Configuration Tasks

Methods to Link Devices in a Topology

GV Orbit Client Version 2.0.0

User Guide

In the Physical Connection Table , more than one table row can be selected at a time; to add to a selection, use Shift or Ctrl to select a range of table rows or to add another row to the selection.

Builder Tab

The Builder tab shows all the outputs and the inputs available for connections. The output streams are shown on the left and the inputs are shown on the right for the selected link. By selecting streams in the Builder tab makes them available in the Candidate tab where they are then linked. For extra information about an input or output, set Router external labels .

The Router external labels are only available for router ports and not all device ports.

To associate a device’s output stream to another device’s input

1 Select one or more source output stream table rows that you want to link to destination’s input.

2 Drag the source output stream table rows onto the destination input(s).

The selected items become available in the Candidate tab.

You can bypass the Candidate tab as follows: you select all your destination, and all your sources and then with your right mouse button held down you drag the destinations over the sources. With this method, the only way to review your connections is by going into the

Connected tab and disconnecting the wrong/unwanted ones.

244

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Methods to Link Devices in a Topology

Candidate Tab

Once a device’s output stream has been associated to another device’s input in the Builder tab, you can review these associations to then select the ones you want to link together.

To link a device’s output stream to another device’s input

1 Select one or more table rows that you want to link the source’s output stream to the destination’s input.

2 When satisfied with your selection, click Connect at the top of the table.

Connected Tab

This tab shows the currently linked streams between the source’s output and the destination's input. Links can be disconnected in this tab.

To disconnect a device’s output stream from another device’s input

1 Select one or more table rows that you want to disconnect the source’s output stream to the destination’s input.

2 When satisfied with your selection, click Disconnect at the top of the table.

Other Tab

This tab will show you all the other connections that a device's ports has on another links.

For example, you have device1 with 20 ports, 10 are connected to device2 and 10 to device3. You select the first link and you connect the 10 ports. You select the second link on the Other tab you will see the first 10 ports that you connected.

245

Configuration Tasks

Deleting the Connection Between Device Groups

GV Orbit Client Version 2.0.0

User Guide

Deleting the Connection Between Device Groups

To delete the connection between devices

Open the required topology.

1 Select the required Area. See Selecting an Area , on page 203.

2 Select the required topology. See Adding Devices to a Topology , on page 224.

3 Select the Link button at the top of the interface.

4 Draw a line across the connection.

The scissor icon appears on the line and the link turns red.

5 Release the mouse.

The connection link is removed.

246

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Defining Device Properties

You set the parameters for the selected device in the Property Editor .

• The configuration parameters for most devices is intuitive and no further explanation is

required. See Device Properties Definitions , on page 250 for a primer.

• The configuration of certain devices requires advanced knowledge; see

Special Device

Configuration Tasks , on page 347 for more information about these devices.

Inheritance of Property Values from the Device Group Properties Tab

Certain parameter values in the Device Properties tab inherit their values from the corresponding parameter values in the Device Group Properties tab. This allows you to configure common parameters for a large number of devices at once with a default value.

Device Group Properties Tab

Parameter Values (Default)

Parameter Value

Inheritance

Device Properties Tab

Parameter Values

Device Properties Tab

Parameter Values

When you change the value of a parameter in the Device Properties tab such that it is now different from the corresponding value set in the Device Group Properties tab, the parameter will be displayed with an orange background. This is shown below.

The parameter’s value is a non-default value

(indicated by the orange highlight)

Click to reset the parameter’s value back to the default value set in the Device Group

Properties

To define properties for a device

1 Open the required topology. See Selecting a Graph , on page 204.

2 Select the device you want to configure.

247

Configuration Tasks

Defining Device Properties

The Property Editor is displayed on the right.

GV Orbit Client Version 2.0.0

User Guide

In this case, the IPG2 bubble is selected and the Device Group Properties tab is selected in the Property Editor .

3 Select the Device Properties tab to view the properties for the individual device. See also

Description of Common Device Properties , on page 348.

248

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Defining Device Properties

For example, for the Cameras, there is a Device Group Properties tab for the camera group and a Device Properties tab for each of the five cameras.

Camera Device Group Properties

The Device Group Properties tab sets the default parameter values to be passed down to each individual device in the Device Properties tab to save time. These default values can be overridden in the at the device level in the Device Properties tab.

Camera Device Properties

Note: All devices, device groups, and connections have properties.

249

Configuration Tasks

Defining Device Properties

GV Orbit Client Version 2.0.0

User Guide

Device Properties Definitions

This is a non-exhaustive overview of the device properties parameters.

Parameter

Name a

Description

Short Name

# Devices

Network Host Name a

Logical Level

Description

The name or identifier for this device instance.

The name or identifier for this input or output port.

For devices that use GVOP to configure them, see Synchronization of

Discovered GVOP Devices, Source, Destination, and Spigot Names made in GV Orbit Client , on page 229.

An optional description for the related input, output, or device. For

devices that use GVOP to configure them, see Synchronization of

Discovered GVOP Devices, Source, Destination, and Spigot Names made in GV Orbit Client , on page 229.

The nickname by which the input, output, or device is referred to everywhere in the system. For devices that use GVOP to configure them, see

Synchronization of Discovered GVOP Devices, Source,

Destination, and Spigot Names made in GV Orbit Client , on page 229.

The number of device instances in this device group.

The hostname is the unique name by which the device is known on the network. For devices that use GVOP to configure them, see

Synchronization of Discovered GVOP Devices, Source, Destination, and

Spigot Names made in GV Orbit Client , on page 229.

The logical level for this input or output. Click to change the logical level through the Logical Level Selector.

250

Select a logical level and click OK to change the level.

For more information about logical levels, to create, or modify logical levels, see

Logical Level Editor Tasks , on page 210.

The number of physical input port connections made to the device. # Input Connectors

# Output Connectors The number of physical output port connections made to the device.

# Streams Per Input The typical number of streams available on each physical input connection.

# Streams Per Output The typical number of streams available on each physical output connection.

# Streams The actual number of streams available on the selected physical input

/ output connection.

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Defining Device Properties

Parameter

Port Identifier

IP Address

Automatic Sources and Destinations

Description

This is the generic identifier of the port within GV Orbit Client.

The port’s IP Address.

This parameter is for GVOP devices (see

GVOP Devices , on page 226)

only: set to automatically use the names and the flow type configured for sources and destinations for this same device in GV Orbit Client in

real time when the Topology is activated (see Activating a Topology , on page 253).

This can be set for the device as a whole, or for individual spigots.

When a GVOP device is newly added to the topology, this parameter is now set by default.

For more information, see

Synchronization of Discovered GVOP

Devices, Source, Destination, and Spigot Names made in GV Orbit

Client , on page 229 and

About Automatic Sources or Destinations , on page 264.

For topologies created prior to GV Orbit Control Client version 2.8.0 or higher, this parameter is deselected for all pre-existing GVOP devices. If you set this parameter, then connected camera / monitor

groups will no longer work. See also To migrate GVOP Devices for IP routing , on page 235.

When deselected, the streams will be unexposed for the device. You can create custom logical sources/destinations by exposing the required streams first, using are the Stream Configurator. See

Stream

Configurator Tasks , on page 339.

Set to automatically create a destination by the system for the

specified streams. See also About Automatic Sources or Destinations , on page 264.

Automatic

Destination

Automatic

Destinations on

Inputs

Automatic

Destinations on

Outputs

Automatic Source

Automatic Sources on

Outputs

Automatic Sources on

Inputs

Set to automatically create a source by the system for the specified streams. See also

page 264.

About Automatic Sources or Destinations , on

Expose Streams When set, it displays the streams for this device in the Logical Device

Table. See Logical Device Table Tasks , on page 259.

The following methosa are available to set or clear this parameter at once:

• Quick Config; see Using Quick Config , on page 236.

• The Stream Configurator; see Stream Configurator Tasks , on page 339

SSM Address Enabled Shows if the source specific multicast address is enabled.

251

Configuration Tasks

Deleting a Device From a Topology

GV Orbit Client Version 2.0.0

User Guide

Parameter

SDP

Redundancy Port

Description

See

Using SDP Parameters to Take a Stream from a non-NMOS Device to an NMOS Device , on page 401.

Associates a port with another port to create a redundant network traffic flow path for failover protection. The associated port will not be available to carry other traffic. This is usually a requirement of a SMPTE

ST 2022-7 network topology.

ST 2022 7 , on page 415.

a.When an asterisk (*) is shown, parameter cannot be edited in GV Orbit Client. To edit this value, it must be done GV Orbit Client. For more information about this, see

Synchronization of Discovered

GVOP Devices, Source, Destination, and Spigot Names made in GV Orbit Client , on page 229.

Deleting a Device From a Topology

You must open a topology in the Topology Configurator before you can delete it.

To delete a topology

1 Select the Area. See

2 Select the topology. See Selecting a Graph , on page 204.

3 Select the device you want to remove.

The device is highlighted on the Topology.

4 Click Delete .

252

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Activating a Topology

By activating a topology makes GV Orbit Client connect to and activate all drivers to devices in the topology. For example, for a GV Node it means initiating the Densité and NP0016 connections and being able to control them. By activating a topology, panels will become active and light up.

You must select a topology and open it in the Topology Configurator before you can make it active.

Note: Only one topology can be active at a time for each area.

To make a topology active

1 Select the required Area. See Selecting an Area , on page 203.

2 Select the required topology. See Selecting a Graph , on page 204.

3 Click Active at the top of the Topology Configurator.

A confirmation message appears.

4 Click OK to continue.

253

Configuration Tasks

Making an Active Topology Inactive

The following changes occur.

GV Orbit Client Version 2.0.0

User Guide

• The topology name is displayed in red at the top of the Topology Configurator.

• A red lightbulb is displayed beside the topology name.

• A red box appears around the topology.

• Active is written on the bar.

• The topology is locked.

• The red Active bar is displayed on the thumbnail for the active topology.

Making an Active Topology Inactive

Only one topology can be active at a time for each area. You must open the active topology in the Topology Configurator before you can make it inactive.

To make an active topology inactive

1 Select the required Area. See Selecting an Area , on page 203.

254

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Making an Active Topology Inactive

2 Select the required topology. See Adding Devices to a Topology , on page 224.

3 Click the Active button at the top of the Topology Configurator.

A confirmation message appears.

4 Click OK to continue.

The following changes occur.

• The topology name no longer appears in red at the top of the Topology

Configurator.

• The red bar no longer appears at the base of the Topology.

• The topology is unlocked.

• The red Active bar is no longer displayed on the thumbnail for the active topology in the secondary window.

255

Configuration Tasks

Unlocking / Relocking a Topology

GV Orbit Client Version 2.0.0

User Guide

Unlocking / Relocking a Topology

A topology is locked automatically when you make it active. The lock only affects the current GV Orbit Control Client application. If multiple users have the same topology open, then each user can lock/unlock their client to do edits; this setting is not global to all open clients.

To unlock an active topology

1 Select the required Area. See Selecting an Area , on page 203.

2 Select the required topology. See Selecting a Graph , on page 204.

This opens the topology in the Topology Configurator.

3 Click the Lock button.

A confirmation message appears.

256

GV Orbit Client Version 2.0.0

User Guide

4 Click OK to continue.

Configuration Tasks

Locking an Unlocked Topology

When a topology is unlocked

• The lock icon is unlocked.

• If you have Edit permissions to the Topology Configurator for the selected area, you can modify the active topology.

Locking an Unlocked Topology

It is recommended to relock an unlocked topology, when you have finished your edits. This prevents you from inadvertently making edits on an active topology, such as selecting an object and pressing delete by accident.

Note: You can only lock an unlocked active topology. Inactive topologies cannot be locked or unlocked.

To lock a unlocked active topology

1 Select the required Area. See Selecting an Area , on page 203.

2 Select the required topology. See Selecting a Graph , on page 204.

257

Configuration Tasks

Locking an Unlocked Topology

This opens the topology in the Topology Configurator.

GV Orbit Client Version 2.0.0

User Guide

3 Click the unlocked Lock button at the top of the Topology Configurator.

No confirmation message appears.

The Lock icon switches to the locked state.

No one can edit the topology.

258

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Logical Device Table Tasks

Use the Logical Device Table task to view and configure the streams for the logical levels.

Audio shuffling and breakaway can also be configured to create multiple streams with different audio channels (for example, for multi-language support).

The Logical Device Table task is also where you create virtual crosspoints (XPTs) and to configure logical destination devices that are related to these virtual XPTs. See

Virtual Crosspoints (XPTs) , on page 276.

Megasource is a logical source device that is defined with multiple streams, under multiple logical levels, that can be routed to a logical destination with at least one matching logical level. This allows the definition of a source device with multiple locations in the topology, where the destination devices’ logical levels will determine which streams to route. For example, the user may connect Bars to two different routers, the destination logical level will determine which of these two source streams are to be used. This is usually the source stream that is local to the destination. Megasource also allows for UHD quad-link sources to share a single stream of 16 channel audio and ancillary data with the 4 video streams. See also

Using Megasource , on page 271 for more information.

Accessing the Logical Device Table task

To access the Logical Device Table Task

1 Open GV Orbit Control Client Stage. See

2 Select an area. See

3 Select a topology. See

Adding a Source to the Logical Level Table , on page 266.

4 Select Configuration > Logical Device Table .

259

Configuration Tasks

Accessing the Logical Device Table task

The Logical Device Table task appears.

GV Orbit Client Version 2.0.0

User Guide

260

The default streams for your topology, are displayed in the left hand column under

Stream Browser .

The following tabs are found in the right hand column under Multilevel Table .

Tab

Sources

Destinations

Virtual XPTS

Description

Show the currently configured sources. Sources are the available outputs for all the devices on your topology. See

Show the currently configured destinations. Destinations are the available inputs for all the devices on your topology. See

Adding and

Configuring a Destination , on page 271.

Show the currently configured virtual crosspoints. See

Virtual Crosspoints (XPTs) , on page 276.

Items in the Multilevel Table may be shown as grayed out and they cannot be edited.

These devices’ configuration properties come from GV Orbit Client. See

Synchronization of Discovered GVOP Devices, Source, Destination, and Spigot Names made in GV Orbit Client , on page 229.

5 Select the Sources tab to view the streams from the sources.

The Logical Level associated with the source are displayed. For information on the logical levels, see

Logical Level Editor Tasks , on page 210.

6 Scroll down in the Sources view to see all the levels for the selected source.

Stream Browser / Channel Browser

The Stream Browser shows all currently available steams. When a stream has two or more channels, the Channel Browser gives you access to the individual audio channels in a stream thereby allowing you to implement audio breakaway and audio shuffle for

independent audio routing. See Creating Logical Devices with Shuffled Audio , on page 274.

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Accessing the Logical Device Table task

To make use of this feature, streams will need to pass through a device that supports audio

breakaway/shuffling, such as GV Node or Audio Live. See Configuring a GV Node Device , on page 349 and

Configuring a Device that Supports Audio Breakaway/Shuffling such as

Audio Live , on page 437.

The selected stream

Shows detailed information about this stream

The Channel Browser shows the available audio channels for the selected stream

Note: if more than one stream is selected in the

Stream Browser, then the

Channel Browser shows all channels derived from the selected streams

Each audio channel can be dragged onto a different level in the Multilevel table to shuffle the source’s audio

The Stream Browser and Channel Browser menu have the following menu options.

Icon

Select All

Description

Selects all items in the Stream Browser.

Clear All Deselects all items in the Stream Browser.

Channel Browser Shows the Channel Browser (found in the Stream Browser only).

Show Long

Names

Automated

Sources / Destinations

Toggles between the display of the long name or short name of the stream and device names.

Creates all the audio levels in the Multilevel Table for the selected

example of how to use this feature.

Channels per Device Set how many channels are assigned per logical device when you have enabled the Automated Sources or Automated Destinations options.

For example, if you select 64 streams in the channel browser, and you set Channels per Device to 16, and then you click the Automatic

Sources option, it will automatically create 4 logical sources for you.

The first 16 streams are assigned to A1-16 of the first source, the next

16 are assigned to A1-A16 of the second source, and so on.

Likewise, if you select 64 streams in the channel browser, and you set

Channels per Device to 8, and then you click the Automated Sources option, it will automatically create 8 logical sources for you. The first 8 streams assigned to A1-A8 of the first source, the next 8 assigned to

A1-A8 of the second source, and so on.

Similarly, if you select 64 streams, and set Channels per Device to 2, it will create 32 sources.

261

Configuration Tasks

Accessing the Logical Device Table task

GV Orbit Client Version 2.0.0

User Guide

Icon

Filter

Information

Description

Filters the list. Note that the filter operates on the currently shown list items according to the Show Long Names setting.

See

Filtering Lists, Table Columns, Sources, and Destinations , on page 285.

Shows detailed information about the stream / channel.

Multilevel Table Menu

The Multilevel Table menu has the following menu options.

Icon

New

Delete

Description

Creates a new Source / Destination / Virtual XPTS in the Logical Device

Table. See Adding a Source to the Logical Level Table , on page 266,

Adding and Configuring a Destination , on page 271, and

Virtual Crosspoints (XPTs) , on page 276.

Removes the currently-selected Source / Destination / Virtual XPTS in

the Logical Device Table. See Deleting a Source, Destination, or Virtual

XPTS , on page 274.

Select All

Clear All

Levels

Selects all rows in the Multilevel table.

Deselects all rows in the Multilevel table.

Hide automatic sources

Hide automatic destinations

Shows the Logical Level Selector. This allows you to set the logical levels that are to be shown in the Multilevel Table.

See

Setting the Logical Levels to be Displayed in the Multilevel Table , on page 265.

Shows or hides automatic sources / destinations in the Logical Device

Table.

Virtual

Destinations

Reset all filters The columns of the Logical Device Table have filters. These buttons

Reload all filters clear all filters and restores the previous filters.

See

Filtering Lists, Table Columns, Sources, and Destinations , on page 285.

Export

Shows the available destinations available from previously-configured virtual XPTS.

Exports the Logical Device Table to a CSV file. See

Exporting a Logical

Device Table , on page 274 or Selecting all Devices in the Logical

Device Table for Export , on page 274.

label

Restore default

Show Long

Names

When a source or destination has been renamed, this resets the name to its original label.

Toggles between the display of the long name or short name of the stream and device names.

262

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

About the Multilevel Table and GVOP Devices

Icon

Show Redundant

Streams

Refresh

Description

For each stream in the Multilevel Table:

• When a source or destination has redundant IP streams (as may be the case with an SMPTE ST 2022-7 network for example), for each stream in the Multilevel Table, this toggles between the display of the

IP address for the primary stream and the display of the IP address for the secondary stream.

• When this option is selected, and the stream has a secondary IP address to be shown, the stream’s secondary IP address is shown with a blue background to identify that the secondary stream’s IP address is currently being shown.

Streams that have no redundancy (no secondary IP address) are unaffected by this option.

Reloads the Logical Device Table’s contents.

About the Multilevel Table and GVOP Devices

When a device uses GVOP (see

GVOP Devices , on page 226), and the

Automatic Sources and Destinations parameter is enabled in the device’s properties (this is the default setting;

see Device Properties Definitions , on page 250), GV Orbit automatically creates sources and

destinations for the GVOP device. When the device is online, the device's configuration is read from the GVOP device in real time and updates the sources and destinations in the

Logical Device Table's Multilevel Table.

For example, if the Flow Type for a video flow is assigned to SMPTE2022 in a GVOP device, then in the Multilevel Table, this flow appears as an SDI flow for this device and the SMPTE

ST 2110-20, 2110-30, and 2110-40 flows are not used. Likewise, if an SMPTE ST 2110-30 audio flow is set to None, then in the Multilevel Table, this flow is no longer applied to the audio level for the given source or destination.

In addition, if the IP Friendly Name service is running on the GV Orbit Server, the custom naming configuration for the device and its spigots

Multilevel Table.

1 is read in real time and it updates the names and descriptions of the sources and destinations in the Logical Device Table's

Synchronization of

Discovered GVOP Devices, Source, Destination, and Spigot Names made in GV Orbit Client , on page 229.

1.Custom naming for the device and its spigots is carried out in GV Orbit Client.

263

Configuration Tasks

About Automatic Sources or Destinations

GV Orbit Client Version 2.0.0

User Guide

About Automatic Sources or Destinations

Certain sources and destinations are created automatically by GV Orbit Client, such as edge devices: cameras, monitors, and so on. Automatic sources or destinations are created when the following properties (as applicable) have been set in the device’s property editor:

• Automatic Sources and Destinations

• Automatic Destination

• Automatic Destinations on Inputs

• Automatic Destinations on Outputs

• Automatic Source

• Automatic Sources on Outputs

• Automatic Sources on Inputs

The A icon is shown next to the name for the row in the Multilevel Table to indicate that the source or destination was automatically created by GV Orbit Client.

Source or destination was automatically created by GV Orbit

Client

This yellow bar indicates that the name is no longer the automaticallygenerated name

Note: You cannot delete a default source from the Logical Level Table. However, you can modify the levels associated with the source. Also, you can modify or delete the sources that you create.

Automatically created sources’ and destinations’ name can be re-named by double-clicking the name field. A yellow bar indicates that the name of the source or destination is no longer the automatically-generated name. Click Restore default label to revert back to the automatically-generated name.

Such automatically generated sources and destinations have icons to represent the source or destination type when shown, for example, in the Panel Configurator, Category Configurator, or elsewhere. A key to a few source and destination icons is shown below. These icons are derived from the icon used to represent the device in the Device Library and on the Topology

Configurator. See

Adding Devices to a Topology , on page 224 .

Icon

Description

Camera source

Logical device source

Encoder source

Monitor destination

Default destination for a panel. See

Creating a Single-Destination Work Flow

Panel , on page 315.

264

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Setting the Logical Levels to be Displayed in the Multilevel Table

If you try to delete an automatic source or destination from the Logical Device Table, the following message is displayed at the bottom of the task.

To remove an automatic source or destination, you must deselect the following properties

(as applicable) in the device’s Property Editor:

• Automatic Sources and Destinations

• Automatic Destination

• Automatic Destinations on Inputs

• Automatic Destinations on Outputs

• Automatic Source

• Automatic Sources on Outputs

• Automatic Sources on Inputs

Setting the Logical Levels to be Displayed in the Multilevel Table

You can show or hide the Logical Level shown in the Multilevel Table. For example, once you have created custom levels in the Logical Table Editor, you might want to show those levels while hiding others that are not of interest for the moment. Showing or hiding

Logical Levels in the Multilevel Table is used to facilitate bulk assignment of sources and destinations in the Multilevel Table. See

Bulk Assigning Logical Levels in the Multilevel

Table , on page 271.

To modify the logical levels associated with a source

1 Select a Source in the Logical Device Table. See Accessing the Logical Device Table task , on page 259.

2 Click the Logical Levels icon at the top of the table.

A secondary window opens displaying the levels for the selected source.

265

Configuration Tasks

Adding a Source to the Logical Level Table

GV Orbit Client Version 2.0.0

User Guide

3 Select one or more levels you want to use for the selected source.

4 Click OK .

The columns in the Multilevel Table adjust to add the ones you have selected.

Adding a Source to the Logical Level Table

By default, the logical device table displays the sources in the selected topology. You can add a logical device to the table that is not on the topology. You would then have the option of switching to the new logical device in place of the existing device.

To add a source to the logical level table

1 Open the logical level table for the required topology.

2 Click New at the top of the Multilevel Table .

A secondary window appears.

3 Enter the required information in the Base Name , Start Index , and Count fields .

4 Click OK .

266

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Configuring Streams for New Sources

New sources are created. The Base Name is displayed under the Name and

Description fields. The number of new sources created corresponds to the number you enter in the Count field.

In the example, five new sources are created. The name for each device begins with the base name CAM100. A number is appended to the base name. This begins with the starting index and increases by one for every number in the count.

Configuring Streams for New Sources

After creating new sources, the next step is to configure the streams for them. Different streams can be assigned to different levels, so that a source is composed of streams from different devices (to do implicit breakaway).

267

Configuration Tasks

Configuring Streams for New Sources

GV Orbit Client Version 2.0.0

User Guide

For example, the column you drop a stream on in the Multilevel table selects the part of the stream to use to create the logical device. This is shown below for a stream from the Stream

Browser.

SDI Video

Video

Component

Audio

Components

Audio

Channel 1

Audio

Channel 2

Select the row before dropping a destination onto it

Stream Drop onto

Multilevel Table

Column

SDI

A1 to A16

ANC

V-ANC

Description

This fills all levels (video, 16 audio channels (A1 to A16), ANC, and

V ANC) with the equivalent levels from the SDI video stream.

This takes the video level only from the SDI stream.

This takes the audio levels only from the SDI or audio stream for all 16 audio channels (A1 to A16).

This takes the first audio channel from the SDI or audio stream.

This takes the ANC level only from the SDI stream.

This takes the V ANC level only from the SDI stream.

268

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Configuring Streams for New Sources

For instance, you could create a source with Video from a GV Node and the audio from an

IPG-3901, or IPG-4901. You do this by assigning the GV Node stream under the SDI column, and the IPG-3901, or IPG 4901 stream under the Audio ( A ) column. If audio breakaway/shuffling is required to complete the path, GV Orbit Client will automatically choose a route through Audio Live for example.

Configuring Streams for Audio Live Audio Channels

When using Audio Live in your topology (see

Configuring a Device that Supports Audio

Breakaway/Shuffling such as Audio Live , on page 437), you can:

• From the Stream Browser, drop the audio stream onto the audio ( A ) column. This is shown above.

• From the Channel Browser, drop one or more audio channels from the stream onto the

A1 to A16 column(s). To open the Channel Browser, see Stream Browser / Channel

Browser , on page 260.

SDI Video

Video

Component

Audio

Components

Audio

Channel 1

Audio

Channel 2

Symbols for currently active Audio Breakaway and Shuffle

Symbols are used in the name of a logical device to identify if the audio has been shuffled or there is an audio breakaway currently active.

Symbol

Breakaway

Shuffle

Description

This icon appears next to the name for the row to indicate that the audio comes from another stream source.

This icon appears next to the name for the row to indicate that one or more audio levels have been exchanged for another audio level from the same stream. To shuffle the audio, see

Creating Logical Devices with Shuffled Audio , on page 274.

To configure streams for the new sources

1 Open the Logical Device Table for the required topology.

In the left hand column under Stream Browser , the default streams for your topology are displayed.

269

Configuration Tasks

Configuring Streams for New Sources

GV Orbit Client Version 2.0.0

User Guide

2 Add sources to the Logical Level Table. See

Adding a Source to the Logical Level Table , on page 266.

3 Select a source’s row to which you want to add a stream.

270

4 Drag a stream onto the source.

Video

Component

Audio

Components

In the above image, a stream is added to a source for its video component. Drag the same stream or another stream from the Stream Browser to a source to add its audio components.

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Bulk Assigning Logical Levels in the Multilevel Table

The Stream Browser and Channel Browser have filters that allow you to refine the stream selection shown. See

Filtering Lists, Table Columns, Sources, and Destinations , on page 285. It

is often possible that by using filtering, streams can be grouped together so that they can be dropped in bulk onto the Multilevel Table, on a row or a column.

• To bulk drop streams on to a row, select one row first and then select two or more streams to drop onto the row.

Select the row before dropping a destination onto it

• To bulk drop streams on to a column, select two or more rows first and then select two or more streams to drop onto the column.

Adding and Configuring a Destination

The procedures for adding and configuring destinations are the same as for adding and

configuring sources. For details, see Adding a Source to the Logical Level Table , on page 266 and

Configuring Streams for New Sources , on page 267.

The IP Clean Switch option enables routing of an IP source to a local GV Node destination for a vertically accurate switch.

Using Megasource

Megasource changes GV Orbit Client’s pathfinding rules to match exact logical levels before applying best match logic. This allows you to create logical sources where the same or different streams can be added to the logical level columns that share the different custom logical levels. Megasource only applies to sources with multiple stream/level pairings and the filtering happens when a normal destination is used in a route.

When doing a take, the GV Orbit Client’s pathfinding algorithm will attempt to find an exact level match between the logical source and the logical destination. Failing to find an exact match, it attempts to find a compatible level match as it currently does. If there is more than one possible compatible match (ambiguous take), it will fail the take because we don't know which stream should be used on the logical destination.

Note that a UHD 4K take is a subset of this feature where there are four SDI levels per logical source and logical destination (one SDI level for each quad-link or two-sample interleave division substream component). See

Creating the Logical Levels for a UHD 4K Routing

Setup , on page 214 for more information.

271

Configuration Tasks

Using Megasource

GV Orbit Client Version 2.0.0

User Guide

For example, you have three SDI signals from the same source. One signal is full resolution

1080p video, the second signal is 720p video, and the third is 480p video. One destination is for the full resolution 1080p video, the second destination is for the 720p video, the second destination is for the 480p video, where the destination devices’ logical levels will determine which streams to route.

The following is an example of how to do this.

Using Megasource

1 Create the following Topology to use for this example. See Adding Devices to a

Topology , on page 224.

2 Create three copies of the SDI Logical Level called SDI-A , SDI-B , and SDI-C in the

Logical Level Editor . See

Duplicating a Logical Level , on page 213.

3 Click in the Multilevel Table , Sources tab, of the Logical Device Table to hide the

automatically-generated sources. See Multilevel Table Menu , on page 262.

4 Click in the Multilevel Table , Sources tab, of the Logical Device Table to create a new source (shown in this example as Megasource ). See

Adding a Source to the Logical

Level Table , on page 266.

5 In the Logical Device Table, select a source’s row to which you want to add the streams.

See

To configure streams for the new sources , on page 269.

272

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Using Megasource

6 From the Stream Browser of the Logical Device Table , drag the three source streams onto the Multilevel Table. The first stream represents 1080p video, the second stream represents is 720p video, and the third stream represents 480p video.

Select a row before dropping the streams onto it

7 Click in the Multilevel Table , Destinations tab, of the Logical Device Table to hide the automatically-generated destinations. See

Multilevel Table Menu , on page 262.

8 Click in the Multilevel Table , Destinations tab, of the Logical Device Table to

create new destinations, one for each level (1080p, 720p, and 480p video). See Adding a

Source to the Logical Level Table , on page 266.

9 In the Logical Device Table, select the first source’s row to which you want to add the streams.

10 From the Stream Browser of the Logical Device Table , drag the first destination stream onto the Multilevel Table.

11 In the Logical Device Table, select the second source’s row to which you want to add the streams.

12 From the Stream Browser of the Logical Device Table , drag the second destination stream onto the Multilevel Table.

13 In the Logical Device Table, select the third source’s row to which you want to add the streams.

14 From the Stream Browser of the Logical Device Table , drag the third destination stream onto the Multilevel Table.

Select the row before dropping a destination onto it

15 Test the configuration by making takes between a logical source and destination that use the Megasource

source. See Performing a Take in Router Control , on page 467. See

in Pathfinder that the correct source resolution is received by each destination. See

Viewing Information about the Destinations , on page 451.

273

Configuration Tasks

Deleting a Source, Destination, or Virtual XPTS

GV Orbit Client Version 2.0.0

User Guide

Deleting a Source, Destination, or Virtual XPTS

You can delete any source, destination, or virtual XPTS that you have created.

To delete a source, destination, or virtual XPTS

1 Open the Logical Device Table task for the required topology.

2 Select the Sources tab, the Destination tab, or virtual XPTS tab according to what you are deleting.

3 Select the sources, destinations, or virtual XPTS in the table.

Note: You can delete one or more sources or destinations at the same time.

4 Click the Delete icon .

Exporting a Logical Device Table

You can export the data in your logical device table in a csv file.

To export a logical device table

1 Open the Logical Device Table task for the required topology.

2 Select the rows you want to export.

3 Click the Export icon .

4 Navigate to the folder where you want to save the file.

5 Click Save .

Selecting all Devices in the Logical Device Table for Export

You can select all devices in the logical device table, for example, to export the Device

Table’s configuration data to a csv file.

To select all the devices and save their configuration data

1 Open the Logical Device Table task for the required topology.

2 Click the Select All icon .

3 Click the Export icon .

4 Navigate to the folder where you want to save the file.

5 Click Save .

Creating Logical Devices with Shuffled Audio

You can define the audio configurations for logical sources by selecting any audio sub- stream (from a MADI stream or an AES67 stream from an Audio Live device for example) in the Logical Device Table and change its pre-assigned level directly in the table.

Audio live permits the breakaway of audio feeds. To do this, add an Audio Live device to your network and to your topology. See

Configuring a Device that Supports Audio

Breakaway/Shuffling such as Audio Live , on page 437. The audio channels for the sources

become available under the Channel Browser for those streams (see Stream Browser /

Channel Browser , on page 260).

274

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Creating Logical Devices with Shuffled Audio

For example:

• You may have audio embedded on the first 8 audio channels for English-language program and the last eight channels for French-language program. In this scenario, the first logical source would have the implicit stream for audio in only the first 8 audio logical levels (that is, associated to audio levels 1 to 8) and the second logical source would have those same first 8 logical levels of audio explicitly defined with the same stream, but the audio logical levels are associated to audio levels 9 to 16.

• A user defined destination logical device may include MADI audio. In order to define the destination as utilizing the logical source audio from logical levels audio 1 and audio 2 onto logical levels audio 11 and audio 12, it is necessary to place the destination device stream under logical levels audio 11 and audio 12, but define the source audio of the stream as coming from source logical levels audio 1 and audio 2, respectively.

To create logical devices with shuffled audio

1 Create one or more new logical devices. See Adding a Source to the Logical Level Table , on page 266.

2 Drag a stream from the stream browser (for example, an audio stream) and drop it on its corresponding level on the newly created logical device (audio level, A ). Once the steam is dropped on its level, all the corresponding sub-levels will be automatically filled in ( A1 to A16 ). The table will show the main stream on the audio level and up to

16 other sub-levels contained in this level.

Shuffle

Button

If the selected row/cell is eligible for shuffling, a shuffle button will appear in the column header.

3 Select the row and click the shuffle button to open a logical level selector with the filtered compatible levels available for selection.

275

Configuration Tasks

Configuring Virtual Crosspoints (XPTs)

GV Orbit Client Version 2.0.0

User Guide

4 Select a new level to assign to the stream. If for example, the stream is on audio1 and you want to change it to audio9, select the audio9 level from the stream. Click OK .

Configuring Virtual Crosspoints (XPTs)

Without virtual XPTs, only one route can be made for each task. Virtual XPTs are used when multiple outputs are required to be switched to the same source in a single take .

Destination 1 Destination 2 Destination 1 Destination n

Virtual XPT

Source Source

Virtual XPTs can be used to:

• Show user-friendly device names on the operators’ control panels. For example, the name of the virtual XPT is shown on control panels when used.

• Hide implementation details from the operator(s). For example, in a transparent fashion, an output signal is also sent to a monitor.

Virtual XPTs are used for the following two primary applications:

• Monitoring: to follow the source routed to a given destination and to route that same source to other destinations as needed.

• Utility DA (distribution and amplifier): to allow for a configurable virtual destination/source that can be routed to other real destinations.

276

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Configuring Virtual Crosspoints (XPTs)

The following virtual XPT functional behaviors are by design:

• A take with a virtual XPT will fail if the path to the source does not exist and as a consequence the virtual source will fail. The status (Tally) will not reflect this.

• A take with a virtual XPT’s destination will be ignored if the take fails.

• A logical destination can only be added to one virtual XPT destination at a time. Once a real destination has been added to a virtual XPT, it is no longer available to be used with other virtual destinations. A pop-up message is shown if you try to add a logical destination that has already been added to another virtual XPT. Click OK to remove the logical destination from the previous virtual XPT and add to it the new virtual XPT.

• You can only route virtual sources to unrelated virtual destinations that are not associated with the same virtual XPT. This allows you to increase the number of logical destinations devices that can be switched with a single route. Routing a logical source device to the virtual destination of another virtual XPT will route said source to all logical destination devices that the virtual source is routed to. Routing that virtual source to another virtual destination, will mean routing the original logical source device to all destination devices that the corresponding virtual source was routed to, as well.

Destination 2-1 Destination 2n

Destination 1-1 Destination 1n Virtual XPT 2

Virtual XPT 1

Source

Routing a logical source device to the virtual destination of another virtual XPT

• A virtual XPT can have up to 100 real logical destinations.

• The status of a virtual XPT is shown in the Path Manager. See

Accessing the Path

Manager , on page 449.

• Adding a logical destination device to a virtual XPT changes the status of the destination to the virtual source - with the logical source device content being routed to the logical destination device(s). Removing the logical destination device from a virtual XPT, will change the status of that destination to the logical source device.

277

Configuration Tasks

Configuring Virtual Crosspoints (XPTs)

GV Orbit Client Version 2.0.0

User Guide

Virtual XPT Use Scenario 1

In this scenario, the physical level is set up so that any source routed to destination Z will be taken to the following destinations: R, S, and T.

Virtual XPT Setup

Operator “takes” A to Z

Result: Operator still sees A as taken to Z

If the operator takes A to Z, the software “discovers” that source Z is virtually routed to R, S, and T. Therefore, it routes A to R, S, and T as real routes.

Here, a source was taken to multiple destinations with a single take, and that fact was concealed from the operator. The operator’s control panel reports that A was taken to Z.

The Path Manager can be used to know the actual path that was internally used by the router; see the

1 In the Topology Configurator, activate the topology. See Activating a Topology , on page 253.

Other inputs can be taken to Z with a similar result: that source will be taken to destinations

R, S, and T.

Virtual XPT Use Scenario 2

In this scenario, the virtual XPT setup is the same as for scenario 2.

Virtual XPT Setup Operator “takes” A to Z Result: Operator still sees A as taken to Z

If the operator takes B to Z, the software “discovers” that source Z is virtually routed to R, S, and T. Therefore, it routes B to R, S, and T as real routes.

The operator’s control panel reports that A was taken to Z. The operator executed a single take.

278

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Configuring Virtual Crosspoints (XPTs)

This scenario illustrates that any time an operator takes a source to virtual XPT destination n , the router actually takes the source to the real destinations “connected” to virtual XPT source n .

To create Virtual XPTs

Virtual XPTs are created in the Logical Device Table task.

2 Open the Logical Device Table task. See

Accessing the Logical Device Table task , on page 259.

3 Select the Virtual XPTs tab.

4 Click New

5 Enter a name for the new virtual XPT and click OK .

Optionally, a range of virtual XPTs can be created: The Name parameter is the prefix for the generated virtual XPTs. The Start Index is the index starting value, and the End

Index is the last index value for the virtual XPT range.

279

Configuration Tasks

Configuring Virtual Crosspoints (XPTs)

GV Orbit Client Version 2.0.0

User Guide

The new virtual XPT is added to the Multilevel Table under the Virtual XPTS tab.

A new logical source and a new logical destination are created automatically in the system with the name of the virtual XPT.

Virtual source and destination filters are available for you to filter on virtual XPTs when

configuring the panel, categories, and router control user interfaces. See Filtering Lists,

Table Columns, Sources, and Destinations , on page 285

6 Add the default destinations for the virtual XPT. Select the virtual XPT and then click

Destinations .

280

A list of all currently available destinations appears.

7 Select the default destinations the virtual XPT will use and click OK .

Mon3

Mon4

Mon5

Mon6

Mon7

Mon8

VXPT

In this scenario, the physical level is set up so that any source routed to destination

VXPT will be taken to the following destinations: Mon5 , Mon6 , and Mon7 .

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Configuring Virtual Crosspoints (XPTs)

Once you have created one or more Virtual XPTs, you can start using them in Router

Control.

To perform a take with a Virtual XPT

You must first create and activate the topology in the Topology Configurator. You perform

takes with a Virtual XPT in Router Control. See also Performing a Take in Router Control , on page 467.

1 In the Topology Configurator, activate the topology. See Activating a Topology , on page 253.

2 Create a virtual XPT in the Logical Device Table task. See To create Virtual XPTs , on page 279. As an example, in this procedure, the name of the virtual XPT is

VXPT .

3 Open Router Control. See

Accessing the Router Control Task , on page 466.

Virtual XPT Source Virtual XPT Destination

The Current Virtual XPT Destinations

The default virtual XPT destinations that were configured in the Logical Device Table

are shown by selecting the virtual XPT destination. See To create Virtual XPTs , on page 279.

4 To route Cam1 to Mon5, Mon6, and Mon7 using the virtual XPT VXPT , perform a take

Cam1 to destination VXPT .

Cam1

Cam2

Cam3

Cam4

Cam5

Cam6

Mon3

Mon4

Mon5

Mon6

Mon7

Mon8

VXPT

281

Configuration Tasks

Configuring Virtual Crosspoints (XPTs)

GV Orbit Client Version 2.0.0

User Guide

First click the destination virtual XPT VXPT and then click Cam1 and finally click Take .

S: Current source

P: Pending source

D: Destination

The destination virtual XPT VXPT button shows the current source.

Virtual XPT Source

The Path Manager can be used to know the actual path that was internally used by the router; see the

1 In the Topology Configurator, activate the topology. See Activating a Topology , on page 253.

To dynamically add a Virtual XPT destination

Destinations can dynamically be added to a virtual XPT. In this example, Mon8 , and Mon9 are added to the virtual XPT VXPT ’s destination.

2 First click the source virtual XPT and then click Mon8 and finally click Take .

3 First click the source virtual XPT and then click Mon9 and finally click Take .

282

The current destinations for the selected virtual XPT are updated.

Click to revert to the default virtual XPT destinations configured in the Logical Device Table

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Configuring Virtual Crosspoints (XPTs)

how to use the controls available in this window. The Path Manager can be used to know the actual path that was internally used by the router; see the

Path Manager

Tasks , on page 448.

To dynamically remove a Virtual XPT destination

Destinations can dynamically be removed from a virtual XPT. In this example, Mon9 is removed from the virtual XPT VXPT ’s destinations. This is done by assigning the destination to be removed to another source.

1 In the Topology Configurator, activate the topology. See Activating a Topology , on page 253.

2 First click the destination Mon9 then click Cam9 and finally click Take .

Minimize and Expand Virtual XPT Destinations

In the Router Control Task, when a virtual XPT is routed to another virtual XPT, the second virtual source is nested in the first virtual XPT. See

Routing a logical source device to the virtual destination of another virtual XPT , on page 277.

As shown below, when Minimize Virtual XPT is selected, the VXPT2 virtual XPT is shown minimized.

283

Configuration Tasks

Configuring Virtual Crosspoints (XPTs)

GV Orbit Client Version 2.0.0

User Guide

As shown below, when Expand Virtual XPT is selected, all destinations are shown, including the nested destinations of all other virtual XPTs.

These are the now-visible destinations of VXPT2

to use the other controls available in this window.

284

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Filtering Lists, Table Columns, Sources, and Destinations

Virtual source and destination filters are available for you to filter on virtual XPTs when configuring the panel and category configurator user interfaces. To show virtual XPT sources or destinations only, enable the Show virtual setting in the filters dialog only.

Click to open filter tool

Deselect these filters

Select this filter

The functions available in a filter adapt to the screen in which the filter is found. For example, the Stream Browser has filters to allow you to filter streams that come from either input or output ports.

Click to open filter tool

Filter text

Select this filter only

Filter Parameter

Reload filter []

Reset filter

Filter by Stream

Description

Reloads the previously-used filter.

Clears the text in the filter function.

Filter by the stream’s name.

Filter by Device Group Filter by the device group’s name.

Filter by Device Filter by the device’s name.

Filter by Port Filter by the port’s name.

285

Configuration Tasks

Filtering Lists, Table Columns, Sources, and Destinations

GV Orbit Client Version 2.0.0

User Guide

Filter Parameter Description

Filter by Logical Level Filter by the Logical Level’s name.

Show SDI

Show IP

Show MADI

Show Inputs

Show results where the connection type is SDI.

Show results where the connection type is IP.

Show results where the connection type is MADI.

Show results where the connection direction is an input.

Show Outputs

Show automatic

Show custom

Show virtual

Show results where the connection direction is an output.

Show automatically-created sources and destinations.

Show user-created sources and destinations.

Show virtual XPTS.

286

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Category Configurator Tasks

Use the Category Configurator to make it easier to manage the sources in your topologies.

Creating groups of categories, based on type or use, is useful when you have multiple resources.

Categories are used to group sources and destinations together thereby allowing them to be accessed quickly on a panel, either by adding a category button or by using keyboard

Accessing the Category Configurator

To access the Category Configurator Task

1 Open GV Orbit Control Client Stage. See

2 Select an area. See

3 Select a topology. See

Creating Categories for the Sources and Destinations in Your Topology , on page 289

4 Select Configuration > Category Configurator .

287

Configuration Tasks

Accessing the Category Configurator

The Category Configurator task opens:

GV Orbit Client Version 2.0.0

User Guide

288

See the following Category Configurator procedures:

•

•

Assigning a Keystroke Label to a Source or Destination , on page 292

•

Creating a Keystroke Label , on page 293

Sources & Destinations Menu

The Sources & Destinations menu has the following menu options.

Icon

Select All

Select Alias

Description

Select / deselect all source or destination items.

Select the Alias you want to use to identify Source and Destination streams in GV Orbit Client’s interface.

Aliases are created in the Alias Editor. See Adding Aliases , on page 463.

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Creating Categories for the Sources and Destinations in Your Topology

When you first open the Category Configurator, the Home tab appears in the Sources and

Destinations tab.

To create a category for your sources

1 Open the Category Configurator task for the required topology. See

Accessing the

Category Configurator , on page 287.

2 Click Add .

3 The Enter a name for the new category window appears:

4 Enter a name for the new category and click OK .

The new category is added to the top of the Category Configurator column.

5 Click Sources or Destinations to view the available sources / destinations.

All the sources / destinations in the selected topology are displayed. This includes the logical sources you created in the Logical Device Table task. See

Logical Device Table

Tasks , on page 259.

289

Configuration Tasks

Creating Categories for the Sources and Destinations in Your Topology

6 Select the newly created category.

GV Orbit Client Version 2.0.0

User Guide

290

The category is added to the lower part of the center column under Category Content.

7 Drag the sources / destinations from the Sources & Destinations column to the

Category Content area.

Alternatively, you can drag a source/destination to the created Category button.

When a Category contains only Sources or it contains only Destinations, the Category’s symbol will change accordingly to show the type of content. For example, this allows

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Re-ordering Category Content you to have two Categories with the same name where one only has Sources and the other Category only has Destinations and you can still distinguish them.

Table 1: Meaning of Category Icons

Icon Description

The category:

• Is empty (contains no Sources or Destinations).

• Contains a mix of Sources and Destinations.

The category only contains Sources.

The category only contains Destinations.

8 Click Home to toggle between Sources (Green) or Destinations (Orange) as necessary.

Re-ordering Category Content

The sequence of category content (Sources and Destinations) can be re-ordered so that when a category is used on a panel, the Sources and Destinations will be shown in the order that you want it to be.

1 Add Sources and Destinations to a Category. See Creating Categories for the Sources and Destinations in Your Topology , on page 289.

2 Re-order the Sources and Destinations in a Category: in the Category Content, drag the

Source and Destination tiles into the oder you want them to be.

3 In the Panel Configurator, add a panel and configure it. See Panel Configurator Tasks , on page 294.

4 Add the Category to a panel button. See Adding Resources to the Panel , on page 306.

5 For each panel button you have added a Category to, select the panel button individually and set the Sort Mode property to Manual it in the button’s Property

Editor. See

Setting the Properties for Panel Resources , on page 310.

291

Configuration Tasks

Assigning a Keystroke Label to a Source or Destination

GV Orbit Client Version 2.0.0

User Guide

Assigning a Keystroke Label to a Source or Destination

A keystroke label can be added to sources and destinations once they have been added to a category. Assigning a keystroke label to a source or destination allows a user to bring up categories by using a keypad on a panel. For example, if you have 100 categories in your system, a panel can bring up category 37 by pressing 3 then 7 instead of browsing through dozens of panel pages. This also applies to selecting sources or destinations. For instance,

Cam17 can be directly accessed by pressing 1 then 7 on the panel instead of searching for the Cam17 button.

To add a keystroke label to a source or destination

1 Open the Category Configurator task for the required topology. See

Accessing the

Category Configurator , on page 287.

2 Click a Category to show sources and destinations that have been configured for that category, shown in Category Content .

3 From the Keystroke Label Editor drag one or more labels onto a source or destination to create a unique sequence for that source or destination.

The Keystroke Editor shows the current keystroke label for the selected source or destination.

Edit a Source or Destination Keystroke Sequence

The Keystroke Editor allows you to change the selected source or destination’s keystroke label. Setting for automatically assigning keystroke labels to a source or destination can also be set.

292

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Creating a Keystroke Label

Set Auto Add to automatically assign a keystroke to a source or destination as it is added to a category. Click Options to configure this feature.

Proceed as follows to delete a keystroke.

1 Select a source or destination shown in Category Content .

2 Select a keystroke in the Keystroke Editor and click Delete.

Proceed as follows to delete all keystrokes.

1 Select a source or destination shown in Category Content .

2 Click Clear All in the Keystroke Editor .

Creating a Keystroke Label

You can assign custom keystrokes to a source or destination. Create a keystroke label to do so.

To creating a keystroke label

1 Open the Category Configurator task for the required topology. See

Accessing the

Category Configurator , on page 287.

2 In the Keystroke Label Editor, click New .

The Create a new keystroke label window opens.

3 Set the keystroke label as required and click OK .

293

Configuration Tasks

Panel Configurator Tasks

GV Orbit Client Version 2.0.0

User Guide

Panel Configurator Tasks

This allows you to add buttons and behaviors to a panel. Those buttons represent sources, destinations, levels, groups and various operations that can be saved under specific configurations and then pushed to a software or hardware panel.

For an example of how to setup and use a panel, see Panel Configuration Example Using

Categories with Custom Navigation , on page 319.

Accessing the Panel Configurator

To access the Panel Configurator Task

1 Open GV Orbit Control Client Stage. See

2 Select an area. See

3 Select a topology. See

Creating a New Panel , on page 296 or

4 Select Configuration > Panel Configurator .

The Panel Configurator task appears:

294

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Accessing the Panel Configurator

Page Editor Menu

The Page Editor menu has the following menu options.

Icon

Manage

Add Page

Home Page

Delete Page

Cut

Copy

Paste

Copy Category

Properties

Refresh

Select All

Clear All

Clear

Description

Creates multiple templates for hardware or software panels of various models. Then, you can add the template to a panel that you have added to the topology. A pre-existing panel can be duplicated; see

Viewing another Panel , on page 299.

Adds a page to the panel’s layout. See

Adding Panel Pages , on page 302.

Returns to the panel’s previous page, when the panel configuration has two or more pages.

Goes forward to the panel’s next page, when the panel configuration has two or more pages.

Make the currently shown page the panel’s Home page. This is available when the panel’s configuration has two or more pages and you currently are not on the Home page. To add panel pages, see

Adding Panel Pages , on page 302. To set a page to be a panel’s home

page, see

step 4 on page 302.

Removes the currently-selected page from the panel’s configuration.

This is unavailable for the panel page currently designated as the

Home page.

Cuts the contents from the panel’s currently selected button(s).

Copies the contents from the panel’s currently selected button(s).

Pastes the clipboard contents to the panel’s currently selected button.

See

About the Copy / Cut / Paste Buttons , on page 295.

Copies the properties of another category to the panel’s currently selected category. First configure a category’s properties according to your needs, and then copy the properties to other categories using

this feature as needed. See Copying the Properties from one Category to Another , on page 312.

Reloads the Panel’s contents.

Selects all the panel’s contents.

Deselects all the panel’s contents.

Removes all the selected panel’s contents.

About the Copy / Cut / Paste Buttons

Copy / cut / paste buttons can be used from one panel page to another and from one panel to another. Copy / cut / paste can be done using either the icons in the toolbar or through keyboard shortcuts: <ctrl>+X, <ctrl>+C, and <ctrl>+V.

You can multi-select using the <Shift> / <Ctrl> key:

• By holding the <Shift> key and selecting the first and the last button/cell on the panel, all buttons/cells in between are selected. If the first and the last selected

295

Configuration Tasks

Creating a New Panel

GV Orbit Client Version 2.0.0

User Guide buttons/cells are in different lines, the entirety of the lines will be selected between the two buttons/cells.

• By holding the <Ctrl> key, you can toggle the selection by clicking individual buttons/cells on the panel.

Creating a New Panel

You can create multiple templates for hardware or software panels of various models. Then, you can add the template to a panel that you have added to the topology. A pre-existing

panel can be duplicated; see Viewing another Panel , on page 299.

To create a new panel

1 Open GV Orbit Control Client Stage. See

2 Select an area. See

3 Select a topology. See

. See Accessing the Panel Configurator , on page 294.

4 Select Configuration > Panel Configurator

296

5 Click Manage .

A secondary window opens.

6 Click New .

GV Orbit Client Version 2.0.0

User Guide

The New window appears.

Configuration Tasks

Creating a New Panel

7 Enter meaningful text in the Name , Summary , and Description fields to identify the panel.

8 Select the required model from the list.

9 Click Create .

The new panel is added to GV Orbit Client.

Panels can have more than one page. When the panel is shown with a red outline, this indicates that the Home Page is being shown.

A Red outline indicates that the Home Page is currently being shown

10 Configure the panel’s properties; see Configuring a Panel’s Properties , on page 300.

297

Configuration Tasks

Duplicating a Pre-Existing Panel

GV Orbit Client Version 2.0.0

User Guide

Duplicating a Pre-Existing Panel

A pre-existing panel can be copied to reuse that panel’s configuration properties and then you only need to modify the necessary panel properties as required for the new application. The new panel configuration will have a new name and any changes to that configuration will not affect the original panel configuration that you chose to base its configuration on.

To duplicate a Pre-Existing Panel

1 Open GV Orbit Control Client Stage. See

2 Select an area. See

3 Select a topology. See

. See Accessing the Panel Configurator , on page 294.

4 Select Configuration > Panel Configurator

298

5 Click Manage .

A secondary window opens.

6 Click on a pre-existing panel that you want to duplicate and then click Duplicate .

GV Orbit Client Version 2.0.0

User Guide

The New Name window appears.

Configuration Tasks

Viewing another Panel

7 Enter a name to identify the panel.

8 Click Ok .

9 Configure the panel’s properties; see Configuring a Panel’s Properties , on page 300.

Viewing another Panel

When you have configured two or more panels, you can change between configuring them as follows.

To view a Pre-Existing Panel

1 Open GV Orbit Control Client Stage. See

2 Select an area. See

3 Select a topology. See

. See Accessing the Panel Configurator , on page 294.

4 Select Configuration > Panel Configurator

5 Click Manage .

299

Configuration Tasks

Configuring a Panel’s Properties

A secondary window opens.

GV Orbit Client Version 2.0.0

User Guide

6 Click on a pre-existing panel that you want to view.

The configuration for the selected panel appears.

Configuring a Panel’s Properties

Set the basic parameters to configure the panel.

To Configure a Panel’s Properties

1 Click 1 next to Zones [1] .

300

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Configuring a Panel’s Properties

The following properties can be configured for the panel. See also

Source and Destination Aliases with a Panel , on page 309.

Parameter

Name

# Zones

Description

The name or identifier for this panel

Alias group

(Destinations)

Alias group (Sources)

Sets the number of zones available for the selected panel. The default is 1, however you can add more as needed.

Buttons can be assigned to any zone. Each zone can then act as an separate panel. For example, you can have two zones on a panel, and each zone has its own sources, destinations, and take button.

Selection and take in one zone will not affect the other zone. Zones can be assigned to the button in the Property Editor when the button is selected in the Resources for Topology .

Shows the currently selected destination / source alias to use on the panel button’s / interface to use in place of the short labels. See

Using

Comment An optional comment about this panel.

Default Destination Shows the currently selected default destination for this panel. See

Creating a Single-Destination Work Flow Panel , on page 315.

Description An optional description for this panel.

Display 24 characters When deselected, panel button labels are limited to a maximum length of 8 characters.

When selected, panel button labels are limited to a maximum length of 24 characters. This option is useful when using source / destination aliases that usually are longer than 8 characters. This will disable the destination status on the destination buttons. The display will only show the system names. The level buttons will only show the system names. To create source / destination aliases, see

Alias Editor Tasks , on page 462. See also

Using Source and Destination Aliases with a Panel , on page 309.

Multi-select

Panel Definition

When deselected, the panel will allow multiple selection of destination buttons. This enables an operator to take a single source to multiple destinations at once.

When selected, only one destination can be selected at a time.

The current panel’s model number that was added in

step 6 on page 296.

Select Persist When deselected, the source and destination selections are cleared when a take is complete.

When selected, the source and destination selections are maintained when a take is complete.

This is parameter is selected by default. This parameter is not zonespecific.

301

Configuration Tasks

Adding Panel Pages

GV Orbit Client Version 2.0.0

User Guide

Adding Panel Pages

A panel can have one or more pages. Each page can be tailored to a function or purpose.

Navigation buttons can be added to the page so the panel user can go page to page. There

is more than one way for a panel user to navigate to another page; for example, see Panel

Configuration Example Using Categories with Custom Navigation , on page 319.

To add a panel page

1 View a panel. See Viewing another Panel , on page 299.

2 Configure the panel. See

Configuring a Panel’s Properties , on page 300.

3 In Tool , navigate to Home > Pages and click Add Page .

A new page is added to the Pages list in the Tool pane.

4 To make a panel page the Home page, select the page in Tools and click Home .

A Red outline indicates that the Home Page is currently being shown

302

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Adding Actions to a Panel

In the Tool list of panel pages, the Home icon is shown for current Home page. A red outline around the panel image indicates when the Home page is currently being shown.

Tool Page Icon Description

The panel page is currently not a home page.

The panel page is currently a home page.

Adding Actions to a Panel

A panel can support a number of actions that must be added to it before the action becomes available to the user. For example, add a Take button to a panel as follows.

1 Open the Panel Configurator task for the required topology. See

Creating a New Panel , on page 296.

2 Select the required Panel.

3 Drag the Take tool from the Tools column onto a panel button.

4 If the panel has a display, drag the Page Up and Page Down tools from the Tools column onto panel buttons (some panels have two dedicated buttons set apart for this purpose next to the display).

See the panel’s documentation for more specific details about the behavior of panel buttons. The following table provides summary information.

Built-in Panel

Actions

Blank

Cancel

Description

Some buttons can span multiple pages. This is use to force a button to appear on a higher-level page only.

Cancels a Keystroke. Removes all keystrokes in the selection.

303

Configuration Tasks

Adding Actions to a Panel

GV Orbit Client Version 2.0.0

User Guide

Built-in Panel

Actions

Category

Description

This either (1) displays a category’s device list or (2) displays a “suffix page.” A category button is associated with either a source category or destination category. The button text is normally the category name and is short as space is limited.

Clear Clears the Keystroke. Removes the last key stroke.

Default Destination Provide the tally for the default destination when the Show Tally parameter is set in the button’s property.

Set a destination to which all takes made on a panel will be made. See

Creating a Single-Destination Work Flow Panel , on page 315.

Destination Select a destination.

Destination Item This is used to do an indexed take. Use Multiple destination items to preset a multiple take. Each destination item will have a different index.

Destination Status Provide the tally for the selected destination. See also

Creating a Single-

Destination Work Flow Panel , on page 315.

Indexed Take

Keystroke

Level

Make a take on the Destination item.

Create a Keypad to select Source or Destination by their numbers.

Level Map

• Used to display the level of the destinations.

• Used to display the preset of a selected level.

• Used for audio Break away and audio shuffling.

This cross-connects levels. The function is typically used to shuffle audio channels, for example, to connect AES1/2 to AES3/4.

List Item Used in conjunction with the Category list button to create an area where the source or destination will be displayed in a list.

Load Home Page Takes the panel user to the Home page. To set a page to be a panel’s home page, see

step 4 on page 302.

Load Page

Lock

Multi-Select

Loads any panel page. To add a panel page, see

Adding Panel Pages , on page 302

This prevents changes to the panel settings, especially router crosspoints.

When the panel is locked, the button array becomes blank except for the

Panel Lock button which becomes high-tally red. The button is a toggle: press the ‘Lock’ button to lock the panel. Press it again to unlock the panel.The button text is either “Lock” or “Unlock.”

information about the use and limitations of this feature.

Allows the selection of multiple destinations.

Page Down

Page Up

Continue forward to browse down a category list (this does not change the page). Normally you would not use this button directly but let the category list place it automatically, unless you need to map to a special button on a panel.

This scrolls the alphanumeric display down.

This scrolls the alphanumeric display up.

304

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Adding Actions to a Panel

Built-in Panel

Actions

Panel Lock

Protect

Reset Panel

Salvo

Select

Select Persist

Source

Quick Source

Take

Description

This locks the panel. When set, the panel button turns red and all other panel buttons are unavailable. Press the button again to release the lock.

Browse backwards to move up a category list (this does not change the page). Normally you would not use this button directly but let the category list place it automatically, unless you need to map to a special button on a panel.

This is a toggle that sets or clears a protect on the current destination device. The protect can be removed at the panel that originally set the protect, at any panel that has the same user ID, or by a forced release at any panel.

• Note: a protect prevents others from routing to a destination; a lock prevents anyone—even the user who issued the lock—from routing to the destination.

• You may lock a protected destination, but you cannot change a locked destination to a protected destination directly.

You must first unlock it. The ‘Destination Protect’ button text is normally

Dest Protect and when a selected MD destination is protected, the button legend becomes Dest Unprotect .

information about the use and limitations of this feature.

Reset the panel to its initial state and go to the home page.

This executes a system salvo. A salvo is a pre-defined set of commands.

The button text is the salvo’s mnemonic. Pressing the salvo button puts the panel in “salvo” mode. To confirm that you want to execute the salvo, press a ‘Take’ button. When you press the take button, the salvo begins executing immediately. Salvos are typically short in duration. If you want to cancel the salvo before it executes, press the salvo button again. If you press an ‘Information’ button while the panel is in salvo mode, the panel presents the salvo commands on the display. You may scroll the display to view the entire salvo.

See

Creating Salvos , on page 470.

After selecting Source or Destination from a Keypad, the user presses

Select. This confirms the choice.

The destination stays selected after a Take.

This selects a source. Note that the quick source button selects a source and also performs an immediate take. Quick Source and Source buttons are similar, except that the Quick Source performs a take. Be aware of which buttons are quick sources so you do not perform an accidental take.

In X-Y mode, a take button routes the preset source device(s) on selected levels to the selected destination device. In MD mode, a take button routes the preset source device(s) to the selected destination device(s) on all levels.

305

Configuration Tasks

Adding Resources to the Panel

GV Orbit Client Version 2.0.0

User Guide

Adding Resources to the Panel

The Resources for Topology menu has the following menu options.

Icon

Quick Source

Default

Destination

Select All

Clear All

Select Alias

Description

This is shown only when Sources is selected. When enabled, the sources that are dragged onto the panel are quick sources, meaning the operator does not need to press the take button to do the take.

The take is done as soon as the source is selected on the panel.

This is shown only when Destinations is selected. This makes the selected destination the default destination for the panel. When set:

• The panel’s properties shows the currently selected destination, found under Default Destination .

• The icon on the destination changes to thus indicating its default destination status.

To remove the Default Destination, select the destination set as the

Default Destination and click .

See

Configuring a Panel’s Properties , on page 300.

See

Creating a Single-Destination Work Flow Panel , on page 315.

Selects all the available resources.

Deselects all the available resources.

Select the Alias you want to use to identify Source and Destination streams in GV Orbit Client’s interface.

Aliases are created in the Alias Editor. See Adding Aliases , on page 463.

306

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Adding Resources to the Panel

In the Tool list of panel pages, the Home icon is shown for current Home page. A red outline around the panel image indicates when the Home page is currently being shown.

Tool Page Icon Description

The currently configured sources. Sources are the available outputs for

all the devices on your topology. See Adding a Source to the Logical

Level Table , on page 266.

Sources may be identified by an icon that represents the source type when it was automatically created as a virtual device. See

About

Automatic Sources or Destinations , on page 264 for more information.

The currently configured destinations. Destinations are the available

inputs for all the devices on your topology. See Adding and

Configuring a Destination , on page 271.

Destinations may be identified by an icon that represents the destination type when it was automatically created as a virtual device.

See

About Automatic Sources or Destinations , on page 264 for more

information.

When a destination has been set to be the default destination for a panel, it is designated by the Default Destination icon . See

Creating a Single-Destination Work Flow Panel , on page 315.

Logical levels allow for the creation of shuffling and breakaways.

For more information about logical levels, see Logical Level Editor

Tasks , on page 210.

Shows the available categories. See:

• Table Category Configurator Tasks on page 287.

•

Table 1 Meaning of Category Icons on page 291 .

•

Panel Configuration Example Using Categories with Custom

Navigation , on page 319

A keystroke label can be added to sources and destinations once

they have been added to a category. See Assigning a Keystroke

Label to a Source or Destination , on page 292.

Click a zone to see which panel buttons are assigned to that specific zone. The number of zones is set in the # Zones parameter in the panel

properties. See Configuring a Panel’s Properties , on page 300.

Some panel buttons support the display of more than one color. For buttons that support colors, the button’s color is used to show the current operating state. The color used for a button to represent any

one of the given states can be changed. See Changing a Button’s Color used to Represent a State

, on page 313 and Changing a Button’s

Default Color used to Represent a State , on page 314.

When a salvo is triggered, it executes a list of pre-configured actions. See

Creating Salvos , on page 470

To add panel resources

1 Open the Panel Configurator task for the required topology. See

Creating a New Panel , on page 296.

307

Configuration Tasks

Adding Resources to the Panel

GV Orbit Client Version 2.0.0

2 Select the required Panel. See

Viewing another Panel , on page 299.

User Guide

The resources that can be added to the panel are displayed in the lower section of the center column under Resources for Topology .

3 Click on resource type to begin adding individual resources to the panel such as

Sources , Destinations , or Levels .

For example, click Sources to add cameras and other types of sources.

All the sources available in the topology are listed. This includes the logical sources you

created in the Logical Device Table task. See Logical Device Table Tasks , on page 259.

308

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Adding Resources to the Panel

4 Select a resource and drag it to one of the panel buttons at the top of the column. More than one resource can be added at a time; to add to a selection, use Shift or Ctrl to select a range of resources or to add another resource to the selection.

5 For each panel button you have added a resource to, select it individually and set the properties for it in the Property Editor. For a Category, see

Setting the Properties for

Panel Resources , on page 310.

6 Add resources from Destinations , Levels , and Keystrokes to the panel as required.

Note:

Only use the video+ancillary (V-ANC) logical level button unless you are routing in

SMPTE ST 2110 mode. For SMPTE ST 2110 mode, you can individually use the Video or the Ancillary logical level buttons.

To directly control a GV Node’s internal matrix, you must use the video + ancillary logical level button for video breakaway.

Using Source and Destination Aliases with a Panel

Aliases can be used for a panel to change the name of sources and destinations from short labels to the labels of the corresponding alias. First you must create one or more source and destination aliases; to create an alias, see

Alias Editor Tasks , on page 462.

1 Under Resources for Topology , click Sources or Destinations .

2 Select from the Select Alias drop-down list the alias to use for this panel instance.

309

Configuration Tasks

Adding Resources to the Panel

GV Orbit Client Version 2.0.0

User Guide

3 If the aliases are longer than 8 characters, consider setting the Display 24 characters option for the panel in the Panel’s Property Editor

. See Creating a New Panel , on page 296.

Setting the Properties for Panel Resources

When a resource has been added to a panel’s button, you can select the button to then configure the properties for it.

Parameter

Category

Category filter

Display Mode

Description

Selects the category instance for the selected button.

Typically this should be the category that was dragged onto the panel in Resources for Topology. It can be changed here for another category.

A category can contain sources and/or destinations. Select the ones you want to be displayed.

Both : display sources and destinations.

Destinations : display destinations only.

Sources : display sources only.

Keystroke : if the category item has keystrokes assigned to it, you can select this option.

List : if not select List; this will list all sources/destinations in the category.

310

GV Orbit Client Version 2.0.0

User Guide

Parameter

Exit Mode

Exit Page

Name

Page

Sort Mode

Configuration Tasks

Adding Resources to the Panel

Description

Select how the panel user will be returned once they have made a category item selection or Take. The category item selection is displayed once the panel user has pressed the category selection button.

Never : The panel user will remain in the same page where the category item selection is made. Other navigation buttons must be added to the page so that the panel user can navigate from the page.

With this option, the Exit Page parameter below is not applicable.

Preset : Once the panel user has made a selection in the category items, the panel user is immediately returned to the previous page

(where the category selection button is located). This is the default.

With this option, the Exit Page parameter can send the panel user to any other page (see below).

Take : When the category items page has a Take button, the panel user is returned to the previous page (where the category selection button is located) once they select a category and then click Take. With this option, the Exit Page parameter can send the panel user to any other page (see below).

See

Panel Configuration Example Using Categories with Custom

Navigation , on page 319 for an example of how to use this parameter.

In conjunction with the Exit Mode parameter, this parameter changes the Preset and Take return navigation to any other panel page. This can be used to save the panel user from making extra panel presses to navigate back to the Home page, for example.

In order to use this feature the Exit Mode must be set to Preset or

Take . See above.

When the value for this parameter is blank (empty), the Exit Page parameter has no effect. This is the default.

When the value for this parameter is a panel’s page, the panel behavior is to take the panel user to the selected panel page once they have pressed the category item selection or Take button. See

Panel

Configuration Example Using Categories with Custom Navigation , on page 319 for an example of how to use this parameter.

Set the name that will appear in the category button instead of the category name.

Sets the page to display when the category button is pressed. It should typically contain either List Item buttons or Keystroke buttons.

If the list display mode is selected, this will:

A-Z: show the sources/destinations in alphabetical order.

Manual: show the sources/destinations in the order you have set for the Category. see

Re-ordering Category Content , on page 291.

Z-A: show the sources/destinations in reverse alphabetical order.

311

Configuration Tasks

Adding Resources to the Panel

GV Orbit Client Version 2.0.0

User Guide

Parameter

Keystroke

Zone

Description

These options are present for the List Item buttons. If the list of sources/destinations in the category is greater than the number of list item buttons added to the page, some buttons will be used as next or previous buttons. This is determined automatically by GV Orbit Client, but you can override the default by specifying that a button can be used as a next or previous button if need be.

This parameter is available with the Keystroke button. It specifies the keystroke associated with the button.

Select the zone for the category button.

Buttons can be assigned to any zone. Each zone can then act as an separate panel. For example, you can have two zones on a panel, and each zone has its own sources, destinations, and take button.

Selection and take in one zone will not affect the other zone. Zones can be assigned to the button in the Property Editor when the button is selected in the Resources for Topology .

Copying the Properties from one Category to Another

Copies the properties of the panel’s currently selected category to one or more other categories used on the panel. The scope (the type of parameters) of the copy can be controlled.

To copy the Properties from one Category to Another

1 Add two or more categories to the panel. See Adding Resources to the Panel , on page 306.

2 Configure the properties of one of the categories according to your needs. See

Setting the Properties for Panel Resources , on page 310.

3 Select the category from which you want to copy the properties from.

4 Click Copy Category Properties to copy the properties of the selected category to other categories.

Icon

Select All

Description

Selects all the available categories.

312

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Adding Resources to the Panel

Icon

Clear All

Description

Deselects all the available categories.

Property to copy Select from the dropdown list the property parameter field you want to copy.

• All Properties: Copy all the following properties to the selected categories: Display Mode , Exit Mode , Page , Category Filter , Zone , and Sort Mode .

• Display Mode , Exit Mode , Page , Category Filter , Zone , and Sort

Mode : This allows you to copy only a specific property parameter while leaving the remaining property parameters for the categories untouched.

For more information about these category property parameters, see

Setting the Properties for Panel Resources , on page 310.

5 Select one or more categories to which you want to copy the properties to. Click OK .

Changing a Button’s Color used to Represent a State

1 Click a button that has a behavior previously associated to it (a blank button will not work). See

Adding Actions to a Panel , on page 303 and

Adding Resources to the Panel , on page 306.

313

Configuration Tasks

Adding Resources to the Panel

2 Click on the Colors resource type.

GV Orbit Client Version 2.0.0

User Guide

All available state colors for the selected button are shown on the lower half.

3 Drag a color from the color pallet (shown on the upper half) onto any one the state colors on the lower half.

A Def bar appears on the state color which indicates the default color. Double-click the state color to revert to this default color.

Changing a Button’s Default Color used to Represent a State

The default color used by all buttons for a behavior state can be changed when an across the system change is necessary.

1 Click the Custom Color Settings icon .

2 Click a behavior that you want to configure, for example, Destination .

314

3 Drag a color from the color pallet (shown on the upper half) onto any one the state colors on the lower half.

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Creating a Single-Destination Work Flow Panel

Certain panel buttons support fewer colors. The 7, 3, and 2 Color Buttons columns will show how your color choice will be implemented for these reduced color-range buttons.

Creating a Single-Destination Work Flow Panel

A panel can be configured as an input selector: the panel shows a range of sources, from which the panel operator can choose from, and the selected source will always be routed to a single specific, pre-defined static destination for monitoring. Note that in this example, there are no destination buttons defined on the panel.

To create a single-destination work flow panel

This example shows how to create a single-destination work flow panel.

1 Create a new panel. See

Creating a New Panel , on page 296.

2 Add the sources and a Lock and Take buttons to the panel. See Adding Resources to the

Panel , on page 306 and

3 Select the destination to which all sources will be routed for this panel: In Resources for

Topology , Destinations , select a destination to which any selected source will be sent.

4 Set this destination as the default destination: click Default Destination . The icon on the destination changes to .

In the panel properties, the Default Destination parameter shows the selected destination as its value.

315

Configuration Tasks

Adding the New Panel to the Topology

GV Orbit Client Version 2.0.0

User Guide

5 On the Home page, add a Destination Status from the Built-In Tool to a panel button.

This panel button provides the tally of the default destination to the panel operator.

See

To add a Virtual Device to a topology , on page 224.

The panel operator can now select a source that will be routed to the Router-Out 1 In 1 destination. The Destination Status button updates with the current tally for the destination.

Adding the New Panel to the Topology

After you have configured one or more templates for your software or hardware panels, you can add a panel to your topology.

To add a panel to the topology

1 Add the Panel to the Topology: from the Device Library , Virtual Device , find the Panel bubble. See

316

2 Select the bubble for the panel device to configure the panel’s Device Group Properties in the Property Editor

Parameter

Name

# Devices

Description

The name or identifier for this panel instance.

The number of panel instances in this device group.

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Adding the New Panel to the Topology

Parameter Description

Network Host Name When one or more panels are managed by DCNM through the media network, set a unique network identifier for these panels so as to be able to push policies to them.

An optional description for this panel’s control port.

Advanced >

Description

Advanced > Logical

Level

Advanced > Default

Connector Type

The logical level for this panel. See page 210.

The panel’s connector type.

Logical Level Editor Tasks , on

3 Select Device Properties and click New next to Control Port at the top of the

Property Editor and select NV96XX Panel Control from the list.

The Panel Control Port

tab appears. See also Description of Common Device

Properties , on page 348.

Parameter

Name

Description

Logical Level

Panel Behavior

Panel Definition

Panel User

Reset Device

Required a



Description

The name or identifier for this panel instance.

An optional description for this panel instance.

The logical level for this panel. See

Logical Level Editor

Tasks , on page 210.

Select the name of the panel you used when you created

the panel (see Creating a New Panel , on page 296) from

the drop-down list.

When you have selected the Panel Behavior parameter, this is the panel’s model number that was selected when you created the panel. It is read-only.

Select the panel’s user name from the drop-down list. For further information, see

Administration Tasks , on page 473.

A panel Admin or Operator user has the ability to release locks made by another user. Whereas non-Admin or non-

Operator users can only release locks they made themselves.

Destinations Lock/Protect is performed through the panel and if a destination is currently locked by another user, any take to this same destination will fail.

If a specific router port is locked/protected but not linked to any destination within the Control System, the

Lock/Protect status won't be exposed in the Control

System and in fact is not releasable.

more information.

When the topology is inactive (see

Making an Active

Topology Inactive , on page 254), click to reset the device.

317

Configuration Tasks

Adding the New Panel to the Topology

GV Orbit Client Version 2.0.0

User Guide a.This parameter must be configured in order for the panel to become functional.

4 Select Panel Control Port tab to make the following properties visible. See also

Description of Common Device Properties , on page 348.

Parameter

Panel Control Port >

Name

Panel Control Port >

Description

Panel Control Port >

Connection State 1 / 2

Required a Description

The panel’s control port name.

An optional description for this panel’s control port.

Panel Control Port >

PanelID



Connection State 1 shows the connection status of the panel with the primary server of a server group.

Connection State 2 shows the connection status of the panel with the secondary server of a server group. See

the topology is inactive (see Activating a

unknown:

Topology , on page 253) or the panel does not have

network connectivity to the GV Orbit Client server(s).

offline: the panel does not have network connectivity to the GV Orbit Client server(s).

online: the panel is connected to the GV Orbit Client server(s).

Each control panel must have been configured with a unique Panel ID number.

Enter the Panel ID that corresponds with the physical panel that is to be used with this panel instance.

a.This parameter must be configured in order for the panel to become functional.

5 In the hardware or software panel, ensure you have configured the Panel ID number and the Controller 1 IP address. For a software panel, set Connect .

When the panel is online, you can control GV Orbit Client from the panel.

318

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Panel Configuration Example Using Categories with Custom Navigation

You can view the health of the panel in the System Status task. See

The green bar indicates the health of the panel is good.

6 Click the Panel ID at the top of Panel Communication Status column to view data on the panel. This appears at the bottom of the interface.

Panel Configuration Example Using Categories with Custom Navigation

This panel configuration example shows how to:

• Set panel navigation when using categories.

• Generally configure a panel.

For this example, the following panel page structure is used. The goal of this example is to teach you how to configure the panel so that the panel user has a work flow with the least number of panel navigation button presses (that is, the need to use exit , return , or home button presses has been minimized).



Home





Category

(test signal selection)





Dest Items



Take

Source Items (test signals)

Panel Page Structure and Panel User Navigation Steps for this Example

319

Configuration Tasks

Panel Configuration Example Using Categories with Custom Navigation

GV Orbit Client Version 2.0.0

User Guide

The following steps outline panel navigation button presses used for this example. See the circled numbers in the above diagram.

Step

Panel User Button

Press

Category

Dest Items

–

Description

On the panel’s Home page is:

• Is a range of sources and destinations, plus a Take button for normal routing activities.

• A Category button (test signal selection) that allows the panel user to route a test signal to a destination using categories.

On the panel’s Category page (test signal selection) are Dest

Items and Source Signals buttons (test signals).

The panel user presses Dest Items .

Select a destination A selection of five destination category items are shown in the

Dest Items page. The panel user presses a button to select a destination to which a test signal will be sent.

The panel user is returned to the panel’s Category page.

Source Items On the panel’s Category page (test signal selection) are Dest

Items and Source Signals buttons (test signals).

The panel user presses Source Items .

Select a source and then Take

A selection of five source category items (test signals) are shown in the Source Items page. The panel user presses a button to select a source (test signal)and then presses TAKE .

Once the Take is made in the Source Items page, the panel’s configuration navigates the panel user to the Home page where the panel user is ready to continue with other operations.

About panel user navigation in this example

Note that no up , home , or return navigation buttons are used in this example. In practice, a panel’s configuration should include navigation buttons as an answer to when a panel user changes their mind and no longer wants to commit to an action. In this example, a panel user must complete the action once started; there is no escape function to exit the above procedure part way through. This is solved by adding a Load Page action to a panel button and configuring the action to take the panel user to the Home Page for example. See

Adding Devices to a Topology , on page 224 and

To configure this example

Proceed as follows.

1 Create the following topology that is used for this example.

320

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Panel Configuration Example Using Categories with Custom Navigation

Add to the Topology Configurator the following device groups: 5 Test Signal

Generators, 5 cameras, 5 monitors. Then add a router with 10 inputs and 5 outputs to the Topology Configurator. See

To name a device and set the number of devices in the group , on page 225.

2 Click Quick Connect to link the devices together. See

Using Quick Connect to Link all

Devices in a Topology , on page 239.

3 In the Category Configurator, Create the categories you will use with the panel. See

Creating Categories for the Sources and Destinations in Your Topology , on page 289.

For this example, five test signal sources have been added to the Source Category

(shown) and five destinations have been added to the Destination Category (not shown).

4 Create a panel if you have not already done so. See Creating a New Panel , on page 296.

5 Configure the panel’s properties. See

Configuring a Panel’s Properties , on page 300.

321

Configuration Tasks

Panel Configuration Example Using Categories with Custom Navigation

GV Orbit Client Version 2.0.0

User Guide

6 Add the following pages to the panel: Category , Source Items , and Dest Items . See

Adding Panel Pages , on page 302.

These are the pages between which the panel user will navigate according to the configuration parameters you set in the Panel’s configuration, shown in later steps in this procedure.

322

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Panel Configuration Example Using Categories with Custom Navigation

7 On the Home page, add a Load Page from the Built-In Tool to a panel button. See

Category to a panel button. See Adding

8 On the Home page, select the Load Page panel button and set the Page property parameter to Category . With this setting, when the panel user presses this button, they will be shown the Category page.

323

Configuration Tasks

Panel Configuration Example Using Categories with Custom Navigation

GV Orbit Client Version 2.0.0

User Guide

9 On the Category page, add the Destination

Resources to the Panel , on page 306.

10 On the Category page, add the Source Category to a panel button. See

Adding

Resources to the Panel , on page 306.

324

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Panel Configuration Example Using Categories with Custom Navigation

11 On the Category page, select the Destination Category panel button and set the Exit

Mode , Exit Page , and Page property parameters.

The following configuration parameter explanation should be interpreted within the context of this example procedure.

Parameter Description

Category This should show Destination for this step.

Exit Mode

Exit Page

Select how the panel user will be returned once they have made a category item selection or Take.

In this example, set this to Preset . With this option, the panel behavior is to take the panel user to the Category page immediately once they have pressed a destination category in the Dest Items page.

In this example, this is set to [blank]. The Exit Page feature is unused.

Page For the Destination category, set to Dest Items .

With this setting, when the panel user presses this panel button on the

Category page, they will be shown the Dest Items page where the panel user is able to select a destination item.

Setting the Properties for

Panel Resources , on page 310 for more information about the remaining properties.

325

Configuration Tasks

Panel Configuration Example Using Categories with Custom Navigation

GV Orbit Client Version 2.0.0

User Guide

12 On the Category page, select the Source Category panel button and set the Exit Mode ,

Exit Page , and Page property parameters.

The following configuration parameter explanation should be interpreted within the context of this example procedure.

Parameter Description

Category This should show Source for this step.

Exit Mode

Exit Page

Select how the panel user will be returned once they have made a category item selection or Take.

In this example, set this to Take . With this option, the panel user has to select a source category and then press the Take button.

In conjunction with the Exit Mode parameter, this parameter changes the Take return navigation to any other panel page.

In this example, set this to Home ; the panel behavior is to take the panel user to the Home page immediately once they have pressed the category item selection and then the Take button in the Source Items page.

Page For the Source category, set to Source Items .

With this setting, when the panel user presses this panel button on the

Category page, they will be shown the Source Items page where the panel user is then able to select a source item and then clicks Take.

326

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Panel Configuration Example Using Categories with Custom Navigation

13 On the Dest Items page, add five List Item from Built-In to five panel buttons. This corresponds to one List Item for each of the five sources.

Note: You can use copy and paste a block of List Item on the panel to quickly create a large number of sources or destinations.

14 On the Source Items page, add five List Item from Built-In to five panel buttons. This corresponds to one List Item

for each of the five sources. See Adding Resources to the

Panel , on page 306.

327

Configuration Tasks

Panel Configuration Example Using Categories with Custom Navigation

15 On the Source Items page, add a Take button.

GV Orbit Client Version 2.0.0

User Guide

16 Add a panel device to the topology and configure the panel and its control port properties. See

Adding the New Panel to the Topology , on page 316.

Note: The panel device bubble on the Topology Configurator does not need to be linked to any other bubble.

17 In the Topology Configurator, activate the topology. See

Activating a Topology , on page 253.

18 Test the panel’s behavior. Change the Exit Page and Exit Mode property parameters for the Source and Destination buttons on the Category page to see how the navigation behavior changes.

19 Add load page buttons that will allow the panel user to return to the Home page, to each of the following pages: Category , Source Items , and Dest Items

. See also Adding

Resources to the Panel

, on page 306 and Setting the Properties for Panel Resources , on page 310 for more information.

This step is necessary because when the changing the Exit Page and Exit Mode property parameters for the Source and Destination buttons on the Category page, the panel user might wind up in a page without a way to exit out of it. Once testing is complete, and navigation is perfected, these buttons can be removed.

328

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

GPIO Configurator Tasks

Tally devices you connect to the panel’s inputs can trigger events in the router control system such as a salvo or it can route a source to a destination.

In reaction to pressing a panel button, to a GPI input, or to a XPT status, the router control system can trigger events through the panel’s relay outputs to switch your tally devices.

SUPPORTED PANELS: the following panels that support GPIO; NV9605, NV9606, NV9607,

NV9609, NV9646, NV9649 (configured as a NV9609 panel model), NV9640, and NV9642.

Soft panels are available with GPIO controls that allow you to test and debug your GPIO configuration before putting a panel into production.

PREREQUISITES: The following must have been configured:

• a Topology (

Topology Configurator Tasks , on page 219) including:

• Panel Configuration: see Panel Configurator Tasks , on page 294

• Sources and destinations: see

Methods to Link Devices in a Topology , on page 239.

• a router: see

Configuring Router Devices , on page 426

Accessing the GPIO Configurator

To access the GPIO Configurator Task

1 Open GV Orbit Control Client Stage. See

2 Select an area. See

3 Select a topology. See

Creating a New Panel , on page 296,

4 Create and configure a Panel. See

Configuring a

Panel’s Properties , on page 300,

Adding Actions to a Panel

, on page 303, and Adding

Resources to the Panel , on page 306.

5 If a salvo is to be triggered by a GPI, create one or more salvos. See

Creating Salvos , on page 470.

6 If aliases are to be used, create them. See

Adding Aliases , on page 463.

7 Add a panel to the topology. See

Adding the New Panel to the Topology , on page 316.

329

Configuration Tasks

Accessing the GPIO Configurator

8 Select Configuration > GPIO Configurator .

GV Orbit Client Version 2.0.0

User Guide

330

The GPIO Configurator task appears:

GPIO Rules

Errors log and Script Help

GPI Rules and GPO Rule Editor

The GPIO Configurator has the following main sections shown above:

• GPIO Rules

• GPI Rules and GPO Rule Editor

• Errors log and Script Help

GPIO Rules Menu

The GPIO rules menu has the following menu options.

Icon

New

Duplicate

Description

Create a new rule in the rules list. See

Adding a GPIO Rule , on page 331.

Make a copy of the currently-selected rule. See

Duplicating a Rule , on page 337.

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Adding a GPIO Rule

Icon

Delete

Alias

Description

Remove the currently-selected rule. See

Deleting a Rule , on page 338.

Select the Alias to use for all rules. See

Choosing an Alias for all Rules , on page 338.

GPI / GPO Rule Editor Menu

The GPIO rule editor has the following menu options.

Icon

Delete

Select GPI

Select GPO

Validate

Description

Remove the configuration for this rule.

Select the GPI input to be configured. See

Configuring a GPI to Trigger an Event , on page 332.

Select the GPO output to be configured. See Configuring a Script to

Trigger a GPO , on page 334.

Verifies if the rule is valid

Adding a GPIO Rule

Create one or more rules to control your tallies. Rules can be enabled and disabled as needed.

Note:

It is possible to create two or more rules can that act upon the same GPO, thereby creating a conflict. No error or warning will be flagged in this case. When two or more rules conflict, you must deactivate rule(s) such that only one rule controls a

GPO at a time. See

Activating / Deactivating a Rule , on page 337.

To add a rule

1 Click New .

2 Enter meaningful text in the Name and Description fields to identify the rule.

3 For the new row, click the cell for the Panel ID column.

331

Configuration Tasks

Configuring a GPI to Trigger an Event

GV Orbit Client Version 2.0.0

User Guide

The Panel Selector window appears showing the panels that have been previously

configured. See Panel Configurator Tasks , on page 294.

4 Select the panel which has GPIO connections made to it that you want to configure.

5 Click OK .

The Panel Id is shown for the GPIO rule and the Status is green.

Configuring a GPI to Trigger an Event

Tally inputs (called GPIs) can be configured to trigger an event when the input transitions from OFF to ON and to trigger another event on a transition from ON to OFF. Events include:

• Execute a salvo. The salvo must have been previously created. See

Creating Salvos , on page 470.

• Route a source to a destination. The source and destination must have been previously created. See

Logical Device Table Tasks , on page 259.

Input Transition from

ON to OFF

Input Transition from

OFF to ON

GPI Contact

Closed (ON)

GPI Contact

Open (OFF)

GPI Contact

Closed (ON)

Time

332

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Configuring a GPI to Trigger an Event

Separate actions are triggered depending on whether the transition is from ON to OFF or the transition is OFF to ON as shown above.

To configure a GPI state transition to route a source to a destination or trigger a salvo

1 Add a Rule if necessary. See

To add a rule , on page 331. Select the rule you want to

configure. Ensure the rule is de-activated.

2 Click the GPI tab.

3 Select the panel’s GPI input to be used as a trigger.

4 Select the action to execute when this input transitions from ON to OFF:

• Execute a salvo: select the salvo to be executed from the list.

• Route a source to a destination: select a source and a destination from the lists.

5 Select the action to execute when this input transitions from OFF to ON:

• Execute a salvo: select the salvo to be executed from the list.

• Route a source to a destination: select a source and a destination from the lists.

6 Repeat for the remaining GPI inputs to be used as a trigger for an action.

7 Click Validate to check the syntax and semantics with respect to the current configuration and it then saves the script.

8 Activate the rule. See

To activate a rule , on page 337.

333

Configuration Tasks

Configuring a Script to Trigger a GPO

GV Orbit Client Version 2.0.0

User Guide

Configuring a Script to Trigger a GPO

Relay outputs can be configured to activate on a number of Boolean true or false conditions that form a script:

• One or more routes occurring on specific levels.

• Conditions involving output ports (destination, level).

• A transition on one or more of the panel’s tally inputs.

Term

Operator

Term Term

Operator

In this dialog, you create a Boolean script involving sources, destinations, port status, and

GPI (input) status. When the conditions of the entire Boolean script evaluates as true, the relay output closes. When the conditions are not met, the relay output opens. Names of sources, destinations, levels and so on are case sensitive.

Boolean expressions comprise terms and operators. The operators include those shown under the Script Help tab. Expressions can be parenthesized to control the order of evaluation. Operator precedence is normally NOT > AND > OR. All parenthesized expressions are evaluated first; expressions in nested parentheses are evaluated before those in outer parentheses.

Function

AND,OR, NOT,()

Description

Logical AND, OR, NOT, and precedence. Note that && (AND), || (OR), !

(NOT) are also supported.

Tally(SRC,DST) Returns true when the specified source is tallied on the specified destination for the SDI level.

Tally(SRC,DST,Level) Returns true when the specified source is tallied on the specified destination for the specified level.

Tally(SRC,DST,Levels...) Returns true when the specified source is tallied on the specified destination for the specified level shuffles. Level shuffle arguments are in pairs.

Locked(DST) Returns true when the specified destination is locked.

LockReleased(DST)

Protected(DST)

Returns true when the specified destination is unlocked.

Returns true when the specified destination is protected.

ProtectReleased(DST) Returns true when the specified destination is unprotected.

GPI(GPI#, STATUS) Returns true when the GPI status is equal to the specified STATUS.

STATUS value could be ON or OFF.

334

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Configuring a Script to Trigger a GPO

For example, the following script is true when Cam1 is tallied on Mon1 for the SDSDI level and GPI1 input is on or GPI8 input is on:

Tally(Cam1, Mon1, SDSDI) AND (GPI(1, ON) OR GPI(8, ON))

Click a function to see an example script of how to use the function under Example .

To configure a script to control GPOs

1 Add a Rule if necessary. See

To add a rule , on page 331. Select the rule you want to

configure. Ensure the rule is de-activated.

2 Click the GPO tab.

3 Select the panel’s GPO output to be used as a trigger.

335

Configuration Tasks

Deleting a GPI or GPO Action Configuration

GV Orbit Client Version 2.0.0

4 Create a script that when true will close the output relay’s contact.

User Guide

5 Click Validate to check the script’s syntax.

Any errors are shown in the Errors tab. Correct the script as necessary. Click the Script

Help tab for how to use script arguments.

6 Activate the rule. See

To activate a rule , on page 337.

Deleting a GPI or GPO Action Configuration

To delete a GPI or GPO action configuration

1 Click the GPI or GPO tab.

336

2 Select an Input or Output to be deleted.

3 Click Delete .

GV Orbit Client Version 2.0.0

User Guide

Activating / Deactivating a Rule

To activate a rule

1 Set Active in the rule’s row.

Configuration Tasks

Activating / Deactivating a Rule

The rule’s configuration becomes read only and cannot be modified. The rule’s status becomes a green circle to indicate that the rule is valid.

To deactivate a rule

1 Deselect Active in the rule’s row.

Duplicating a Rule

To duplicate a rule

1 Select the rule to be duplicated.

2 Click Duplicate .

3 Set the name and description of the new rule.

4 Click OK .

337

Configuration Tasks

Deleting a Rule

To delete a rule

1 Select the GPIO rule to be deleted.

GV Orbit Client Version 2.0.0

User Guide

2 Click Delete .

Choosing an Alias for all Rules

The source and destination aliases must have been previously created. See

Adding Aliases , on page 463. The alias selection applies to all current rules.

To set an alias

1 Click Alias .

2 Set the Source and Destination aliases to use for all rules.

3 Click OK .

338

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Stream Configurator Tasks

The Stream Configurator task displays all streams in the current topology and allows you to configure on a large scale the following stream parameters:

• Set the stream’s Unicast and multicast IP addresses

• Change the stream’s SDP template

• Change the stream’s logical levels

• Expose or hide streams

This can be done in bulk by selecting multiple rows and using the paste functionality, to set the IP addresses of hundreds of streams in one action. Filters allow you to narrow down the list in order to only show the devices you want to change their IP addresses / port numbers.

The list has multiple sort, so you can put the devices in the right order (from top to bottom), thereby allowing you to paste an incremental range of IP addresses. Content can be pasted from a vertical column of Microsoft Excel worksheet cells, or from a text editor where there is one IP address per line.

The Stream Configurator is also useful for troubleshooting: for example, you discover an unexpected IP address is being routed and you want to find the device associated with that

IP address. Use the IP address in the filtering at the top of the Unicast IP or Multicast IP columns in the Stream Configurator to find the device.

PREREQUISITES: The following must have been configured:

• a Topology (

Topology Configurator Tasks , on page 219).

• a number of devices on the topology such as a GV Node which has a variety of streams

(see

Adding Devices to a Topology , on page 224).

Setting the IP address in GV Orbit Client for third-party IP devices are an ideal application for the stream configurator; see

Using Quick Config , on page 236 and the example in

Setting Port Redundancy for Many Devices at Once , on page 237 to create such devices.

Accessing the Stream Configurator

To access the Stream Configurator Task

1 Open GV Orbit Control Client Stage. See

2 Select an area. See

3 Select a topology. See

4 The topology must be currently:

• Activated (see

• Unlocked (see

Filters the list by signal type and direction. See Stream Configurator

339

Configuration Tasks

Accessing the Stream Configurator

5 Select Configuration > Stream Configurator .

GV Orbit Client Version 2.0.0

User Guide

The Stream Configurator task appears:

340

Stream Configurator Menu

The Stream Configurator menu has the following menu options.

Icon

Refresh

Select All

Clear All

Filters

Description

Reloads the Stream Configurator’s contents. The Stream Configurator’s content is static. If you make a configuration change in another task, it will not automatically be reflected in the Stream Configurator.

Selects all rows in the Stream Configurator.

Deselects all rows in the Stream Configurator.

Filters Tool , on page 342.

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Accessing the Stream Configurator

Icon Description

Paste IP addresses Pastes the clipboard contents to the selected Stream Configurator’s column from a Microsoft Excel spreadsheet column or a text editor, where there is one IP address per line.

See

Pasting Unicast and Multicast IP Addresses from a Microsoft Excel

Spreadsheet / Text Editor , on page 343.

Set stream SDP file Set the SDP pattern for streams. See

Setting SDP Templates for one or more Streams , on page 344.

Set stream level Sets the logical level of one or more selected streams. This shows the

Logical Level Selector.

Expose or hide streams

Filter

Select a logical level and click OK to change the level of all selected streams to the new logical level.

For more information about logical levels, see Logical Level Editor

Tasks , on page 210.

Sets to expose or hide streams of one or more selected streams. Only certain devices support this property. When Expose Stream is set, it displays the streams for this device in the Logical Device Table. See

Logical Device Table Tasks , on page 259.

Row filters can be applied to each column by typing text in the filter boxes to filter the list according to a column’s content. The combination of all applied filters means that a row must match all filter

values in order to be displayed. See Filtering the Stream Configurator

List , on page 342. See also

Filtering Lists, Table Columns, Sources, and

Destinations , on page 285.

341

Configuration Tasks

Stream Configurator Filters Tool

GV Orbit Client Version 2.0.0

User Guide

Stream Configurator Filters Tool

A filter button is available in the toolbar for you to show or hide signal types (SDI, IP, MADI) or signal direction (Input/Rx and Output/Tx streams).

Click to open filter tool

Set the required filters

Icon

Show SDI

Show IP

Show MADI

Show inputs / rx

Show outputs / tx

Description

Show results where the connection type is SDI.

Show results where the connection type is IP.

Show results where the connection type is MADI.

Show results where the connection direction is an input.

Show results where the connection direction is an output.

Pasting IP addresses from a Microsoft Excel worksheet into the Stream

Configurator

In order to paste a vertical column of worksheet cells of an ordered list of IP addresses you have created in Microsoft Excel, you must first prepare the Stream Configurator by:

1 Filtering the table to only show the devices, inputs / outputs, signal type, logical levels, for which you are going to update their IP addresses. Filters allow you to narrow down the Stream Configurator list in order to only show the devices of interest.

2 Sorting the filtered list such that the devices are in the same order as the vertical column of worksheet cells you have created in Microsoft Excel.

3 Paste a vertical column of worksheet cells you have created in Microsoft Excel into either the Unicast IP or Multicast IP columns of the Stream Configurator.

Filtering the Stream Configurator List

First, filter the Stream Configurator’s contents to create a list of only the devices that are of interest; those devices you want to update their IP addresses.

342

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Pasting IP addresses from a Microsoft Excel worksheet into the Stream Configurator

Filtering can be done by combining the following methods:

• Use the Filters tool to show or hide signal types (SDI, IP, MADI) or signal direction

(Input/Rx and Output/Tx streams). See Stream Configurator Filters Tool , on page 342.

• Enter text into the row filters found at the top of each column by typing text in the filter boxes to filter the list according to a column’s content. The combination of all applied filters means that a row must match all filter values in order to be displayed. See

Filtering Lists, Table Columns, Sources, and Destinations , on page 285.

Sorting the Stream Configurator List

Once the Stream Configurator’s contents have been filtered, then sort the filtered list.

Each column can be sorted by clicking the header text. Multiple sort can be applied by

<Shift> + clicking the headers. Bullets and numbers will appear next to the sort arrow indicating the column’s sort priority. An up arrow is ascending sort, and a down arrow is a descending sort.

First sort priority (one bullet)

Second sort priority (two bullets)

Third sort priority

(three bullets)

Fourth sort priority

Fifth sort priority

Eighth sort priority

Pasting Unicast and Multicast IP Addresses from a Microsoft Excel

Spreadsheet / Text Editor

Unicast and Multicast IP address values can be bulk pasted into the Stream Configurator from a Microsoft Excel spreadsheet column by using copy/paste.

• Multicast IPs are formed with the following semi-colon separated concatenated format:

[IPv4 Address]:[Port Number] . For example, the text to be pasted for a multicast address should look like 231.102.30.13:5004

If you paste an IPv4 address without a port number into the Multicast IP column, only the IP address will be updated and the current port number will be left intact.

• Unicast IPs are a basic IP address without a port number.

To paste Unicast or Multicast IP Addresses

1 Select a column with IP addresses from a Microsoft Excel spreadsheet and copy them.

2 Select the rows in the Stream Configurator that contain the streams to be changed. See

Selecting Stream Configurator Rows , on page 346.

343

Configuration Tasks

Editing Unicast and Multicast IP Addresses

GV Orbit Client Version 2.0.0

User Guide

3 Click the paste button in the Stream Configurator toolbar. Choose whether to apply the paste to Unicast or Multicast IP addresses. The paste is made starting from top-tobottom of the selected rows.

Note: All pasted IP addresses are validated and if any one address is invalid, the entire paste is canceled and nothing happens.

Editing Unicast and Multicast IP Addresses

Cells in the Unicast IP column can be double-clicked in oder to edit their contents. These cells will only accept valid IPv4 addresses.

Cells in the Multicast IP column can also be double-clicked in oder to edit their contents.

These cells only accept valid IPv4 addresses and a port number separated by a colon (:). For example 231.102.30.13:1080 .

Setting SDP Templates for one or more Streams

Not all devices are NMOS compliant, however with the use of SDP parameters, GV Orbit

Client may be able to make a take of a stream from a non-NMOS Device to an NMOS Device.

GV Orbit Client can intuit some SDP parameters while other parameters will have to be

provided by you. For more information about how to form an SDP template, see Using SDP

Parameters to Take a Stream from a non-NMOS Device to an NMOS Device , on page 401.

You can set the SDP templates for one or more streams as follows.

1 If necessary, filter and sort the Stream Configurator list to only show the devices, inputs

/ outputs, signal type, logical levels, for which you are going to update their SDP templates. Filters allow you to narrow down the Stream Configurator list in order to only show the devices of interest. See

Filtering the Stream Configurator List , on page 342 and

Sorting the Stream Configurator List , on page 343.

2 Select the rows in the Stream Configurator that contain the streams to be changed. See

Selecting Stream Configurator Rows , on page 346.

3 Click the cogwheel icon. The SDP template text for the last selected stream in the table is shown in a pop-up.

If the last selected stream type is SDI or a receiver, the SDP template text area will be blank.

4 Type in or paste the SDP template text into the pop-up text area and click OK . See

Using SDP Parameters to Take a Stream from a non-NMOS Device to an NMOS Device , on page 401.

Note: The SDP text you enter is not validated by GV Orbit Client. The SDP is directly applied to IP streams only. All other stream types are ignored.

344

GV Orbit Client Version 2.0.0

User Guide

Configuration Tasks

Setting SDP Templates for one or more Streams

All selected streams will be updated with the new SDP template.

GV Orbit Client SDP Variables that can be used with Third-Party Devices

The following table lists whether the GV Orbit Client SDP variables are supported when used with third-party devices. Any unsupported SDP variable must be replaced by a hard coded value that represents the third-party device’s static property value.

GV Orbit Client SDP

Variable

${audioBits}

${channelCount}

${clockSetting}

${sequence}

${packetTime}

${portIpAddress}

${streamIpAddress}

${streamPortNumber}

${redundantIpAddress}

${redundantPortNumber}

Supported with thirdparty-devices



Description

The audio stream’s bit depth.

The number of (audio) channels.

The PTP master clock setting.

This SDP file’s ID.

The length of time in milliseconds represented by the (audio) media in a packet.

The sending port’s IP address.

The source for this variable comes from the Port’s IP Address parameter for this stream.

The transmit (sending) stream’s multicast IP address.

The source for this variable comes from the stream’s IP Address parameter.

The transmit (sending) stream’s IP port number.

The source for this variable comes from the stream’s IP Port parameter.

The transmit (sending) stream’s redundant multicast IP address.

The source for this variable comes from the stream’s IP Address parameter used for the redundancy port. See the

Redundancy Port parameter to identify the current redundancy port.

The transmit (sending) stream’s redundant IP port number.

The source for this variable comes from the stream’s IP Port parameter used for the redundancy port. See the

Redundancy Port parameter to identify the current redundancy port.

345

Configuration Tasks

Selecting Stream Configurator Rows

GV Orbit Client Version 2.0.0

User Guide

GV Orbit Client SDP

Variable

${redundantPortIpAddre ss}

Supported with thirdparty-devices



${rtpPayloadType}

${samplingRate}

Description

The transmit (sending) stream’s redundant IP port number.

The source for this variable comes from the stream’s IP Address parameter used for the redundancy port. See the

Redundancy Port parameter to identify the current redundancy port.

The RTP payload type as defined by the SDP specification.

The audio stream’s sampling rate.

Selecting Stream Configurator Rows

Stream Configurator rows can be selected as follows:

• All current rows can be selected by clicking Select All from the Stream Configurator’s menu. See

Stream Configurator Menu , on page 340.

• Select one or more streams in the Stream Browser using <Ctrl> + click.

• Select a range of streams in the Stream Browser by selecting the first stream and then

<Shift> + click the last stream in the range.

346

The configuration of certain features for a specific device require an in depth explanation which is provided here.

Special Devices

These special device are described under the following headings:

•

Configuring a GV Node Device , on page 349

•

Configuring an IPG 3901 / IPG 4901 Device , on page 360

•

Configuring an IPVU Device , on page 366

•

Configuring an IQMix or IQUCP25 Device , on page 369

•

Configuring UHD 4K Two-Sample Interleave Division IP Streams for use with an IQMix,

IQUCP, or IPVU Device , on page 371

•

Configuring UHD 4K Quad-Link SDI Streams for use with an IQMix, IQUCP, or IPVU

Device , on page 376

•

Configuring an MV-820-IP Multiviewer Device , on page 380

•

Configuring a Kahuna IP Production Switcher Device , on page 384

•

Configuring a K-Frame Production Switcher , on page 387

•

Adding NMOS Devices to a Topology , on page 394

•

Using SDP Parameters to Take a Stream from a non-NMOS Device to an NMOS Device , on page 401

•

Configuring Cisco DCNM Network Switch Devices , on page 405

•

Direct Flow Orchestration: How To Create a Static Flow with a Cisco Network Switch , on page 411

•

Configuring a GV Fabric Network Switch Device , on page 412

•

Configuring Network Switch Redundancy to Support SMPTE ST 2022 7 , on page 415

•

Configuring an NVISION Hybrid Series Router , on page 420

•

Configuring Router Devices , on page 426

•

Configuring a Device that Supports Audio Breakaway/Shuffling such as Audio Live , on page 437

•

Configuring an IQAMD40 Device , on page 444

347

Special Device Configuration Tasks

Description of Common Device Properties

GV Orbit Client Version 2.0.0

User Guide

Description of Common Device Properties

The description for certain device properties are universal.

Parameter

# Input Connectors

Description

The number of physical input port connections made to the device.

This shows the current status for information purposes.

# Output Connectors The number of physical output port connections made to the device.

This shows the current status for information purposes.

# Streams Per Input The typical number of streams available on each physical input connection. This shows the current status for information purposes.

# Streams Per Output The typical number of streams available on each physical output connection. This shows the current status for information purposes.

# Streams The actual number of streams available on the selected physical input

/ output connection. This shows the current status for information purposes.

Automatic

Destination

Automatic

Destinations on

Inputs

Automatic

Destinations on

Outputs

Automatic Source

Automatic Sources on

Outputs

Automatic Sources on

Inputs

Set to automatically create a destination by the system for the

specified streams. See also About Automatic Sources or Destinations , on page 264.

Set to automatically create a source by the system for the specified streams. See also

page 264.

About Automatic Sources or Destinations , on

Description

Enabled

Expose Streams

An optional description for the related input, output, or device.

This shows the current status for information purposes.

When set, it displays the streams for this device in the Logical Device

Table. See Logical Device Table Tasks , on page 259.

Quick Config can be used to set or clear this parameter; see Using

Quick Config , on page 236.

Logical Level

Name

Short Name

The logical level for this input or output. See Logical Level Editor Tasks , on page 210.

The name or identifier for this device instance.

The name or identifier for this input or output port.

The nickname by which the input, output, or device is referred to everywhere in the system.

SSM Address Enabled Shows if the source specific multicast address is enabled.

SDP See

Using SDP Parameters to Take a Stream from a non-NMOS Device to an NMOS Device , on page 401.

348

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a GV Node Device

To configure a GV node Device

1 Add the GV Node device to the Topology: from the Device Library , Virtual Device , find the GV Node

device bubble. See To add a Virtual Device to a topology , on page 224.

2 Select the GV Node bubble and configure the Device Properties in the Property Editor .

See

Defining Device Properties , on page 247 for more information.

Parameter

Frame IP Address

Description

The network IP address for the associated GV Node frame.

Network Host Name The hostname is the unique name by which the associated GV Node

CPU-ETH3 is known on the network.

Advanced >

Description

An optional description for this GV Node’s control port.

349

Special Device Configuration Tasks

Configuring a GV Node Device

GV Orbit Client Version 2.0.0

User Guide

Parameter

Advanced > 2022-7

Mode

Advanced > 6 HD

Mode

Advanced > Card

Enabled Option

Description

When the IFM-2T-OPT-40G-6 option is active, you can choose to enable SMPTE ST 2022-7 Low Latency redundant, high-bit-rate streams on the aggregation ports, using the GV Node manager.

If this option has been enabled in the GV Node Manager, then enable it here.

This no redundancy, low bitrate option reduces each channel from

3Gbps to 1.5Gbps, allowing all 144 channels to be sent on aggregation ports 1-6, and leaving aggregation ports 7-12 unused.

If this option has been enabled in the GV Node Manager, then enable it here.

This option controls audio embedding / de-embedding.

For example, the XIO-4901 3G/HD/SD SDI input/output card supports audio embedding/de-embedding, as a software option (MDX):

MDX: The GV Node Manager allows you to enable or disable audio embedding/de-embedding on a card’s SDI inputs and outputs.

None: If your system is monitoring MADI signals (supported at the

XIO-4901 card’s inputs/outputs 8 and 9), then disabling the MDX option lets you select MADI at the inputs and outputs matching your physical configuration. See

Configuring MADI support with a GV Node

Device , on page 355 for more information.

Set the signal type.

Advanced > Card

Mode

Advanced > Gateway

Connection State 1

Advanced > Gateway

Connection State 2

Advanced > Gateway

NP16 Connection

State

Advanced > IFM-2T

Version

Gateway Connection State 1 shows the connection status of the GV

Node frame with the primary server of a server group.

Gateway Connection State 2 shows the connection status of the GV

Node frame with the secondary server of a server group. See

The topology is inactive (see Activating a Topology , on page 253) or the GV Node frame does not have network connectivity

unknown:

to the GV Orbit Client server(s).

offline: The GV Node frame does not have network connectivity to the

GV Orbit Client server(s).

online: The GV Node frame is connected to the GV Orbit Client server(s).

This shows the NP16 connection status of the GV Node frame with a server of a server group. unknown:

The topology is inactive (see Activating a Topology , on page 253) or the GV Node frame does not have network connectivity

to the GV Orbit Client server(s).

offline: The GV Node frame does not have network connectivity to the

GV Orbit Client server(s).

online: The GV Node frame is connected to the GV Orbit Client server(s).

The IFM-2T Fabric Module User Interface version number.

350

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a GV Node Device

Parameter

Advanced > Internal

Wiring Done

Advanced > Join

Timeout (ms)

Advanced > Router

Connection State 1

Advanced > Router

Connection State 2

Description

Shows if the internal modeling of the GV Node is complete.

When GV Orbit Client is used with a GV Node version 1.3.0, to allow a clean switch that will not be reported as a fail, we recommend this parameter to be set to 2 ms.

Router Connection State 1 shows the connection status of the router with the primary server of a server group.

Router Connection State 2 shows the connection status of the router

with the secondary server of a server group. See Configuring a

Controller Group , on page 199.

unknown:

The topology is inactive (see Activating a Topology , on page 253) or the router does not have network connectivity to the GV

Orbit Client server(s).

offline: The router does not have network connectivity to the GV Orbit

Client server(s).

online: The router is connected to the GV Orbit Client server(s).

3 Configure the card in each slot and configure the inputs and outputs for each card by making a selection at the top to make the related parameters become available below.

Select the

Card by its slot number in Slots

Card’s SDI output number in SDI Outputs.

Then select the Card’s SDI Output Stream

Configuration number in Streams

Card’s Stream SDP Configuration number in Stream SDP Config

To configure the properties exposed below under

Slot #

Out #

GV Node-[instance] Out #

IP Stream Prototype #

351

Special Device Configuration Tasks

Configuring a GV Node Device

GV Orbit Client Version 2.0.0

User Guide

Select the

Card’s Input Lanes number in Input Lanes .

Then select the card’s stream number in

Streams .

Card’s SDI Input number in SDI Inputs .

Then select the card’s stream number in

Streams .

Card’s Output Lanes number in Output

Lanes .

Then select the card’s stream number in

Streams .

To configure the properties exposed below under

Eth In #.#

GV Node-[instance] Eth In#.# Stream #

In#

GV Node-[instance] In#

Eth Out #.#

GV Node-[instance] Out#.# Stream #

Configure the GV Node Card Properties in the Property Editor . See also

Configuring MADI support with a GV Node Device , on page 355 for more information.

Parameter

Slot #

Description

Card Enabled Option This option controls audio embedding / de-embedding.

For example, the XIO-4901 3G/HD/SD SDI input/output card supports audio embedding/de-embedding, as a software option (MDX):

MDX: The GV Node Manager allows you to enable or disable audio embedding/de-embedding on a card’s SDI inputs and outputs.

None: If your system is monitoring MADI signals (supported at the card’s inputs/outputs 8 and 9), then disabling the MDX option lets you select MADI at the inputs and outputs matching your physical configuration. See

Out #

Name

# Sreams

Port Identifier

Number

Direction

Connector Type

The name or identifier for this SDI output.

The number of streams for this SDI output.

An input lane is specified as QSPFport.lane which in turn corresponds to a physical port on the router. The number property specifies which physical port it is. The port identifier is how you name it so that you can refer to it.

Set the port number on the router.

This shows the current status for information purposes.

Capacity (bps)

IP Address

The stream’s data rate.

The stream’s network IP address.

352

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a GV Node Device

Parameter

Mods-Out to IFM

Description

This option sets the expected output signal type:

SDI: The output signal is a standard SDI video signal with embedded audio.

MADI: The output signal is a MADI signal (supports 64 audio

channels). See Configuring MADI support with a GV Node Device , on page 355 for more information.

Redundancy Port Associate this port with another port to create a redundant network traffic flow path for failover protection. The associated port will not be available to carry other traffic.

GV Node-[instance] Out #

Name

Automatic Source

The name or identifier for this SDI output.

Set to automatically create a source by the system using the specified stream.

Bandwidth (bps) The stream’s data rate.

IGMPv3 SSM Address Source Specific Multicast address as per IGMPv3 (Internet Group

Management Protocol) protocol.

IP Stream Prototype #

Name

Flow Type

SDP

The name or identifier for this SDI output.

Set the content type for this stream: Audio , Data , or Video .

The Session Description Protocol is a format for describing streaming media communications parameters.

Eth In #.#

Name

# Sreams

Port Identifier

The name or identifier for this IP input.

The number of streams for this IP input.

Number

Direction

Connector Type

Capacity (bps)

Set the port number on the router.

This shows the current status for information purposes.

The stream’s data rate.

GV Node-[instance] Eth In#.# Stream #

Name The name or identifier for this IP input.

Flow Type

Automatic Source

SDP

Set the content type for this stream: stream.

Audio , Data , or Video .

Set to automatically create a source by the system using the specified

The Session Description Protocol is a format for describing streaming media communications parameters.

353

Special Device Configuration Tasks

Configuring a GV Node Device

GV Orbit Client Version 2.0.0

User Guide

Parameter Description

IGMPv3 SSM Address Source Specific Multicast address as per IGMPv3 (Internet Group

Management Protocol) protocol.

IP Address

IP Port

In#

Name

The stream’s network IP address.

Port number for the stream.

The name or identifier for this IP input.

# Sreams

Port Identifier

Number

Direction

Connector Type

Capacity (bps)

The number of streams for this IP input.

Set the port number on the router.

This shows the current status for information purposes.

The stream’s data rate.

Bandwidth Usage

(bps)

IP Address

Mods-In to IFM

Redundancy Port

The stream’s network IP address.

This option sets the expected input signal type:

SDI: The input signal is a standard SDI video signal with embedded audio.

MADI: The input signal is a MADI signal (supports 64 audio channels).

See

Configuring MADI support with a GV Node Device , on page 355

for more information.

Associate this port with another port to create a redundant network traffic flow path for failover protection. The associated port will not be available to carry other traffic.

GV Node-[instance] In#

Name The name or identifier for this IP input.

Automatic Source Set to automatically create a source by the system using the specified stream.

IGMPv3 SSM Address Source Specific Multicast address as per IGMPv3 (Internet Group

Management Protocol) protocol.

Eth Out #.#

Name

# Sreams

Port Identifier

The name or identifier for this IP input.

The number of streams for this IP input.

354

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a GV Node Device

Parameter

Number

Direction

Connector Type

Description

Set the port number on the router.

This shows the current status for information purposes.

Capacity (bps)

Bandwidth Usage

(bps)

IP Address

Redundancy Port

The stream’s data rate.

The stream’s network IP address.

Associate this port with another port to create a redundant network traffic flow path for failover protection. The associated port will not be available to carry other traffic.

GV Node-[instance] Out#.# Stream #

Name The name or identifier for this IP input.

IP Address

IP Port

The stream’s network IP address.

Port number for the stream.

Flow Type

Automatic Source

Set the content type for this stream: Audio , Data , or Video .

Set to automatically create a source by the system using the specified stream.

SDP The Session Description Protocol is a format for describing streaming media communications parameters.

The stream’s data rate.

Bandwidth (bps)

IGMPv3 SSM Address Source Specific Multicast address as per IGMPv3 (Internet Group

Management Protocol) protocol.

Configuring MADI support with a GV Node Device

To support a MADI input on a GV Node frame, this option must be configured both in GV

Orbit Client and the MADI input must have been previously configured in iControl

Navigator; locate the GV Node Manager associated with your GV Node and double-click its icon. For example, the following figure shows the 9 th input XIO-4901 card in slot 16 is set to

355

Special Device Configuration Tasks

Configuring a GV Node Device

GV Orbit Client Version 2.0.0

User Guide accept a MADI input. Within GV Orbit Client, the same setting must be made wherever a

MADI input has been configured in iControl Navigator for a GV Node frame.

Fig. 7-1: A GV Node in iControl Navigator

The above iControl Navigator configuration is used as an example configuration for the following procedure.

To configure a GV node MADI input in GV Orbit Client

1 Select the required Area. See Selecting an Area , on page 203.

2 Select the required topology. See Selecting a Graph , on page 204.

3 Add and configure a GV Node device. See Configuring a GV Node Device , on page 349.

356

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a GV Node Device

4 In the Property Editor for the GV Node device, make the same setting as in GV Node

Manager for Enabled Options for the card: in the GV Node’s properties, in Slots , select

16 , then set None in Card Enabled Option .

5 Use the following table to identify the SDI input number used by GV Orbit Client from the card’s slot and input number for the next step. Only the eighth and ninth inputs of each slot support MADI input signals. For example, the ninth input of the card in slot 16 is 144 .

Matrix Input from Fabric Number for each GV Node Frame Slot

Card’s Input from GV Node

Fabric

First Input

GV Node Frame Slot Number

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

1 10 19 28 37 46 55 64 73 82 91 100 109 118 127 136

Second Input 2 11 20 29 38 47 56 65 74 83 92 101 110 119 128 137

Third Input

Fourth Input

Fifth Input

Sixth Input

3 12 21 30 39 48 57 66 75 84 93 102 111 120 129 138

4 13 22 31 40 49 58 67 76 85 94 103 112 121 130 139

5 14 23 32 41 50 59 68 77 86 95 104 113 122 131 140

6 15 24 33 42 51 60 69 78 87 96 105 114 123 132 141

Seventh Input 7 16 25 34 43 52 61 70 79 88 97 106 115 124 133 142

Eighth Input 8 17 26 35 44 53 62 71 80 89 98 107 116 125 134 143

Ninth Input 9 18 27 36 45 54 63 72 81 90 99 108 117 126 135 144

357

Special Device Configuration Tasks

Configuring a GV Node Device

GV Orbit Client Version 2.0.0

User Guide

6 In the Property Editor for the GV Node device, make the same setting as in GV Node

Manager for the card’s input: in the GV Node’s properties, in SDI Inputs , select 144 , then set MADI in Mods-In to IFM .

For each MADI input, 64 audio streams are shown in Streams and the logical level is

MADI for each stream. These 64 streams are made available within the Logical Device

Table for use on manually created logical devices. If you choose the Automatic source/destination option for the MADI, then 4 devices of 16 channels of audio are

358

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a GV Node Device created in the Logical Device Table on the appropriate tab. See

Logical Device Table

Tasks , on page 259.

359

Special Device Configuration Tasks

Configuring an IPG 3901 / IPG 4901 Device

GV Orbit Client Version 2.0.0

User Guide

Configuring an IPG

3901 / IPG

4901 Device

The Densité IP Gateway (IPG-3901) plug-and-play module is a 3 RU module for the Densité

3 frame, which provides bidirectional IP/SDI conversion. The Gateway operates with 10

GigE audio/video video-over-IP, supporting UHD/3G/HD/SD-SDI formats.

The GV Node IP Gateway (IPG-4901) plug-and-play module is a 3 RU single slot module for the GV Node frame, which provides bidirectional fiber IP connectivity to provide conversion to and from other equipment that cannot be handled directly by the GV Node aggregation ports (GV Node’s receivers and transmitters). This card allows the user to expand the receivers available on the GV Node, as well as it brings more flexibility to the allowed audio profiles that can be accepted through the IPG-4901

PREREQUISITES: All IPG-3901 and IPG-4901 devices must have been previously configured in iControl Navigator. GV Orbit Client reads this configuration information from iControl through the GV Node / Densité Manager.

To configure an IPG-3901 / IPG-4901 Device

1 Add the IPG-3901 or IPG-4901 device to the Topology: from the Device Library , Virtual

Device , find the IPG-3901 or IPG-4901 device bubble. See

To add a Virtual Device to a topology , on page 224.

360

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring an IPG 3901 / IPG 4901 Device

2 Select Device Group Properties . Configure the GV Node IP Address / Frame IP

Address and Slot Number properties.

Parameter

# Devices

Network Host Name

# Input Connections

# Output Connections

Advanced > Default

Connector Type

Advanced > # Streams Per

Input

Advanced > # Streams Per

Output

Advanced > Receive Stream

IP Pattern

Advanced > Send Stream IP

Pattern

Description

The number of panel instances in this device group.

The hostname is the unique name by which the associated

IPG-3901 or IPG-4901 is known on the network.

The current status for information purposes, once the GV Node

IP Address and Slot Number parameters are configured and the topology is activated. See

Activating a Topology , on page 253.

3 Activate the topology. See Activating a Topology , on page 253.

The card configuration is read from Densite Manager and applied to the device.

361

Special Device Configuration Tasks

Configuring an IPG 3901 / IPG 4901 Device

GV Orbit Client Version 2.0.0

User Guide

4 Select the Device Properties tab and then select IPG next to Devices . See also

Description of Common Device Properties , on page 348.

Parameter

Network Host Name

GV Node IP Address

Frame IP Address

Slot Number

Connection to

Controller 1

Connection to controller 2

Firmware Version

Internal Wiring Done

Operation Mode

Applies to

IPG-3901 IPG-4901

 



Description

The hostname is the unique name by which the associated IPG-3901 or IPG-4901 is known on the network.

IP Address of the CPU-ETH3 for the GV Node frame into which the IPG-4901 card is installed.

IP Address of the CPU-ETH3 for the Densité frame into which the IPG-3901 card is installed.

The slot in which the IPG-3901 or IPG-4901 device is located in the GV Node frame.

Connection to Controller 1 shows the connection status of the IPG device with the primary server of a server group.

Connection to Controller 2 shows the connection status of the IPG device with the secondary server of a server group. See

Activating a Topology , on page 253) or the IPG

unknown: The topology is inactive (see

device does not have network connectivity to the GV Orbit Client server(s).

offline: The IPG device does not have network connectivity to the GV Orbit Client server(s).

online: The IPG device is connected to the GV

Orbit Client server(s).

Shows the firmware version installed on the

IPG-3901 or IPG-4901 card. This shows the current status for information purposes.

Shows if the internal modeling of the IPG-3901 or IPG-4901 is complete.

Shows the operation mode of the ETH2 port of the IPG-3901 or IPG-4901 card for information purposes:

Redundancy: ETH 2 is redundant to ETH 1.

Aggregation: Both ETH 1 and ETH 2 are available simultaneously.

OFF: ETH 2 is disabled.

362

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring an IPG 3901 / IPG 4901 Device

5 Select ETH# next to Ethernet Ports . These are the network configuration parameters

for the IPG-3901 or IPG-4901 card’s Ethernet ports. See also Description of Common

Description of Common Device Properties , on page 348.

Parameter

IP Address

Gateway

Subnet Mask

Description

The network IP address for this Ethernet port.

The network gateway IP address.

The IP network’s subnet mask.

6 Select one of the streams next to Gateways (by default labelled as OUT# or IN# ). See also

Parameter

Direction

Description

This shows the current status for information purposes.

Logical Level on SDI Stream To force a stream to use the IPG-3901 or IPG-4901 device,

create a new level (see Duplicating a Logical Level , on page 213) that you will use to select these specific streams at

the source and destination ports. Set the logical level that will be used for this here.

For example, create a logical level called IPG-SDI from the SDI logical level. Now use this level to send and receive streams to and from this device.

7 Select 1 or 2 next to Streams . See also

Description of Common Device Properties , on page 348.

Parameter

Ethernet Port

Format

IGMPv3 Source

Description

The Ethernet port this gateway is assigned to (ETH 1 or ETH 2).

This shows the current status for information purposes.

The gateway format: SD, HD, or 3G for video streams, or AES67 profile for audio streams. This shows the current status for information purposes.

For a receiver gateway, this is the address of the joined stream’s port when SSM Address is enabled on the device.

IP Address The stream’s network IP address.

Logical Level on ETH stream The Logical level to apply on the ETH side of the gateway. By default for the video stream, this value is SDI and for the audio stream, this value is SDI audio.

Port The stream's network port.

Redundant IGMPv3 Source When the IPG-3901 or IPG-4901 card is in Redundancy mode:

For a receiver gateway, this is the address of the joined stream’s port when SSM Address is enabled on the device.

363

Special Device Configuration Tasks

Connecting an IPG-4901 device

GV Orbit Client Version 2.0.0

User Guide

Parameter

Redundant IP Address

Redundant Port

Description

When the IPG-3901 or IPG-4901 card is in Redundancy mode:

The stream’s network IP address.

When the IPG-3901 or IPG-4901 card is in Redundancy mode:

The stream's network port.

Connecting an IPG-4901 device

The IPG 4901 has 9 SDI input ports, 9 SDI output ports, and 2 bidirectional ETH ports. The

SDI ports must be connected to the SDI ports of the GV Node in which the IPG-4901 is slotted in. This rule is not enforced in GV Orbit Client. GV Orbit Client allows you to use an

IPG-4901 like an IPG-3901, however this is not a valid use case and will not work.

The 9 SDI input ports short labels are called OUT for OUT from fabric, and the 9 SDI output ports short labels are called IN for In to fabric to follow iControl’s behavior.

Device properties

• It is possible to assign a logical level to SDI ports by changing the Logical Level of SDI stream at the Gateway level.

• It is possible to assign a logical level to IP streams by changing the Logical Level on ETH stream on Stream level, under the Gateway.

• It is possible to change the multicast address for SDI to IP gateways (called OUT) by changing the IP Address, Port, Redundant IP Address and Redundant Port properties on Stream level, under Gateway. These changes are propagated to iControl.

• In OFF or Redundancy mode, gateways OUT 6 to 9 and IN 6 to 9 are disabled and not visible in Property Editor . They become visible only if card is in Aggregation mode.

364

GV Orbit Client Version 2.0.0

User Guide

Example Topology Using an IPG-4901

Special Device Configuration Tasks

Example Topology Using an IPG-4901

365

Special Device Configuration Tasks

Configuring an IPVU Device

GV Orbit Client Version 2.0.0

User Guide

Configuring an IPVU Device

The IPVU is a compact dual-channel IP-to-HDMI converter that is perfect for displaying IP sources and a multiviewer’s IP outputs on HD and UHD HDMI displays.

The inputs of an IPVU are called spigots . See also

How to Know if a Spigot is an Input or an

Output , on page 370.

WARNING

The IPVU’s configuration is set through GV Orbit Client and then GV Orbit Client reads the configuration from the IPVU device. All spigots on an IPVU are inputs.

There is no offline configuration of the IPVU device. It must first be discovered on the network by GV Orbit Client.

The IPVU device must have been previously configured with GV Orbit Client before being integrated into GV Orbit Client as most configuration parameters shown in GV Orbit Client are for information purposes only (GV Orbit Client reads it from the IPVU devices). See the

IPVU Installation Guide for more information.

PREREQUISITES: The Domain ID of the IPVU device(s) must be set in the System Controller

Group Properties under Domain Ids . See

How to Know if a Spigot is an Input or an Output , on page 370.

These devices must be on the same subnet that the GV Orbit Client server is connected to.

Related Topics

•

•

Configuring UHD 4K Two-Sample Interleave Division IP Streams for use with an IQMix,

IQUCP, or IPVU Device , on page 371.

•

Configuring UHD 4K Quad-Link SDI Streams for use with an IQMix, IQUCP, or IPVU

Device , on page 376.

Spigot Usage

An IPVU device has 8 input spigots. They are used according to the IPVU’s output resolution.

Input Spigot Number HD Output Description

Spigot1 Stream input for Monitor

Output 1 connection

Spigot2 Not used

Spigot3

Spigot4

Spigot5

Spigot6

Not used

Stream input for

Output 2

Not used

Monitor

connection

UHD Output Description

SMPTE ST 424-5 Link 1 input stream for

Monitor Output 1 output connection

SMPTE ST 424-5 Link 2 input stream for

Monitor Output 1 output connection

SMPTE ST 424-5 Link 3 input stream for

Monitor Output 1 output connection

SMPTE ST 424-5 Link 4 input stream for

Monitor Output 1 output connection

SMPTE ST 424-5 Link 1 input stream for

Monitor Output 2 output connection

SMPTE ST 424-5 Link 2 input stream for

Monitor Output 2 output connection

366

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring an IPVU Device

Input Spigot Number HD Output Description

Spigot7

Spigot8

Not used

UHD Output Description

SMPTE ST 424-5 Link 3 input stream for

Monitor Output 2 output connection

SMPTE ST 424-5 Link 4 input stream for

Monitor Output 2 output connection

To configure an IPVU Device

1 Add the IPVU device to the Topology: from the Device Library , Discovered , find an

IPVU device bubble that you want to control. See

To add a Discovered Device to a

Topology , on page 227.

2 Configure the IPVU properties. See also

Description of Common Device Properties , on page 348. The IPVU device should be first configured with GV Orbit Client before being

integrated into GV Orbit Client as most configuration parameters shown in GV Orbit

Client are shown for information purposes only.

Parameter Description

Network Host Name The hostname is the unique name by which the associated IPVU is known on the network.

Domain ID Set the same Domain IDs on all IPVU devices that are to communicate with each other on the network.

The default value for Grass Valley equipment is 101 .

Valid range: 0 to 232.

Internal wiring Shows if the internal modeling of the IPVU is complete.

367

Special Device Configuration Tasks

Configuring an IPVU Device

GV Orbit Client Version 2.0.0

User Guide

3 Create and connect the core IP devices to the IPVU. See

Methods to Link Devices in a

Topology , on page 239.

368

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring an IQMix or IQUCP25 Device

The IQMIX / IQUCP25 series is a range of multi-channel video over IP transceiver modules developed for use within low latency, high bandwidth Ethernet IP networks, capable of encoding / decoding multiple SDI signals. They provide both compressed and uncompressed modes of operation.

The inputs and outputs of an IQMIX / IQUCP25 are called spigots . There are a variety of spigot configurations that are available; for example, 6 inputs / 6 outputs, 12 inputs / 0 outputs, 0 inputs / 12 outputs, 8 inputs / 0 outputs. See also

How to Know if a Spigot is an

Input or an Output , on page 370.

WARNING

The spigot configuration is set through GV Orbit Client and then GV Orbit Client reads it from the IQMIX / IQUCP25 card. For any given spigot, you must know which mode (input or output) has been configured to connect the spigots correctly in GV

Orbit Client.

There is no offline configuration of the IQMIX / IQUCP25 device. It must first be discovered on the network by GV Orbit Client.

The IQMIX / IQUCP25 device must have been previously configured with GV Orbit Client before being integrated into GV Orbit Client as most configuration parameters shown in GV

Orbit Client are for information purposes only (GV Orbit Client reads it from the IQMIX /

IQUCP25 devices). See the IQMIX / IQUCP25 User Manual for more information.

PREREQUISITES: The Domain ID of the IQMIX / IQUCP25 device(s) must be set in the System

Controller Group Properties under Domain Ids . See

Configuring a Controller Group , on page 199. These devices must be on the same subnet that the GV Orbit Client server is

connected to.

Note: An IQMix using VC2 video compression format is not currently supported by

GV Orbit Client.

Related Topics

•

How to Know if a Spigot is an Input or an Output , on page 370

•

Configuring UHD 4K Two-Sample Interleave Division IP Streams for use with an IQMix,

IQUCP, or IPVU Device , on page 371.

•

Configuring UHD 4K Quad-Link SDI Streams for use with an IQMix, IQUCP, or IPVU

Device , on page 376

369

Special Device Configuration Tasks

How to Know if a Spigot is an Input or an Output

GV Orbit Client Version 2.0.0

User Guide

To configure an IQMIX / IQUCP25 Device

1 Add the IQMIX / IQUCP25 device to the Topology: from the Device Library , Discovered ,

find an IQMIX / IQUCP25 device bubble that you want to control. See To add a

Discovered Device to a Topology , on page 227.

2 Configure the IQMIX / IQUCP25 properties. See also Description of Common Device

Properties , on page 348. The IQMIX / IQUCP25 device should be first configured with

GV Orbit Client before being integrated into GV Orbit Client as most configuration parameters shown in GV Orbit Client are shown for information purposes only.

Parameter Description

Network Host Name The hostname is the unique name by which the associated IQMIX /

IQUCP25 is known on the network.

Domain ID

Internal wiring

Set the same Domain IDs on all IQMIX / IQUCP25 devices that are to communicate with each other on the network.

The default value for Grass Valley equipment is 101 .

Valid range: 0 to 232.

Shows if the internal modeling of the IQMIX / IQUCP25 is complete.

3 Create and connect the edge devices (SDI and IP devices) that are connected to the

IQMIX / IQUCP25. See Methods to Link Devices in a Topology , on page 239.

How to Know if a Spigot is an Input or an Output

To know if a spigot In GV Orbit Client is an input or output, proceed as follows:

1 Select the device bubble on the Topology Configurator. See

Configuring an IQMix or IQUCP25 Device , on page 369.

2 Expand Ip Spigots in Device Properties and select a spigot from the list.

3 For each spigot, interpret the Mode property as follows:

• SRC = Output

• DST = Input

370

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring UHD 4K Two-Sample Interleave Division IP Streams for use with an IQMix, IQUCP, or IPVU Device

To support UHD 4K streams, the image is mapped onto four SDI HD sub-images using a two-sample interleave division. This means each of the four sub-stream carries a quarterresolution picture. These four sub-streams must:

• each be individually represented by four logical levels; one level for each sub-stream.

For example, SDI2SIuhd1 , video2SIuhd2 , video2SIuhd3 and video2SIuhd4 .

• The first logical level, SDI2SIuhd1 , carries the full SDI stream for video, audio, and ancillary data.

• The remaining logical levels will only use the video stream from the SDI levels, video2SIuhd2 , video2SIuhd3 , and video2SIuhd4 .

• be logically linked together so that they are switched together at once ensuring that there is no switching delay between the four streams that would create visible glitches between the four quadrants.

The following shows the typical video stream composition of a two-sample interleave division display with the associated logical levels used in this procedure.

1 1 2 2

3 3 4 4

1 1 2 2

3 3 4 4

1 1 2 2

3 3 4 4

1 1 2 2

3 3 4 4

1 1 2 2

3 3 4 4

1 1 2 2

3 3 4 4

1 1 2 2

3 3 4 4

1 1 2 2

3 3 4 4

UHD Composite Image

1 1 2 2

3 3 4 4

1: SMPTE ST 424-5 Link 1 pixels carried by HD Logical

Level SDI2SIuhd1

2: SMPTE ST 424-5 Link 2 pixels carried by HD Logical

Level Video2SIuhd2

3: SMPTE ST 424-5 Link 3 pixels carried by HD Logical

Level Video2SIuhd3

4: SMPTE ST 424-5 Link 4 pixels carried by HD Logical

Level Video2SIuhd4

371

Special Device Configuration Tasks GV Orbit Client Version 2.0.0

Configuring UHD 4K Two-Sample Interleave Division IP Streams for use with an IQMix, IQUCP, or IPVU Device User Guide

PREREQUISITES:

• For IQMix / IQUCP device(s):

• The IQMix / IQUCP device(s) must already be configured in GV Orbit Client. See

• Configure the IQMix / IQUCP device spigots to be used for UHD in GV Orbit Client by enabling the UHD Links parameter in the Link Control Page for all quad-link signal spigots.

• Set the corresponding spigots to use 2SI signals: Under TPG , clear (disable) the

SDQS check boxes as required.

• The IPVU device(s) must already be configured in GV Orbit Client. See Configuring an

IPVU Device , on page 366.

• Configure the IPVU device spigots to be used for UHD in GV Orbit Client by:

• Enabling the Enable UHD parameter in the IPVU configuration page for

Monitor Output 1 and 2 as necessary.

• Set the UHD Mode to 2SI .

372

To configure UHD 2SI Streams with an IPVU Device

1 Add IPVU device(s) to the topology and configure them in GV Orbit Client. See

Configuring an IPVU Device , on page 366.

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring UHD 4K Two-Sample Interleave Division IP Streams for use with an IQMix, IQUCP, or IPVU Device

2 Link the IPVU device(s) to the logical sources and destinations in GV Orbit Client. See

Methods to Link Devices in a Topology , on page 239.

The following topology will be used as an example, where the IPVU receives UHD stream sources from the GV Node.

3 Create the logical levels necessary to support 2SI sources and destinations: Create the following UHD logical levels from the Logical Level Editor from the pre-existing SDI logical level: SDI2SIuhd1 , SDI2SIuhd2 , SDI2SIuhd3 , and SDI2SIuhd4

. See Duplicating a Logical Level , on page 213.

Duplicate the SDI Logical Level four times to create SDI2SIuhd1 ,

SDI2SIuhd2 , SDI2SIuhd3 , and SDI2SIuhd4

For this example, only the following “2SIuhd” levels will be used: SDI2SIuhd1 ,

Video2SIuhd2 , Video2SIuhd3 , and Video2SIuhd4 . It is optional to delete all other

373

Special Device Configuration Tasks GV Orbit Client Version 2.0.0

Configuring UHD 4K Two-Sample Interleave Division IP Streams for use with an IQMix, IQUCP, or IPVU Device User Guide

“2SIuhd” logical levels for a cleaner presentation, if they are not used elsewhere. See

Deleting a Logical Level , on page 216.

4 From the Multilevel Table of the Logical Device Table , under the Sources tab, click the

Levels icon . See Accessing the Logical Device Table task , on page 259.

5 Select the levels you want to display in the Logical Device Table . As shown below, the

2SIuhd filter was applied and then you can select the 4 SIuhd levels ( SDI2SIuhd1 ,

Video2SIuhd2 , Video2SIuhd3 , and Video2SIuhd4 ), each representing one sub-stream of a of a 2SI signal. Click OK .

374

The columns of the Multilevel Table updates to only show the SDI2SIuhd1 ,

Video2SIuhd2 , Video2SIuhd3 , and Video2SIuhd4 columns .

6 In the Logical Device Table, select a source’s row to which you want to add the streams.

See

To configure streams for the new sources , on page 269.

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring UHD 4K Two-Sample Interleave Division IP Streams for use with an IQMix, IQUCP, or IPVU Device

7 In the Logical Device Table, map streams with levels: Configure the UHD sources and destinations by assigning quad-link IP streams to each level.

Select the row before dropping a destination onto it

8 Select the levels you want to display in the Logical Device Table . Again, select the 4

SIuhd levels ( SDI2SIuhd1 , Video2SIuhd2 , Video2SIuhd3 , and Video2SIuhd4 ), each representing one sub-stream of a of a 2SI signal. Click OK .

The columns of the Multilevel Table updates to only show the SDI2SIuhd1 ,

Video2SIuhd2 , Video2SIuhd3 , and Video2SIuhd4 columns.

9 From the Multilevel Table of the Logical Device Table , under the Destinations tab, click the Levels icon . See

Accessing the Logical Device Table task , on page 259.

10 Repeat step 6 for destinations.

11 Test the configuration by making takes between a logical source and destination that use the two-sample interleave division streams. See

Performing a Take in Router

Control , on page 467. See in Pathfinder that the correct source sub-streams are

received by each destination. See Viewing Information about the Destinations , on page 451.

375

Special Device Configuration Tasks

Configuring UHD 4K Quad-Link SDI Streams for use with an IQMix, IQUCP, or IPVU Device

GV Orbit Client Version 2.0.0

User Guide

Configuring UHD 4K Quad-Link SDI Streams for use with an IQMix,

IQUCP, or IPVU Device

To support UHD 4K streams, a quad-link (square division) configuration is used. That is, the

UHD image is divided into four SDI HD quadrants, and each quadrant is sent as four separate streams. These four streams must:

• each be individually represented by four logical levels; one level for each quadrant. For example, SDI , SDIuhd2 , SDIuhd3 and SDIuhd4 .

• The first logical level is the base SDI logical level. This logical level carries the video, audio, and ancillary data.

• The SDIuhd2 , SDIuhd3 and SDIuhd4 logical levels are video only.

The following shows the typical video stream composition of a UHD quad-link display with the associated logical levels used in this procedure.

Quadrant 1, Link 1

HD Logical Level SDI

Quadrant 2, Link 2

HD Logical Level

SDIuhd2

Quadrant 3, Link 3

HD Logical Level

SDIuhd3

Quadrant 4, Link 4

HD Logical Level

SDIuhd4

UHD Composite Image

376

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring UHD 4K Quad-Link SDI Streams for use with an IQMix, IQUCP, or IPVU Device

PREREQUISITES:

• For IQMix / IQUCP device(s):

• The IQMix / IQUCP device(s) must already be configured in GV Orbit Client. See

Configuring an IQMix or IQUCP25 Device , on page 369.

• Configure the IQMix / IQUCP device spigots to be used for UHD in GV Orbit Client by enabling the UHD Links parameter in the Link Control Page for all quad-link signal spigots.

• Set the corresponding spigots to use Square Division signals: Under TPG , set

(enable) the SDQS check boxes as required.

• For IPVU device(s):

• The IPVU device(s) must already be configured in GV Orbit Client. See Configuring an IPVU Device , on page 366.

• Configure the IPVU device spigots to be used for UHD in GV Orbit Client by:

• Enabling the Enable UHD parameter in the IPVU configuration page for

Monitor Output 1 and 2 as necessary.

• Set the UHD Mode to SQD .

377

Special Device Configuration Tasks

Configuring UHD 4K Quad-Link SDI Streams for use with an IQMix, IQUCP, or IPVU Device

GV Orbit Client Version 2.0.0

User Guide

To configure UHD Quad-Link Streams

Create the logical levels necessary to support quad-link sources and destinations.

1 Create the following UHD logical levels from the Logical Level Editor from the preexisting SDI logical level: SDIuhd1 , SDIuhd2 , SDIuhd3 and SDIuhd4 . See

Duplicating a

Logical Level , on page 213.

Duplicate the SDI Logical Level four times to create SDIuhd1 , SDIuhd2 ,

SDIuhd3 , and SDIuhd4

2 From the Multilevel Table of the Logical Device Table , click the Levels icon . See

Accessing the Logical Device Table task , on page 259.

3 Select the levels you want to display in the table. As shown below, a filter SDIuhd was applied and then you can select the 4 SDI UHD levels and click OK .

378

The logical device table will show 4 items ( SDIuhd1 , SDIuhd2 , SDIuhd3 , and SDIuhd4 ), each with a UHD level representing one quadrant of a of a quad-link signal.

4 Add IQMix / IQUCP device(s) to the topology and configure them in GV Orbit Client. See

Configuring an IQMix or IQUCP25 Device , on page 369.

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring UHD 4K Quad-Link SDI Streams for use with an IQMix, IQUCP, or IPVU Device

5 Link the IQMix / IQUCP device(s) to the logical sources and destinations in GV Orbit

Client. See

Methods to Link Devices in a Topology , on page 239.

The following topology will be used as an example, where the IQMix is used as the UHD stream sources (called uhd1 and uhd2 ) and the IQUCP is used as the UHD stream destination (called DEST-uhd ).

6 In the Logical Device Table, map streams with levels: Configure the UHD sources and destinations by assigning quad-link IP streams to each level.

Select the row before dropping a destination onto it

7 Repeat step 6 for destinations.

8 Test the configuration by making takes between a logical source and destination that use the quad-level link streams. See

Performing a Take in Router Control , on page 467.

See in Pathfinder that the correct quad-level link streams are received by each

destination. See Viewing Information about the Destinations , on page 451.

379

Special Device Configuration Tasks

Configuring an MV-820-IP Multiviewer Device

GV Orbit Client Version 2.0.0

User Guide

Configuring an MV-820-IP Multiviewer Device

The MV 820 IP multiviewer has 48 IP inputs and 12 IP outputs in a 2 RU chassis, making it ideal for high-density IP monitoring applications. Internally, the MV 820 IP multiviewer is an MV 820 SDI multiviewer wrapped inside four IQMix cards to provide IP connectivity through a rear panel that supports the QSFP network interface adapters (refer to the MV-

820 Multiviewer User Manual, where this is referred to as the Video IP Circuitry ). These four

IQMix cards are used to convert the IP network input streams to feed the 48  SDI inputs of the MV-820 cards, and uses three of the four same IQMix cards to also convert the 12  SDI mosaic outputs of the MV-820 cards into IP stream outputs. These IQMix cards are labeled as MV 820 IP REAR

in GV Orbit Client and GV Orbit Client. See Configuring an IQMix or

IQUCP25 Device , on page 369 for more information about how to configure an IQMix.

The inputs and outputs of an MV 820 IP are called spigots that, within GV Orbit Client, are provided by four MV 820 IP REAR devices with the following spigot configuration: 48 input spigots across four MV 820 IP REAR devices and 12 mosaic output spigots across three

MV 820 IP REAR devices. The third MV 820 IP REAR device has no output spigots.

MV-820-IP-REAR ‘A’: 12 Input Spigots

MV-820-IP-REAR ‘B’: 12 Input Spigots

MV-820-IP-REAR ‘C’: 12 Input Spigots

MV-820-IP-REAR ‘D’: 12 Input Spigots

MV 820 SDI

Multiviewer

MV-820-IP-REAR ‘A’: 4 Output Spigots

MV-820-IP-REAR ‘B’: 4 Output Spigots

MV-820-IP-REAR ‘C’: 0 Output Spigots

MV-820-IP-REAR ‘D’: 4 Output Spigots

For each MV 820 IP REAR device, the spigots are used as follows. The third MV 820 IP REAR

device has no output spigots. See also How to Know if a Spigot is an Input or an Output , on page 370.

Input: Spigot 5

Input: Spigot 16

IQMix

Mosaic Output: Spigot 1

Mosaic Output: Spigot 2

Mosaic Output: Spigot 3

Mosaic Output: Spigot 4

There is no offline configuration of the MV 820 IP device. It must first be discovered on the network by GV Orbit Client.

The MV 820 IP multiviewer must have been previously configured with GV Orbit Client before being integrated into GV Orbit Client as most configuration parameters shown in GV

Orbit Client are for information purposes only (GV Orbit Client reads it from the MV 820 IP cards). See the MV 820 IP User Guide for more information.

For example, in GV Orbit Client 2.5 the MV 820 IP is shown as 4  MV 820 IP-REAR.

PREREQUISITES: The Domain ID of the MV 820 IP devices must be set in the System

Controller Group Properties under Domain Ids . See

Configuring a Controller Group , on

380

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring an MV-820-IP Multiviewer Device

page 199. These devices must be on the same subnet that the GV Orbit Client server is

connected to.

Note: An MV 820 IP using VC2 video compression format is not currently supported by GV Orbit Client.

To configure an MV 820 IP Multiviewer

1 Select the required Area. See Selecting an Area , on page 203.

2 Select the required topology. See Selecting a Graph , on page 204.

3 The topology must be currently:

• Activated (see

• Unlocked (see

clicking an instance. See Defining Device Properties , on page 247 for more information.

4 From the Device Library , on the left, select Discovered , from the drop-down list.

5 From the Device Library , Discovered , find the four MV 820 IP REAR devices with the IP addresses that correspond with those for the MV 820 IP multiviewer on your network: select one of the MV 820 IP REAR device bubbles and drag it into position on the

Topology and release the mouse button.

The device pulled from the Device Library , Discovered becomes greyed out and another instance of the same device instance cannot be added again to the Topology.

6 Now create a device group by adding the remaining three MV 820 IP REAR device bubbles on top of the MV 820 IP REAR already on the Topology: a Select another MV 820 IP REAR device bubble from the Device Library and drag it on top of the first MV 820 IP REAR device instance already on the Topology and release the mouse button. b Repeat this action for the third and fourth MV 820 IP REAR device bubble in the

Device Library .

The four MV 820 IP REAR device instances are shown as a single device on the

Topology and can be individually configured in the Property Editor , under Devices , by

7 Click on the name of the device underneath the bubble to name the device or device

group. See To name a device and set the number of devices in the group , on page 225.

381

Special Device Configuration Tasks

Configuring an MV-820-IP Multiviewer Device

GV Orbit Client Version 2.0.0

User Guide

8 Configure the MV 820 -

IP multiviewer’s properties. See also Description of Common

Device Properties , on page 348. The MV

820 IP device should be first configured with

GV Orbit Client before being integrated into GV Orbit Client as most configuration parameters shown in GV Orbit Client are shown for information purposes only.

Parameter Description

Network Host Name The hostname is the unique name by which the associated MV 820 IP is known on the network.

Domain ID Set the same Domain IDs on all MV 820 IP devices that are to communicate with each other on the network.

The default value for Grass Valley equipment is 101 .

Valid range: 0 to 232.

Internal wiring Shows if the internal modeling of the MV 820 IP is complete.

9 Create the logical sources and destinations in GV Orbit Client for the MV 820 IP by adding SDI devices to the topology and then linking them. See

Methods to Link

Devices in a Topology , on page 239. An example is shown below.

Logical Sources

Represent the

Multiviewer’s SDI

Mosaic Outputs

Logical

Destinations

Represent the

Multiviewer’s SDI

Inputs

These logical sources and destinations represent the SDI inputs and outputs of the

MV 820 multiviewer that will be used when making a take. a From the Device Library , Virtual Devices, find the SDI Device bubble and drag it into position on the Topology and release the mouse button.

382

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring an MV-820-IP Multiviewer Device b Click on the name of the device underneath the bubble to name the device or

device group. See To name a device and set the number of devices in the group , on page 225. For example, Enter

MV-Out in both the Name and Short Name fields, then enter 12 for the number of device instances. These parameters can also be set in the Property Editor .

c From the Device Library , Virtual Devices, find the SDI Device bubble and drag it into position on the Topology and release the mouse button.

d Click on the name of the device underneath the bubble to name the device or device group. For example, Enter MV-In in both the Name and Short Name fields, then enter 48 for the number of device instances. e Interconnect the SDI source and destination devices to the proper IQMix spigot SDI inputs and outputs as shown above.

If needed, contact support for more information as how to configure this device. See

Grass Valley Technical Support , on page 288.

383

Special Device Configuration Tasks

Configuring a Kahuna IP Production Switcher Device

GV Orbit Client Version 2.0.0

User Guide

Configuring a Kahuna IP Production Switcher Device

The Kahuna IP is a production switcher. Internally, the Kahuna IP production switcher is an

Kahuna SDI production switcher wrapped inside two IQMix cards to provide IP connectivity. These two IQMix cards are used to convert the IP network input streams to feed the 12  SDI inputs of the Kahuna, and the other IQMix card to convert the 12  SDI outputs of the Kahuna into IP stream outputs. These IQMix cards are labelled as

KahunaIPI10 and KahunaIPO10

in GV Orbit Client. See Configuring an IQMix or IQUCP25

Device , on page 369 for more information about how to configure an IQMix.

The inputs and outputs of a Kahuna IP are called spigots . There are 12 input and 12 output spigots. In the GV Orbit Client Device Library, the Kahuna IP switcher is discovered as two separate IP devices: the first represents the IP inputs (device type: KahunaIPI10) and the second represents the IP outputs (device type: KahunaIPO10).

KahunaIPI10: 12 Input Spigots

Kahuna SDI

Switcher

KahunaIPO10: 12 Output Spigots

There is no offline configuration of the Kahuna IP device. It must first be discovered on the network by GV Orbit Client.

The Kahuna IP device must have been previously configured with GV Orbit Client before being integrated into GV Orbit Client as most configuration parameters shown in GV Orbit

Client are for information purposes only (GV Orbit Client reads it from the Kahuna IP device).

See the Kahuna IP User Guide for more information.

PREREQUISITES: The Domain ID of the Kahuna IP device(s) must be set in the System

Controller Group Properties under Domain Ids . See

Configuring a Controller Group , on page 199. These devices must be on the same subnet that the GV Orbit Client server is

connected to.

To configure a Kahuna IP Device

1 Select the required Area. See Selecting an Area , on page 203.

2 Select the required topology. See Selecting a Graph , on page 204.

3 The topology must be currently:

• Activated (see

• Unlocked (see

To name a device and set the number of devices in the group , on page 225.

384

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a Kahuna IP Production Switcher Device

4 From the Device Library , on the left, select Discovered from the drop-down list.

The Kahuna IP is discovered as two separate IP devices: the first represents the IP inputs

(device type: KahunaIPI10) and the second represents the IP outputs (device type:

KahunaIPO10).

5 From the Device Library , Discovered , find the Kahuna IP input device that you want to control: select the KahunaIPI10 device bubble and drag it into position on the

Topology and release the mouse button.

The device pulled from the Device Library , Discovered becomes greyed out and another instance of the same device instance cannot be added again to the Topology.

6 From the Device Library , Discovered , find the matching KahunaIPO10 device bubble and drag it into position on the Topology and release the mouse button.

7 For each Kahuna IP device (IP inputs device type: KahunaIPI10 and IP outputs device type: KahunaIPO10 ) Click on the name of the device underneath the bubble to name the device. See

8 Configure the Kahuna IP properties. See also Description of Common Device

Properties , on page 348. The Kahuna IP device should be first configured with GV Orbit

Client before being integrated into GV Orbit Client as most configuration parameters shown in GV Orbit Client are shown for information purposes only.

Parameter Description

Network Host Name The hostname is the unique name by which the associated Kahuna IP is known on the network.

Domain ID Set the same Domain IDs on all Kahuna IP devices that are to communicate with each other on the network.

The default value for Grass Valley equipment is 101 .

Valid range: 0 to 232.

Internal wiring Shows if the internal modeling of the Kahuna IP is complete.

385

Special Device Configuration Tasks

Configuring a Kahuna IP Production Switcher Device

GV Orbit Client Version 2.0.0

User Guide

9 Create and connect the edge devices (SDI and IP devices) that are connected to the

Kahuna IP. See Methods to Link Devices in a Topology , on page 239. An example is

shown below.

Logical Sources

Represent the

Switcher’s SDI

Mosaic Outputs

386

Logical Destinations

Represent the

Switcher’s SDI Inputs

These logical sources and destinations represent the SDI inputs and outputs of the

Kahuna switcher that will be used when making a take. a From the Device Library , Virtual Devices, find the SDI Device bubble and drag it into position on the Topology and release the mouse button.

b Click on the name of the device underneath the bubble to name the device or

device group. See To name a device and set the number of devices in the group , on page 225. For example, Enter

Switcher-Out in both the Name and Short Name fields, then enter 3 for the number of device instances. These parameters can also be set in the Property Editor .

c From the Device Library , Virtual Devices, find the Monitor Device bubble and drag it into position on the Topology and release the mouse button.

d Click on the name of the device underneath the bubble to name the device or device group. For example, Enter Switcher-In in both the Name and Short Name fields, then enter 12 for the number of device instances. e Interconnect the SDI source and destination devices to the proper IQMix spigot SDI inputs and outputs as shown above.

If needed, contact support for more information as how to configure this device. See

Grass Valley Technical Support , on page 288.

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a K-Frame Production Switcher

The K-Frame is a series of production switchers, and certain models support IP connectivity.

The following frames are supported:

• K-Frame-V Production Switcher has 4 slots each providing 8 inputs and 4 outputs to the switcher, for a total of 32 inputs x 16 outputs.

• K-Frame-X Production Switcher has 14 slots. 10 slots each providing 16 inputs and 8 outputs to the switcher, followed by 4 slots each providing 8 inputs and 4 outputs of the switcher, for a total of 192 inputs x 96 outputs.

The following diagram shows a K-Frame-V / K-Frame-X Production Switchers populated with a typical assortment of I/O cards.

8 × 4 I/O SDI Card

8 Inputs, 4 Outputs

Inputs 1 to 8

Outputs 1 to 4

SFPs 1 to 4

8 × 4 I/O IP Card

8 Inputs, 4 Outputs, 4 SFPs

Inputs 9 to 16

Outputs 5 to 8

SFPs 5 to 8

K‐Frame‐V Series

8 × 4 I/O IP Card

8 Inputs, 4 Outputs, 4 SFPs

Inputs 17 to 24

Outputs 9 to 12

SFPs 9 to 12

8 × 4 I/O IP Card

8 Inputs, 4 Outputs, 4 SFPs

Inputs 25 to 32

Outputs 13 to 16

SFPs 13 to 16

16 × 8 I/O SDI Card

16 Inputs, 8 Outputs

16 × 8 I/O IP Card

16 Inputs, 8 Outputs, 8 SFPs

16 × 8 I/O IP Card

16 Inputs, 8 Outputs, 8 SFPs

16 × 8 I/O IP Card

16 Inputs, 8 Outputs, 8 SFPs

16 × 8 I/O IP Card

16 Inputs, 8 Outputs, 8 SFPs

16 × 8 I/O IP Card

16 Inputs, 8 Outputs, 8 SFPs

16 × 8 I/O IP Card

16 Inputs, 8 Outputs, 8 SFPs

16 × 8 I/O SDI Card

16 Inputs, 8 Outputs

Inputs 1 to 16

Outputs 1 to 8

SFPs 1 to 8

Inputs 17 to 32

Outputs 9 to 16

SFPs 9 to 16

Inputs 33 to 48

Outputs 17 to 24

SFPs 17 to 24

Inputs 49 to 64

Outputs 25 to 32

SFPs 25 to 32

Inputs 65 to 80

Outputs 33 to 40

SFPs 33 to 40

Inputs 81 to 96

Outputs 41 to 48

SFPs 41 to 48

Inputs 97 to 112

Outputs 49 to 56

SFPs 49 to 56

Inputs 113 to 128

Outputs 57 to 64

SFPs 57 to 64

Inputs 129 to 144

Outputs 65 to 72

SFPs 65 to 72

Inputs 145 to 160

Outputs 73 to 80

SFPs 73 to 80

K‐Frame‐X Series

8 × 4 I/O SDI Card

8 Inputs, 4 Outputs

Inputs 161 to 168

Outputs 81 to 84

SFPs 81 to 84

8 × 4 I/O IP Card

8 Inputs, 4 Outputs, 4 SFPs

Inputs 169 to 176

Outputs 85 to 88

SFPs 85 to 88

8 × 4 I/O IP Card

8 Inputs, 4 Outputs, 4 SFPs

Inputs 177 to 184

Outputs 89 to 92

SFPs 89 to 92

8 × 4 I/O SDI Card

8 Inputs, 4 Outputs

Inputs 185 to 192

Outputs 93 to 96

SFPs 93 to 96

There are two types of modules which can be used in the K-Frame Production Switcher slots:

• SDI only card, equipped with BNC connectors.

387

Special Device Configuration Tasks

Configuring a K-Frame Production Switcher

GV Orbit Client Version 2.0.0

User Guide

• IP only card, equipped with SFP connectors.

Here are some details about IP cards you will need to know to model your K-Frame

Production Switcher in GV Orbit Client:

• An SFP can receive two streams and transmit one. A stream is a group of the essence flows (a 2022-6 stream has a single flow, a TR-04 stream has two flows and a SMPTE

2110 stream has three flows)

• Each SFP stream maps directly to a switcher input or output of the slot. For example: the IP card in the second slot of the K-Frame-V Production Switcher has 4 SFP pairs (for redundancy) providing signals to inputs 9-16 of the switcher. The first SFP provides streams for inputs 9-10, the second SFP provides streams for inputs 11-12 and so on.

• IP cards support SMPTE 2022-6, SMPTE 2110, and TICO.

• Redundancy in SMPTE 2022 and SMPTE 2110 is supported.

• For SMPTE 2110-30, the following profiles are supported: L16/48K/125us, L16/48K/1ms,

L24/48K/125us, L24/48K/1ms.

Note that GV Orbit Client only controls the K-Frame Production Switcher’s IP receivers and transmitters. In consequence, The K-Frame Production Switcher must have been previously setup and configured before being integrated into GV Orbit Client. See the K-Frame

Installation & Service Manual for more information.

PREREQUISITES: GV Orbit Client must have IP connectivity to the K-Frame Production

Switcher:

• to automatically detect the K-Frame Production Switcher’s model (K-Frame-V / K-

Frame-X) and its current configuration parameters that are needed by GV Orbit Client.

• before making connections to the Production Switcher bubble in GV Orbit Client. See

To configure a K-Frame Production Switcher , on page 390.

388

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a K-Frame Production Switcher

K-Frame Production Switcher Nomenclature used in GV Orbit Client

The following diagram shows the nomenclature used in GV Orbit Client for the K-Frame-V

Production Switcher signal flow. A K-Frame-X Production Switcher’s signal flow uses a similar architecture, with more inputs and outputs.

Slots

8 4

Inputs 1 to 8

Outputs 1 to 4

K‐Frame‐V

Video/Audio Routing & Processing

32 Inputs & 16 Outputs

8 4

Inputs 9 to 16

Outputs 5 to 8

8 4

Inputs 17 to 24

Outputs 9 to 12

8 4

Inputs 25 to 32

Outputs 13 to 16

Boards

IP I/O Board

SFPs 1 to 4

IP I/O Board

SFPs 5 to 8

IP I/O Board

SFPs 9 to 12

IP I/O Board

SFPs 13 to 16

System SFPs

Physical SFPs* A

1 2 3 4

B A B A B A B

5 6 7 8

A B A B A B A B

9 10 11 12

A B A B A B A B

13 14 15 16

A B A B A B A B

Streams

Flows

Video

Audio

Ancillary

Port Number Equivalent

Used in GV Orbit

Control / GV Convergent

1 17 2 18 3 19 4 20 5 21 6 22 7 23 8 24 9 25 10 26 11 27 12 28 13 29 14 30 15 31

SMPTE 2022‐7 Support: Ports shown in red are for the Red LAN. Ports shown in blue are for the Blue LAN

16 32

* This is shown in the Short Name property for a port. For example, SFP‐1A is the first input port.

* Note that GV Orbit Client’ s Short Name property for a port is composed of a combination of the System SFP number and the Physical SFP letter in the following format:

SFP-[System SFP number][Physical SFP letter]

389

Special Device Configuration Tasks

Configuring a K-Frame Production Switcher

GV Orbit Client Version 2.0.0

User Guide

For example, SFP-1A is the first input port. This port is shown below in the K-Frame Menu for reference.

When Redundancy Mode is Enabled in the K-Frame Menu, you must use a SMPTE ST 2022-7 network setup; see

Configuring Network Switch Redundancy to Support SMPTE ST 2022 7 , on page 415.

To configure a K-Frame Production Switcher

1 Add the Production Switcher device to the Topology: from the Device Library , Virtual

Device , find the Production Switcher

device bubble. See To add a Virtual Device to a topology , on page 224.

390

2 Click on the name of the device underneath the bubble to enter a meaningful name to identify this device in the Name

field. See To name a device and set the number of devices in the group , on page 225.

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a K-Frame Production Switcher

These parameters can also be set in the Property Editor .

3 Click New next to Control Port at the top of the Property Editor and select K-

Frame CPL TCP/IP from the list. See also

Defining Device Properties , on page 247 for

more information.

The K-Frame CPL TCP/IP tab appears. To remove the control port, click Delete.

4 Configure the K-Frame Production Switcher properties. See also Description of

Parameter Description

Network Host Name The hostname is the unique name by which the associated K-Frame

Production Switcher is known on the network.

IP Address The IP address of the K-Frame Production Switcher to be controlled.

Once connected, GV Orbit Client automatically detects the K-Frame

Production Switcher’s model (K-Frame-V / K-Frame-X) and K-Frame

Production Switcher’s configuration parameters that are needed by

GV Orbit Client.

391

Special Device Configuration Tasks

Configuring a K-Frame Production Switcher

GV Orbit Client Version 2.0.0

User Guide

Parameter

Connection State 1

Connection State 2

Frame Model

Description

K-Frame Production Switcher Connection State 1 shows the connection status of the K-Frame Production Switcher with the primary server of a server group.

K-Frame Production Switcher Connection State 2 shows the connection status of the K-Frame Production Switcher with the secondary server of a server group. See

The topology is inactive (see Activating a Topology , on page 253) or the K-Frame Production Switcher does not have network

unknown:

connectivity to the GV Orbit Client server(s).

Reconnecting: The topology has been activated and GV Orbit Client is learning the K-Frame Production Switcher’s current configuration.

offline: The K-Frame Production Switcher does not have network connectivity to the GV Orbit Client server(s).

online: The K-Frame Production Switcher is connected to the GV Orbit

Client server(s).

Once the topology has been activated, this shows the frame model.

This is shown for information purposes only.

5 Activate the topology. See Activating a Topology , on page 253.

The current K-Frame Production Switcher input and output ports are read into GV Orbit

Client and become available to be connected within GV Orbit Client. According to the type of streams configured in K-Frame Production Switcher, the corresponding logical

levels are created in the Logical Device Table. See Logical Device Table Tasks , on page 259 for more information.

392

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a K-Frame Production Switcher

When a port is selected, see the Short Name property to see the K-Frame Production

Switcher’s internal port reference. For more information, see K-Frame Production

Switcher Nomenclature used in GV Orbit Client , on page 389.

Each input port supports two sources. When a stream is selected, see the Short Name property to see the stream type currently configured in the K-Frame Production

Switcher.

Streams Description

This is the video stream for the first source.

This is the audio stream for the first source a .

This is the Ancillary stream for the first source

a .

This is the video stream for the second source.

This is the audio stream for the second source

a .

This is the Ancillary stream for the second source a

a.This stream is not shown if the selected port is configured as SMPTE 2022-6.

Short Name

Swr-In-1A-Vid

Swr-In-1A-Aud

Swr-In-1A-Anc

Swr-In-2A-Vid

Swr-In-1A-Aud

Swr-In-1A-Anc

The K-Frame Production Switcher can now be used to make takes. See Router Control Tasks , on page 466 for more information.

393

Special Device Configuration Tasks

Adding NMOS Devices to a Topology

GV Orbit Client Version 2.0.0

User Guide

Adding NMOS Devices to a Topology

GV Orbit Client supports Networked Media Open Specifications (NMOS) AMWA IS-04 for device discovery and registration and IS-05 for connection management. Furthermore, it supports AMWA BCP-002-01 for the natural grouping of NMOS resources.

GV Orbit Client has a built-in NMOS registry (see below) that can be used to register NMOS devices. To be able to discover NMOS devices, you have one of the following options:

• Allow GV Orbit Client to automatically discover one or more NMOS registries through

DNS-SD. DNS-SD can discover an NMOS registry that is available on the network and registered in your DNS server.

• Point GV Orbit Client to use its internal NMOS registry (when enabled), or to an external

NMOS registry.

PREREQUISITES:

• Entries for your NMOS registries have been added to the network DNS server. This enables automatic DNS-SD discovery. Contact your IT department to do so. Otherwise you can manually specify the registry to connect to.

Notes

• GV Orbit Client listens for changes to any of the nodes in the registry. As it receives updates, it automatically updates any device that is dropped onto any topology that is associated with that node.

• If the registry is shut down, or the node is stopped and is removed from the registry, the devices will disappear from the list of discovered devices. The devices you already have dropped will remain on the topology, but will no longer receive updates.

• If the registry is restarted or the node is restarted, GV Orbit Client will continue to update the devices on the topology (assuming the devices have the same UUID).

To configure GV Orbit Client for use with NMOS

To use GV Orbit Client with NMOS devices, you first must configure it to use its internal

NMOS registry, to use an external NMOS registry, or to automatically search for external

NMOS registries.

1 Open the System Controller Group Properties

. See Configuring a Controller Group , on page 199.

394

GV Orbit Client Version 2.0.0

User Guide

2 Set the following parameters.

Special Device Configuration Tasks

Adding NMOS Devices to a Topology

Parameter Description

NMOS Discovery DNS GV Orbit Client can automatically discover an NMOS registry through

NMOS Discovery

Search Domain

DNS-SD when the NMOS Discovery DNS and NMOS Discovery Search

Domain parameters are set.

NMOS Discovery DNS: The IP address of the network DNS server that is also used to support networked NMOS devices.

NMOS Discovery Search Domain: The network’s domain name on which GV Orbit Client will search for NMOS devices and the NMOS registry.

The NMOS Discovery DNS and NMOS Discovery Search Domain parameters are automatically retrieved from the GV Orbit Client’s server operating system when available (refer to IP Configuration ,

DNS tab in the GV Orbit Admin Guide ; see Related Documentation , on page 19). The operating system values can be overridden by setting the appropriate values here.

NOTE: If the DNS information is changed in the admin interface, GV

Orbit Client must be restarted to retrieve the new values from the OS.

395

Special Device Configuration Tasks

Adding NMOS Devices to a Topology

GV Orbit Client Version 2.0.0

User Guide

Parameter

NMOS Registry

Description

This shows the current NMOS Registry Query API URL (hostname / IP address and port number).

Set a static NMOS registry URL when NMOS registry discovery is nonfunctional or when you want to override it to use a specific NMOS registry.

If the NMOS Registry service is installed and running on the GV Orbit

Client server and you want to use GV Orbit Client’s built-in NMOS registry, set this URL to the local host IP address for this service: http://127.0.0.1:4041 . The NMOS registry is available to NMOS devices at the current system controller’s IP address a , on port 4041 . The priority of GV Orbit Client’s NMOS registry is 0.

If redundancy has been configured for GV Orbit Client, use the Virtual

IP Address, on port 4041 to access the NMOS registry.

Refer to Application Upgrade in the GV Orbit Admin Guide to install the NMOS Registry service and ensure that it is running. See Related

Documentation , on page 19.

To revert to automatic NMOS registry discovery, clear this field, press

<Enter>, and wait 10 seconds for the above NMOS Discovery DNS and

NMOS Discovery Search Domain parameters to take effect.

a.This is the same IP address as for GV Orbit Client’s administration interface. This is shown as IP

Address

in step 6 on page 201.

3 To be able to discover NMOS devices in GV Orbit Client, you have one of the following options:

• Allow GV Orbit Client to automatically discover one or more NMOS registries through DNS-SD (set the NMOS Discovery DNS and NMOS Discovery Search

Domain parameters). This is possible when the NMOS registries have been added to the network DNS server.

• Manually point GV Orbit Client to use the NMOS Registry service (when enabled), or to an external NMOS registry by setting a fixed URL for the registry (set the

NMOS Registry parameter).

Update the server’s Host file

In order for GV Orbit Client to communicate with the NMOS registry to retrieve a list of all its resources, retrieve update notifications, download SDP files and perform connection management, GV Orbit Client must be able to reach the host where the registry is running by its hostname. In order to do this, an entry for the NMOS host MUST be added to the server’s hosts file.

The Host file is found here: /etc/hosts

Sample entry:

10.37.80.177 <registryHostName>

Once the server for the NMOS registry has been added to the hosts file, the GV Orbit Client service needs to be restarted. See Reboot found under Upgrade Task in the GV Orbit Admin

Guide . See Related Documentation , on page 19.

Note that this applies even if you use the registry's IP address when specifying the URL of the NMOS Discovery Registry. Once the entry in the hosts file is added, the NMOS Registry

396

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Adding NMOS Devices to a Topology parameter can be either http://10.37.80.177:4041 or http://<registryHostName>:4041

To update the server’s Host file, contact Grass Valley Technical Support. See Grass Valley

Technical Support , on page 288.

NMOS Node control port status in GV Orbit Client

GV Orbit Client pings the NMOS node to keep the connection active using the URL http://XXX.XXX.XXX.XXX:4041/x-nmos/node/v1.2/self . GV Orbit Client uses the success of the ping to determine the node’s control port status (Online/Offline).

Note: If the NMOS node’s status is offline, check if the node’s URL contains only a hostname (as opposed to a numeric IP address). If GV Orbit Client cannot resolve the hostname, then you need to add an entry into the server’s hosts file and then restart

GV Orbit Client. GV Orbit Client must be able to resolve the node’s hostname in order to report the control port status as being online, download SDP files, and perform

connection management. See Update the server’s Host file , on page 396 and

Reboot found under Upgrade Task in the GV Orbit Admin Guide . See Related

Documentation , on page 19.

How to test the NMOS registry

Test the registry as follows: in a web browser, enter the following address into the browser’s address bar: http://XXX.XXX.XXX.XXX:4041/x-nmos/query/v1.2/

Where XXX.XXX.XXX.XXX

is the IP address of GV Orbit Client’s NMOS registry. This can be either GV Orbit Client’s system controller IP address (for its internal NMOS registry), or the query API IP address of an external NMOS registry, if available. For external NMOS registries, see the NMOS registry’s documentation as it may use a number of different IP addresses; one for the query API and another for the registration API for example.

The following NMOS registry switches show the current NMOS registry’s content: subscriptions nodes devices senders receivers flows sources

397

Special Device Configuration Tasks

To add an NMOS device to a topology

GV Orbit Client Version 2.0.0

User Guide

This is accessible by, for example, entering the following address into the browser’s address bar: http://XXX.XXX.XXX.XXX:4041/x-nmos/query/v1.2/ nodes

As the NMOS registry has just been started, it is normal that it is empty of content. Wait for devices to discover the NMOS registry and to publish their resources to the registry.

Note: If nodes are not published to the registry and are not listed under http://XXX.XXX.XXX.XXX:4041/x-nmos/query/v1.2/nodes discovered by GV Orbit Client. Further device troubleshooting will be required to identify why a device is not publishing to the NMOS registry.

, they will not be

About the grouphint tag

AMWA BCP-002-01 makes use of the grouphint tags to identify senders and receivers. When a discovered device publishes grouphint tag information in senders / receivers to the NMOS registry, GV Orbit Client will automatically create the related logical sources and destinations for the device, once the NMOS device has been added to the topology. If a discovered device does not publish grouphint tags to the NMOS registry, then you will have to create the logical sources and destinations for the device manually in GV Orbit Client.

To add an NMOS device to a topology

PREREQUISITES:

• There is an operational NMOS registry on the network.

• GV Orbit Client has been configured to connect to the NMOS registry. See To configure

GV Orbit Client for use with NMOS , on page 394.

• NMOS devices must be configured to publish their available resources to the NMOS registry.

Proceed as follows.

398

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

To add an NMOS device to a topology

1 Add the NMOS device to the Topology: from the Device Library , Discovered , find an

NMOS device bubble that you want to control. See To add a Discovered Device to a

Topology , on page 227.

2 Click on the name of the device underneath the bubble to name the device or device

group. See To name a device and set the number of devices in the group , on page 225.

3 The NMOS Control Port parameters are configured in the device’s Property Editor, under the Device Properties tab. See

Defining Device Properties , on page 247 for more

information about this tab.

4 Select NMOS tab (next to Control Port at the top of the Property Editor ) to configure the Device Properties in the Property Editor . See also

Description of Common Device

Properties , on page 348.

The NMOS control port properties appear.

Parameter Description

Connection State 1 / 2 This shows the current connection state to the NMOS nodes. When a redundant configuration is used (two GV Orbit Client servers form a cluster) Connection State 1 and Connection State 2 shows the connectivity of each server to the NMOS nodes.

unknown:

The topology is inactive (see Activating a Topology , on page 253) or the NMOS device does not have network connectivity to

the GV Orbit Client server(s).

reconnecting: The GV Orbit Client server is in the process of establishing communications with the NMOS device.

offline: The NMOS device does not have network connectivity to the

GV Orbit Client server(s).

online: The NMOS device is connected to the GV Orbit Client server(s).

Force Resync Device Set to make GV Orbit Client reload the NMOS device’s parameters from the NMOS registry.

399

Special Device Configuration Tasks

To add an NMOS device to a topology

GV Orbit Client Version 2.0.0

User Guide

Parameter

IS-05 Controllable

Description

This status shows whether the corresponding node in the NMOS registry has devices that support being controlled through IS-05

(connection management).

Yes: Routes to these devices should succeed.

No: If you try to route to a device that is not IS-05 controllable, the route will fail.

Partial: Some devices are controllable in this node, while others are not.

This is the NMOS device’s current URL and port number. NMOS Device URL

Ports and streams are automatically created using the values found in the registry, and they will automatically be updated whenever GV Orbit Client receives notifications of changes from the NMOS registry.

You can change the following NMOS device properties which will not be overwritten with values from the NMOS registry (the value you set for these properties will persist in GV Orbit

Client): Labels, Short labels, Descriptions, Network label, and Logical levels. See

Defining

Device Properties , on page 247.

400

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Using SDP Parameters to Take a Stream from a non-NMOS Device to an NMOS Device

In order to use IS-05 connection management, Session Description Protocol (SDP) information is required to be sent as part of the command. GV Orbit Client can create SDP type parameters that a receiving NMOS device requires in order to successfully complete a take made from devices that do not generate and publish their own information.

The SDP information is now generated by GV Orbit Client and is included in the connection management commands to allow discovered AMWA NMOS receivers to join nondiscovered senders, or source devices created within the GV Orbit Client client. This SDP information is not currently published to the AMWA NMOS registry.

Within GV Orbit Client, a number of default SDP parameter templates are built-in and are selected according to the stream’s Logical Level parameter. The SDP parameters can be tweaked if necessary as these SDP parameters must represent the current details and specifications of the source’s stream.

The following device bubbles support SDP parameters:

• IP Device

• GV Node

• IQ-family type IP devices, for example, IQMix, IQUCP25, IQAMD, MV-820-IP, Kahuna IP, and so on

• Audio Live

Related Topics

• The Stream Configurator allows you to configure the SDP template for streams on a large scale. See

Stream Configurator Tasks , on page 339.

PREREQUISITES: To customize the SDP parameter, you must know how to form a valid SDP.

This is beyond the scope of this document. For more information about SDP specific parameters, see RFC 4566 . See also SDP .

401

Special Device Configuration Tasks

Using SDP Parameters to Take a Stream from a non-NMOS Device to an NMOS Device

GV Orbit Client Version 2.0.0

User Guide

The SDP parameters are configured in the device’s Property Editor, under the Device Group

Properties tab and in the Device Properties

tab. See Defining Device Properties , on page 247 for more information about these tabs.

402

Certain SDP parameters have been enhanced with new GV Orbit Client variables which allows for better device control integration within GV Orbit Client. These variables are available for SDP parameters configured under the Device Group Properties and the

Device Properties tab, output stream property. Variables always start with a dollar sign ($) and are enclosed in curly brackets {} as shown in the example below.

See

Defining Device Properties , on page 247 to know more about how parameter values in

the Device Properties tab inherit their values from the corresponding parameter values in the Device Group Properties tab.

Example of SDP parameters used in GV Orbit Client

The following is a typical example of the SDP parameters used in GV Orbit Client. v=0 o=- ${sequence} 0 IN IP4 ${portIpAddress} s=grassvalley 1 t=0 0 a=recvonly a=ts-refclk:ptp=IEEE1588-2008:08-00-11-FF-FE-22-04-00:127 a=mediaclk:direct m=video ${streamPortNumber} RTP/AVP 98 c=IN IP4 ${streamIpAddress}/1 a=rtpmap:98 SMPTE2022-6/27000000

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Using SDP Parameters to Take a Stream from a non-NMOS Device to an NMOS Device

Special GV Orbit Client SDP Variables

The following table lists the supported special GV Orbit Client variables for use anywhere within the SDP parameter. These variables reference parameters that are configured elsewhere in GV Orbit Client, thereby automatically keeping stream information up-todate.

GV Orbit Client SDP

Variable

${audioBits}

${channelCount}

${clockSetting}

${sequence}

${packetTime}

${portIpAddress}

${streamIpAddress}

${streamPortNumber}

${redundantIpAddress}

${redundantPortNumber}

${redundantPortIpAddre ss}

${rtpPayloadType}

${samplingRate}

Description

The audio stream’s bit depth.

The number of (audio) channels.

The PTP master clock setting.

This SDP file’s ID

The length of time in milliseconds represented by the (audio) media in a packet.

The sending port’s IP address.

The source for this variable comes from the Port’s IP Address parameter for this stream.

The transmit (sending) stream’s multicast IP address.

The source for this variable comes from the stream’s IP Address parameter.

The transmit (sending) stream’s IP port number.

The source for this variable comes from the stream’s IP Port parameter.

The transmit (sending) stream’s redundant multicast IP address.

The source for this variable comes from the stream’s IP Address parameter used for the redundancy port. See the Redundancy

Port parameter to identify the current redundancy port.

The transmit (sending) stream’s redundant IP port number.

The source for this variable comes from the stream’s IP Port parameter used for the redundancy port. See the Redundancy

Port parameter to identify the current redundancy port.

The transmit (sending) stream’s redundant IP port number.

The source for this variable comes from the stream’s IP Address parameter used for the redundancy port. See the Redundancy

Port parameter to identify the current redundancy port.

The RTP payload type as defined by the SDP specification.

The audio stream’s sampling rate.

Editing SDP Parameters

Any of the above variables can be substituted with a fixed equivalent value so that it is hard coded. For example, the variable ${portIpAddress} represents a multicast IP address and it can be replaced with an IP address such as 230.1.1.1

When you edit any SDP parameter:

403

Special Device Configuration Tasks

Using SDP Parameters to Take a Stream from a non-NMOS Device to an NMOS Device

GV Orbit Client Version 2.0.0

User Guide

• The SDP becomes fixed and will no longer automatically update when you make a change elsewhere in the Property Editor. For example, changing the logical level parameter will not update the SDP parameters with the logical level change. You will have to further edit the SDP to adapt it to any such change.

• The SDP becomes orange to indicate that its default value has been overridden. See

Defining Device Properties , on page 247 to know more about how to reset a parameter

to its default value.

404

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring Cisco DCNM Network Switch Devices

Networks that use Cisco Data Center Network Manager (DCNM) to manage LAN fabric can be controlled by GV Orbit Client.

PREREQUISITES:

• DCNM build 11.0(1) or higher

• Switch’s firmware: NXOS 9.2(1) or higher for 9200, 9300-EX, and 9500-R switches.

• Switch’s BIOS: version 07.64, compile time: 05/17/2018

• Configure the required DCNM network switch’s flow policies. See below.

Configuring the Network Switch’s Flow Policies

If you are using a network switch with DCNM control port, flow policies must be manually set in the DCNM web interface, before you configure GV Orbit Client to use the network switch.

Each flow policy sets the maximum bandwidth that can be allocated to a type of traffic flow.

See the table below. Only the flow policies for bandwidths you will use in your network need to be created.

Each flow policy must have a multicast IP address range associated to it, according to your network addressing pattern, as GV Orbit Client uses a different multicast IP range for each type of traffic flow and bandwidth (audio, video 3G, Video HD, ANC / metadata, and so on).

Class D IP addresses are multicast addresses. By default, IP address 239.255.0.1 may be reserved for use by certain Grass Valley equipment for DDS discovery and should not be allocated for any other purpose.

Review documentation for all equipment you are going to use on your network for any specific IP addressing and bandwidth requirements.

Establish the Customer Multicast IP Addressing Pattern

All network IP devices must be assigned an IP address, and each network traffic type is assigned to a IP address range according to its bandwidth requirement.

For example, the following table shows a typical multicast IP addressing pattern and the bandwidth allocation required by traffic flow type.

Traffic Flow

Type

Video

Audio

Flow Policy

Typical IP address range

From To

Recommended

Bandwidth Allocation

SMPTE2022-6(3G) 230.1.1.1

230.255.255.255 3.2Gbps

SMPTE2022-6(HD) 229.1.1.1

229.255.255.255 1.601Gbps

SMPTE2022-6(SD) 228.1.1.1

228.255.255.255 0.27Gbps

SMPTE2110-20(3G) 238.1.1.1

238.255.255.255 2.703Gbps

SMPTE2110-20(HD) 237.1.1.1

237.255.255.255 1.401Gbps

SMPTE2110-20(SD) 236.1.1.1

236.255.255.255 0.23Gbps

SMPTE2110-30(AES) 234.1.1.1

234.255.255.255 61Mbps

405

Special Device Configuration Tasks

Configuring the Network Switch’s Flow Policies

GV Orbit Client Version 2.0.0

User Guide

Traffic Flow

Type

ANC

(metadata)

Default a

Flow Policy

Typical IP address range

From To

Recommended

Bandwidth Allocation

SMPTE2110-40(ANC) 235.1.1.1

235.255.255.255 2Mbps

* 150Kbps a.This allows any general network management data to pass through the network while guaranteeing that it will not take up any significant amount of total network bandwidth. When needed, this bandwidth allocation is also used for DDS discovery when such equipment uses a multicast address that is outside of any other pre-existing flow policy you have created (this must be the case).

Delete Pre-existing Flow Policies

If your switch has been previously configured, you may need to remove any pre-existing flow policies. These flow policies have the status Create under Deployment Action .

To delete pre-existing current flow policies

1 In the Deployment drop menu, select Undeploy All Custom Policies .

2 The Deployment Action column will show Delete instead of Create .

3 Select all flow policies from the list, but exclude the Default flow policy: do not remove the Default flow policy as it will be needed.

4 Use the delete (X) button to delete the selected flow policies.

Add New Flow Policies Using Your IP Addressing Pattern

According to the IP addressing pattern shown in the above table, create the new flow policies for each traffic flow type you are going to use.

406

GV Orbit Client Version 2.0.0

User Guide

To add new flow policies

1 Click New (+).

Special Device Configuration Tasks

Configuring the Network Switch’s Flow Policies

2 Set the parameters for the flow policy. The setting for QoS/DSCP is CS1 .

3 Click Deploy.

4 Repeat to create all necessary flow policies.

5 In the Deployment drop menu, select Deploy All Custom Policies .

The status under Deployment Action becomes Create and the Deployment Status becomes Success .

407

Special Device Configuration Tasks

Configuring a DCNM Network Switch Device

GV Orbit Client Version 2.0.0

User Guide

Configuring a DCNM Network Switch Device

To configure a DCNM Network Switch Device

1 Add the Network Switch device to the Topology: from the Device Library , Virtual

Device, find the Network Switch device bubble. See

To add a Virtual Device to a topology , on page 224.

2 Click on the name of the device underneath the bubble to enter a meaningful name to identify this device in the Name

field. See To name a device and set the number of devices in the group , on page 225.

These parameters can also be set in the Property Editor .

3 Set the number of physical input and output connectors being used on the network switch in # Input Connectors and # Output Connectors . See

Defining Device

Properties , on page 247 for more information.

408

The configuration for these ports become available as Ports under IN and OUT .

4 Click New next to Control Ports at the top of the Property Editor and select Cisco

DCNM from the list. Dummy Network Switch should be used when the DCNM network

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a DCNM Network Switch Device manager is not being used for the network switch. See

Defining Device Properties , on page 247 for more information.

The Cisco DCNM tab appears. To remove the control port, click Delete.

5 Select Cisco DCNM tab (next to Control Port at the top of the Property Editor ) to configure the Device Properties in the Property Editor . Only the properties shown

below should be used. See also Description of Common Device Properties , on page 348.

Parameter Description

Network Host Name This is the unique name by which the Network Switch is identified within GV Orbit Client. This value is used to construct the input/output port labels.

Cisco DCNM Control Port parameters

Virtual IP Address

Exclusive Policy

Control

Enabled

Username

Password

This is the virtual IP address to communicate with DCNM cluster. This

IP is used to address any active member of the two nodes that are operating in High Availability (HA) mode. If DCNM is not operating in

HA mode, use the DCNM node IP address.

When set, GV Orbit Client operates in exclusive mode: any change to the host aliases, host policies or flow policies (through DCNM web interface for example) will be overwritten and restored by GV Orbit

Client. This is the supported mode to be used.

Only deselect this parameter under the guidance of Grass Valley

Technical Support.

When set, GV Orbit Client controls the switch.

When deselected, GV Orbit Client no longer controls the switch, thus allowing you to perform maintenance operations on the switch. When re-establishing control (set Enabled ), GV Orbit Client will push the current policies to the switch.

Set the administrator’s username to access the DCNM network.

Set the administrator’s password to access the DCNM network.

409

Special Device Configuration Tasks

Configuring a DCNM Network Switch Device

GV Orbit Client Version 2.0.0

User Guide

Parameter Description

Connection State 1 / 2 This shows the current connection state to the switch. When a redundant configuration is used (two GV Orbit Client servers form a cluster) Connection State 1 and Connection State 2 shows the connectivity of each server to the switches.

Unknown: The Virtual IP is not configured yet or the topology is inactive.

Online: GV Orbit Client is connected to DCNM.

Offline: The topology is active and GV Orbit Client is unable to communicate with DCNM.

Reconnecting: GV Orbit Client is trying to reach DCNM.

Active Host Name

Active IP Address

Standby Host Name

Standby IP Address

In a redundant High Availability network architecture, one node (in standby mode) provides failover protection to another node (currently active).

Host Name : The hostname is the unique name by which the active / standby node is known on the network.

IP Address : The network IP address for the active / standby node.

6 Do not configure any parameters found under Ports or Streams. These are shown for information purposes only.

7 Add IP devices to the topology and then connect them to the switch: Click Quick

Connect to link the devices. See

Using Quick Connect to Link all Devices in a Topology , on page 239. See also Methods to Link Devices in a Topology , on page 239.

To support network redundancy for use with SMPTE ST 2022-7 compatible equipment, see

Configuring Network Switch Redundancy to Support SMPTE ST 2022 7 , on page 415.

Use the Path Manager to view and troubleshoot the flow of streams through the switch fabric. See

Configuring Cisco DCNM Network Switch Devices , on page 405.

410

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Direct Flow Orchestration: How To Create a Static Flow with a Cisco Network Switch

Direct Flow Orchestration: How To Create a Static Flow with a Cisco

Network Switch

This topic describes the use case where a destination IP device does not have an API exposed that allows GV Orbit Client to direct the device’s receivers to join send streams. Or you want to control what is to be sent to an IP destination. For this, GV Orbit Client can control the egress ports of a network switch to statically stitch flows feeding the IP device. It is also necessary to remove the network interface ports from the available resources for dynamically stitching flows via IGMP joins. Another way of stating this, it is necessary to remove these paths from the available tielines.

To create a static flow with GV Orbit Client you need to set some information on an output port of a network switch with a DCNM control port.

1 For this procedure the following topology will be used. See

Adding Devices to a

Topology , on page 224.

2 In the Network Switch’s Property Editor , under Control Ports , select an output port on your network switch (for example, Cisco DCNM ). This port should not be connected to anything. See

3 Set the number of streams you need in #Output Connectors .

4 With the Cisco DCNM control port selected, set Expose Streams .

5 Set the name and IP address of the network switch’s control port ( Cisco DCNM ). You find this information through the Inventory page on the DCNM web UI. ( Inventory ,

Switches , Select a leaf , Interfaces tab). You have to add 1 to the last number of the IP. For example: 192.102.45.0/31 becomes 192.102.45.1.

6 On the port's streams, set the Logical Level . See

Configuring the Logical Levels for the

Devices in a Topology , on page 217.

7 On the port's streams, set Automatic Destination if you do not want to create a logical destination yourself.

8 To create the static flow, you need to do a normal take from the streams (or logical destination if you created one) to the source you want.

9 To confirm if the flow is passing, you can check the flow status page on the DCNM UI

( Media Controller , Flow status ). Note: If the static flow was created but the source does not have a signal, there will be no feedback.

To delete a static flow, you need to do a take from the destination to a source with an IP of

0.0.0.0 on the streams.

411

Special Device Configuration Tasks

Configuring a GV Fabric Network Switch Device

GV Orbit Client Version 2.0.0

User Guide

Configuring a GV Fabric Network Switch Device

GV Fabric is an IP switch enabling format agnostic signal routing for small to enterprisewide installations. GV Orbit Client automatically discovers and configures any GV Fabric switch found by the GV Orbit Automatic Network Configurator service (see Automatic

Network Configurator Service in the GV Orbit Admin Guide ; see Related Documentation , on page 19). When this service finds a GV Fabric network switch on the network, or when you factory-reset an existing GV Fabric network switch, the service uses Zero Touch

Provisioning (ZTP) to automatically configure the GV Fabric network switch to optimize its configuration to forward media traffic. Once the initial configuration of the GV Fabric switch is done, the GV Fabric switch becomes available as a discovered device in the Device

Library .

GV Orbit Client also monitors the switch and updates the configuration as required. For example, the switch’s media Ethernet interfaces are automatically assigned as members of the MEDIA_VLAN and configured for use.

LIMITATION: You must manually configure an interface breakout by using the GV Fabric

Command Line Interface (CLI).

To configure a GV Fabric Network Switch Device

1 Add the GV Fabric Network Switch device to the Topology: from the Device Library ,

Discovered , find the GV Fabric Network Switch device bubble that you want to use. See

To add a Discovered Device to a Topology , on page 227.

412

2 Select Device Properties and select GV Fabric

. See Defining Device Properties , on page 247 for more information.

3 Select GV Fabric tab (next to Control Port at the top of the Property Editor ) to configure the Device Properties in the Property Editor . Only the properties shown

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a GV Fabric Network Switch Device

below should be used. See also Description of Common Device Properties , on page 348.

Parameter Description

Network Host Name This is the unique name by which the Network Switch is identified within GV Orbit Client. This value is used to construct the input/output port labels.

GV Fabric Control Port parameters

Name

MGT0 / MGT1 IP

Address

Username

Once GV Orbit Client connects to the switch, the switch’s name is read from the switch’s configuration.

Once GV Orbit Client connects to the switch, the switch’s management

IP addresses are read from the switch’s configuration.

Password

The Zero-Touch Provisioning (ZTP) process creates a gvapi user account in the switch. By default, GV Orbit Control uses the gvapi user account to access the switch.

The username field can be customized to use another switch user account. Such a user account’s capability must be Monitor or higher.

See GV Fabric documentation to create a new user on the switch.

Set the administrator’s password for GV Orbit Control to access the

GV Fabric switch’s user account.

When the GV Fabric device is added to the topology, the password for the gvapi user account is preset.

413

Special Device Configuration Tasks

Configuring a GV Fabric Network Switch Device

GV Orbit Client Version 2.0.0

User Guide

Parameter Description

Unknown: The Virtual IP is not configured yet or the topology is inactive.

Online: GV Orbit Client is connected to DCNM.

Offline: The topology is active and GV Orbit Client is unable to communicate with DCNM.

Reconnecting: GV Orbit Client is trying to reach DCNM.

4 Do not configure any parameters found under Ports or Streams. These are shown for information purposes only.

5 Add IP devices to the topology and then connect them to the GV Fabric switch: Click

Quick Connect to link the devices. See

Using Quick Connect to Link all Devices in a

Topology , on page 239. See also Methods to Link Devices in a Topology , on page 239.

To support network redundancy for use with SMPTE ST 2022-7 compatible equipment, see

Configuring Network Switch Redundancy to Support SMPTE ST 2022 7 , on page 415.

Use the Path Manager to view and troubleshoot the flow of streams through the switch fabric. See

Configuring a GV Node Device , on page 349.

414

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring Network Switch Redundancy to Support SMPTE ST 2022 7

Configuring Network Switch Redundancy to Support SMPTE

ST 2022

7

This topic describes the theory of how to implement network redundancy, and as such, information is provided as an example that can be used for any SMPTE ST 2022-7 compatible equipment.

To make streaming more reliable over an IP network, the implementation of SMPTE

ST 2022-7 seamless protection switching depends on stream redundancy. This protection scheme transmits two identical packet streams over physically separate network routes

(shown as Red LAN and Blue LAN in the figure below), so that if packets from one network are lost or delayed, the data can be reconstructed using packets from the second network stream. This process is seamless because switching between the streams is instantaneous and does not impact content.

Network

Switch ‘Red’

Red LAN

IPG-4901 A

GV Node A IPG-3901 A

GV Node B IPG-3901 B

IPG-4901 B

Blue LAN

Network

Switch ‘Blue’

PREREQUISITES:

• At least two DCNM-compliant switches must be used for this application. Contact Grass

Valley for more information about switch compatibility. See Grass Valley Technical

Support , on page 288.

415

Special Device Configuration Tasks

Configuring Network Switch Redundancy to Support SMPTE ST 2022 7

GV Orbit Client Version 2.0.0

User Guide

• For any GV Node frame: a In iControl’s GV Node Manager, make sure to set redundancy to ON. See the GV

Node User Manual for more information. b In GV Orbit Client, set 2022-7 Mode and configure the Redundancy Port parameter.

See

• For any IPG-4901 / IPG-3901 card a In iControl’s Network panel , Settings tab, for the ETH 2 Port , make sure to set the

Operation Mode to Redundancy . See the IPG-4901 Guide to Installation and

Operation for more information.

b In GV Orbit Client, set the Operation Mode to Redundancy . See

Configuring an

IPG 3901 / IPG 4901 Device , on page 360.

• For certain third-party devices you may have to configure port redundancy manually.

See

Setting Port Redundancy for Many Devices at Once , on page 237.

To configure SMPTE ST 2022-7 example

1 Add the following devices to the Topology: from the Device Library , Virtual Device , add the following device bubbles to the Topology. See

To add a Virtual Device to a topology , on page 224.

Quantity

2  3 instances in a group

Device

Network Switch

IPG-3901

Camera

Monitor

416

GV Orbit Client Version 2.0.0

User Guide

Arrange the devices on the Topology as shown below.

Special Device Configuration Tasks

Configuring Network Switch Redundancy to Support SMPTE ST 2022 7

2 Activate the topology. See Activating a Topology , on page 253.

3 Configure the devices on the Topology. See

Special Devices , on page 347. For any other

device, see

Adding Devices to a Topology , on page 224.

417

Special Device Configuration Tasks

Configuring Network Switch Redundancy to Support SMPTE ST 2022 7

GV Orbit Client Version 2.0.0

User Guide

4 Click Quick Connect to link the devices as shown below. See

Using Quick Connect to

Link all Devices in a Topology , on page 239. See also Methods to Link Devices in a

Topology , on page 239.

2 8

1 10

3 9

Much more elaborate systems can be configured. The objective is to connect all SMPTE

ST 2022-7 IP devices (#2 to #9) to both network switches (RED and BLUE).

5 If you are manually making the connections between the devices, select the links between devices, one at a time, to make the connections between devices as shown below. See

Manually Setting the Link’s Physical Connection Parameters (Sources and

Destinations) , on page 243. If you use Quick Connect, this is not necessary.

Link

# From

1 Camera

2 IPG-3901

3 IPG-3901

IPG-3901

Network Switch

RED

Network Switch

BLUE

IPG-3901

Make the following connections

From To

Cam1

Cam2

Cam3

ETH1

SDI to 1 (Input Port Id: 3)

SDI to 2 (Input Port Id: 4)

SDI to 3 (Input Port Id: 5)

SwitchIn1

ETH2

SwitchOut1

SwitchIn1

ETH1 4 Network Switch

RED

5 Network Switch

BLUE

6 IPG-3901-A

IPG-3901

Network Switch

RED

SwitchOut1

ETH1

ETH2

SwitchIn2

418

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring Network Switch Redundancy to Support SMPTE ST 2022 7

Link

# From

7 IPG-3901-A

Network Switch

BLUE

IPG-3901-A

Make the following connections

From

ETH2

SwitchIn2

SwitchOut2 ETH1 8 Network Switch

RED

9 Network Switch

BLUE

10 IPG-3901

IPG-3901-A

Camera

SwitchOut2

SDI to 1 (Output Port Id: 3)

SDI to 2 (Output Port Id: 4)

SDI to 3 (Output Port Id: 5)

ETH2

Mon1

Mon2

Mon3

419

Special Device Configuration Tasks

Configuring an NVISION Hybrid Series Router

GV Orbit Client Version 2.0.0

User Guide

Configuring an NVISION Hybrid Series Router

To control an NVISION Hybrid Series Router, GV Orbit Control uses the NP0016 router control protocol. The following NVISION Hybrid Routers are supported: NV8140, NV8144,

NV8280, NV8576 or NV8576 Plus. Once the IP address(es) have been added to the Control

Port(s) that connects to the NVISION Hybrid Series Router, the router’s configuration is read into GV Orbit Control, and the router’s card types and ports are automatically configured within GV Orbit Control.

PREREQUISITE: You must have a list of the card type for each slot in the router’s frame. This information may be available in the router’s MRC configuration software.

LIMITATIONS:

• The disembedder / embedder output card is currently not supported.

• The following topology use case is unsupported.

The tieline between two NVISION Hybrid Routers should not be MADI (for example, to link between a MADI source and a MADI destination). Taking a MADI source to a MADI destination will only work if both of them are directly connected to the same NVISION

Hybrid Series Router.

• The following topology use case does not support lock and protect from a third-party control system on the NVISION Hybrid Router for a Logical Destination.

Any output of a NVISION Hybrid Router that is connected to another router cannot be locked in GV Orbit Control. GV Orbit Control will only update the lock/protect status of a destination which is directly connected to the NVISION Hybrid Router (that is, without any other devices in-between).

420

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring an NVISION Hybrid Series Router

To configure an NVISION Hybrid Series Router Device

1 Add the NV Hybrid Router device to the Topology: from the Device Library , Virtual

Device , find the NV Hybrid Router

device bubble. See To add a Virtual Device to a topology , on page 224.

2 The control port(s) must be configured to allow communication with the router thereby permitting GV Orbit Client to control the router. NVISION Hybrid Series Routers are controlled through the NP0016 router control protocol.

Select the NV Hybrid Router bubble and click New next to Control Port at the top of the Property Editor and select the router’s control protocol from the list. Dummy can be used for testing purposes (or pre-deployment) when the actual router model is unknown. See also

Defining Device Properties , on page 247 for more information.

A tab for the selected router model appears. Select this tab to configure the control port.

If the router has a second redundant network connection for controlling it, add a second control port and configure it the same way as the first one except for the IP address which must reflect that of the router’s second network connection.

Specifically, you must set the router’s control port IP Address and IP Port number parameters.

Router Control Protocol See

NP0016 Compact Router

NP0016 Compact Router Control Port Configuration Parameters , on page 431

NP0016 Enterprise Router

NP0016 Enterprise Router Control Port Configuration Parameters , on page 431

To delete a control port, see

To delete a router’s control port , on page 430.

3 Activate the topology. See Activating a Topology , on page 253.

421

Special Device Configuration Tasks

Configuring an NVISION Hybrid Series Router

GV Orbit Client Version 2.0.0

User Guide

The Connection State 1 / 2 status for the control port(s) becomes Online when is has successfully connected to the NVISION Hybrid router.

Once GV Orbit Client has connected to the NVISION Hybrid Router through the Control

Port, it reads the router’s configuration to then automatically configure the NVISION

Hybrid Router device properties in GV Orbit Client accordingly. Should the NVISION

Hybrid router’s configuration change (for example, changes have been made to the type and slot location of the router’s cards), the router’s configuration can be re-loaded

into GV Orbit Client; see To automatically refresh the NVISION Hybrid router’s card information in GV Orbit Client , on page 425.

4 Deactivate the topology. See

Making an Active Topology Inactive , on page 254.

5 Configure the NVISION Hybrid Series Router properties. See also

To automatically refresh the NVISION Hybrid router’s card information in GV

Parameter Description

Network Host Name The hostname is the unique name by which the associated NVISION

Hybrid Series Router is known on the network.

Audio Physical Level

Video Physical Level

From the NVISION Hybrid Series Router’s configuration, specify the level ID number that has been assigned to the router’s audio matrix.

Usually this is 2.

From the NVISION Hybrid Series Router’s configuration, specify the level ID number that has been assigned to the router’s video matrix.

Usually this is 1.

NVision Hybrid Router

Type

Advanced > Internal

Wiring Done

Shows the router’s model type. This is automatically read from the router.

Shows if the internal modeling of the NVISION Hybrid Router is complete.

6 This step is optional; setting the Card Type for each slot in the router’s frame can automatically be done by GV Orbit Client: To automatically update GV Orbit Client’s configuration when the type and slot location of the cards have been changed in the router, see

Orbit Client , on page 425.

Manually set the router’s card type for any of the router’s input and output slots that need to be updated: select an Input Slot or Output Slot in the router’s frame in the

422

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring an NVISION Hybrid Series Router

Property Editor and then set the card type in the Card Type parameter. If the slot has no card installed in it, set the Card Type parameter to NONE .

423

Special Device Configuration Tasks

Configuring an NVISION Hybrid Series Router

GV Orbit Client Version 2.0.0

7 Select each input or output port to configure them individually. These are the configuration parameters for each of the router’s input/output ports. See also

Description of Common Device Properties , on page 348.

User Guide

424

Parameter

Port Identifier

Number

Description

This is the generic identifier of the port within GV Orbit Client.

This shows the current status for information purposes.

Direction

Connector Type

Capacity (bps)

Bandwidth Usage

(bps)

The stream’s data rate.

This shows the current status for information purposes.

Embedder bypassed Shows the current embedder status for the selected output port according to the current path being routed. See also

Path Manager

Tasks , on page 448.

When set, the output embedder is not being used.

When deselected, the output embedder is being used.

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring an NVISION Hybrid Series Router

8 Select each steam found under each input and output port to configure them individually. These are the configuration parameters for the individual streams carried on a network port. See also

Description of Common Device Properties , on page 348.

To automatically refresh the NVISION Hybrid router’s card information in GV Orbit Client

When the router has been reconfigured with new or different cards, GV Orbit Client can read the router’s configuration again to automatically configure the NVISION Hybrid Router device properties in GV Orbit Client accordingly.

1 De-activate the topology if activated. See

Making an Active Topology Inactive , on page 254.

2 Select one of the router’s control ports.

3 Scroll-down the router’s Device Properties list to the control port.

4 Click Update Slotted Cards and then click OK .

GV Orbit Client reads the router’s configuration to then automatically configure the

NVISION Hybrid Router device properties in GV Orbit Client accordingly.

5 Activate the topology. See Activating a Topology , on page 253.

425

Special Device Configuration Tasks

Configuring Router Devices

GV Orbit Client Version 2.0.0

User Guide

Configuring Router Devices

The following procedure configures a router device. Different models of routers use a range of control protocols that GV Orbit Client uses to control the router. Each router control protocol is individually covered in follow up procedures: see also

Configuring a Router’s

Control Port , on page 429.

For more information about how GV Orbit Control manages a router’s Lock, Protect, and

Release, see also

About Lock, Protect, and Release , on page 468.

To configure a Router Device

1 Add the Router device to the Topology: from the Device Library , Virtual Devices , find the Router Device

bubble. See To add a Virtual Device to a topology , on page 224.

2 Add and configure router control port(s) according to the router model you want to control. Control port(s) must be configured to allow communication with the router thereby permitting GV Orbit Client to control the router; see

Configuring a Router’s

Control Port , on page 429.

3 Select the router’s tab (next to Control Port at the top of the Property Editor ) to configure the Device Properties in the Property Editor

. See also Description of

Description of Common Device Properties , on page 348.

Parameter

Physical Level ID

Description

Network Host Name The hostname is the unique name by which the associated router is known on the network.

Set the Physical Level ID value that has been configured for the corresponding router to be controlled by this device instance. To obtain this value, use the router’s native configuration interface.

Advanced > Default

Connector Type

Controller Starting

Input

The router’s physical interface port connector: HD/SDI , IP/RJ-45 ,

MADI .

The starting input port number from which you want to control the router’s physical level.

Controller Starting

Output

The starting output port number from which you want to control the router’s physical level.

426

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring Router Devices

4 Set the number of physical input and output connectors being used on the router in #

Input Connectors and # Output Connectors .

The configuration for these ports become available as Ports under IN and OUT .

427

Special Device Configuration Tasks

Configuring Router Devices

GV Orbit Client Version 2.0.0

5 Select each input or output port to configure them individually. These are the configuration parameters for each of the router’s input/output ports. See also

User Guide

428

Parameter

Port Identifier

Number

Direction

Connector Type

Capacity (bps)

Bandwidth Usage

(bps)

IP Address

Redundancy Port

Description

This is the generic identifier of the port within GV Orbit Client.

This shows the current status for information purposes.

The stream’s data rate.

This shows the current status for information purposes.

This is the interface IP address of the selected port. This is currently not used in the router virtual device.

Associate this port with another port to create a redundant network traffic flow path for failover protection. The associated port will not be available to carry other traffic.

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a Router’s Control Port

6 Select each steam found under each input and output port to configure them individually. These are the configuration parameters for the individual streams carried on a network port. See also

Description of Common Device Properties , on page 348.

Configuring a Router’s Control Port

Control port(s) must be configured to allow communication with the router thereby permitting GV Orbit Client to control the router. There are many types of control ports suited to the router’s individual model or control protocol. First, you must add a control port to the router’s configuration in GV Orbit Client and then configure it.

PREREQUISITE: Add a router device to the Topology Configurator. See To configure a Router

Device , on page 426.

To add a router control port

1 Select the Router bubble on the Topology Configurator and then select Device

Properties and click New next to Control Port at the top of the Property Editor and select the router’s model / control protocol from the list. Dummy can be used for testing purposes (or pre-deployment) when the actual router model is unknown. See also

Defining Device Properties , on page 247 for more information.

A tab for the selected router model appears. Select this tab to configure the control port. The control port(s) must be configured to allow communication with the router thereby permitting GV Orbit Client to control the router.

2 Configure the control port. See below.

429

Special Device Configuration Tasks

Configuring a Router’s Control Port

GV Orbit Client Version 2.0.0

User Guide

To delete a router’s control port

Delete a router’s control port as follows.

1 De-activate the topology if activated. See

Making an Active Topology Inactive , on page 254.

2 Select one of the router’s control ports.

3 Scroll-down the router’s Device Properties list to the control port

430

4 Click Delete .

Supported router control protocols

The following router control protocols are supported.

Router Control Protocol See

NP0016 Compact Router

NP0016 Compact Router Control Port Configuration Parameters , on page 431

NP0016 Enterprise Router

NP0016 Enterprise Router Control Port Configuration Parameters , on page 431

NS-BUS

NV9000 TCP/IP (NP0017 device-based)

SAM SW-P-08 TCP/IP

NS-BUS Control Port Configuration Parameters

page 435

, on page 434

NV9000 TCP/IP Control Port Configuration Parameters , on page 434

SAM SW-P-08 TCP/IP Control Port Configuration Parameters , on

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a Router’s Control Port

NP0016 Compact Router Control Port Configuration Parameters

Parameter

IP Address

Connection State 1

Connection State 2

Connections From

Multiple Servers

IP Port

In router Lock/Protect enabled

Description

The network IP address for the associated router’s management or control port Ethernet address.

Connection State 1 shows the connection status of the router with the primary server of a server group.

Connection State 2 shows the connection status of the router with the secondary server of a server group. See

Activating a Topology , on page 253) or the router does not have network connectivity to the GV

unknown: The topology is inactive (see

Orbit Client server(s).

offline: The router does not have network connectivity to the GV Orbit

Client server(s).

online: The router is connected to the GV Orbit Client server(s).

Set this if the router supports multiple concurrent connections to it.

When set, this allows GV Orbit Client main and backup servers to connect at the same time to the router, thereby increasing system availability.

Port number for the control port stream used by the router. The default is 5194.

Set to transfer the management of Locks/Protects from the GV Orbit

Control control system to the Router for destinations that are directly connected to this router.

Deselect to manage all Lock/Protect in GV Orbit Control exclusively.

See

About In router Lock/Protect enabled for a Router using NP0016 router control protocol , on page 433.

NP0016 Enterprise Router Control Port Configuration Parameters

The enterprise router control port supports the protocol's 'Coherent take' command when

performing multiple crosspoint changes at the same time. See also Description of Common

Parameter

IP Address

Description

The network IP address for the associated router’s management or control port Ethernet address.

431

Special Device Configuration Tasks

Configuring a Router’s Control Port

GV Orbit Client Version 2.0.0

User Guide

Parameter

Connection State 1

Connection State 2

Connections From

Multiple Servers

IP Port

In router Lock/Protect enabled

Use Coherent Take

Message

Description

Connection State 1 shows the connection status of the router with the primary server of a server group.

Connection State 2 shows the connection status of the router with the secondary server of a server group. See

The topology is inactive (see Activating a Topology , on page 253) or the router does not have network connectivity to the GV

unknown:

Orbit Client server(s).

offline: The router does not have network connectivity to the GV Orbit

Client server(s).

online: The router is connected to the GV Orbit Client server(s).

Set this if the router supports multiple concurrent connections to it.

When set, this allows GV Orbit Client main and backup servers to connect at the same time to the router, thereby increasing system availability.

Port number for the control port stream used by the router. The default is 5194.

Set to transfer the management of Locks/Protects from the GV Orbit

Control control system to the Router for destinations that are directly connected to this router.

Deselect to manage all Lock/Protect in GV Orbit Control exclusively.

See

About In router Lock/Protect enabled for a Router using NP0016 router control protocol , on page 433.

Set for GV Orbit Client to use the protocol's 'Coherent take' command when performing multiple crosspoint changes at the same time for this router.

432

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a Router’s Control Port

About In router Lock/Protect enabled for a Router using NP0016 router control protocol

For a router using the NP0016 router control protocol, Lock, Protect, and Release have different behaviors depending on whether the In router Lock/Protect enabled parameter is set in the Router Control Port configuration.

In router

Lock/Protect enabled parameter Description

Set For destinations that are directly attached to the router, this setting transfers the management of Locks/Protects from the GV Orbit Control control system to this router, thereby allowing better third-party router control integration with GV Orbit Control. This is called in router lock and protect.

This setting keeps the router’s Lock/Protect and GV Orbit Control’s

Lock/Protect in synchronization as follows:

• If a Lock/Protect is updated in the router, it's also updated in GV Orbit

Control.

• If a Lock/Protect is updated in GV Orbit Control, it's also updated in the router.

This option has the following effects and consequences: When locks / protections are created in the router through another control system, the user name used to create the locks / protections will be unknown to GV Orbit Control’s user management mechanism. These unknown users are treated as admin users within GV Orbit Control. Note that admin users within GV Orbit Control can override the locks and protections of any other GV Orbit Control user. This means that any third-party control system will override locks / protections made in

GV Orbit Control.

Deselected GV Orbit Client stores the locks in its database and they are preserved after a restart/reboot. As such, destinations will remain locked/protected. GV Orbit Client system does not read a lock from a router and does not control a lock in the router. This is called in control system lock and protect. This is how all other types of routers are managed.

Locks and protections are made in GV Orbit Control without consideration of any locks and protections that have been made through another control system (locks and protections are not synchronized between GV Orbit Control and the router). This can result in unexpected routing behavior such as a failed path that looks as though it should have been successful.

433

Special Device Configuration Tasks

Configuring a Router’s Control Port

GV Orbit Client Version 2.0.0

User Guide

NS-BUS Control Port Configuration Parameters

Parameter

Connection State 1

Connection State 2

IP Address

IP Port

Multiple Connections

Capable

Description

Connection State 1 shows the connection status of the router with the primary server of a server group.

Connection State 2 shows the connection status of the router with the secondary server of a server group. See

The topology is inactive (see Activating a Topology , on page 253) or the router does not have network connectivity to the GV

unknown:

Orbit Client server(s).

offline: The router does not have network connectivity to the GV Orbit

Client server(s).

online: The router is connected to the GV Orbit Client server(s).

The network IP address for the associated router’s management or control port Ethernet address.

Port number for the control port stream used by the router. The default is 37800.

Set this if the router supports multiple concurrent connections to it.

When set, this allows GV Orbit Client main and backup servers to connect at the same time to the router, thereby increasing system availability.

NV9000 TCP/IP Control Port Configuration Parameters

This option uses the NP0017 device-based router control protocol to control an NV9000 router through Ethernet network link(s). If the router has two control ports, add a second

control port, one for each control port on the router. See also Description of Common

Parameter

IP Address

Connection State 1

Connection State 2

Description

The network IP address for the associated router’s management or control port Ethernet address.

Connection State 1 shows the connection status of the router with the primary server of a server group.

Connection State 2 shows the connection status of the router with the secondary server of a server group. See

The topology is inactive (see Activating a Topology , on page 253) or the router does not have network connectivity to the GV

unknown:

Orbit Client server(s).

offline: The router does not have network connectivity to the GV Orbit

Client server(s).

online: The router is connected to the GV Orbit Client server(s).

434

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a Router’s Control Port

Parameter

Connections From

Multiple Servers

IP Port

Protocol

Description

Set this if the router supports multiple concurrent connections to it.

When set, this allows GV Orbit Client main and backup servers to connect at the same time to the router, thereby increasing system availability.

Port number for the control port stream used by the router.

The IP connection protocol.

TCP: A point-to-point connection protocol.

UDP: A stateless connection protocol that can also broadcast data to more than one device.

Lock, Protect, and Release with the NV9000 Control Port

GV Orbit Control stores the locks in its database and they are preserved after a restart/reboot. As such, destinations will remain locked/protected. The GV Orbit Control system does not read a lock from a router and does not control a lock in the router.

SAM SW-P-08 TCP/IP Control Port Configuration Parameters

Grass Valley/Pro Bel devices including the Sirius router that use the Pro Bel SW-P-08 switcher protocol can be controlled by GV Orbit Client through an IP network. These routers use two control ports to control them.

LIMITATION: GV Orbit Client control of a Sirius router is limited to a maximum of 1152

2 crosspoints using single-level X-Y control.

To connect the GV Orbit Client server to the router

1 Add two control ports in GV Orbit Client. See To add a router control port , on page 429.

2 Configure both control port configuration parameters. See also

Parameter

IP Address

Connection State 1

Connection State 2

Description

The network IP address for the associated router’s management or control port Ethernet address.

Connection State 1 shows the connection status of the router with the primary server of a server group.

Connection State 2 shows the connection status of the router with the secondary server of a server group. See

The topology is inactive (see Activating a Topology , on page 253) or the router does not have network connectivity to the GV

unknown:

Orbit Client server(s).

offline: The router does not have network connectivity to the GV Orbit

Client server(s).

online: The router is connected to the GV Orbit Client server(s).

435

Special Device Configuration Tasks

Configuring a Router’s Control Port

GV Orbit Client Version 2.0.0

User Guide

Parameter

Connections From

Multiple Servers

Description

Set this if the router supports multiple concurrent connections to it.

When set, this allows GV Orbit Client main and backup servers to connect at the same time to the router, thereby increasing system availability.

IP Port

Matrix ID

Port number for the control port stream used by the router. The default is 14000.

A SW-P-08 device can have multiple matrices, each with multiple physical levels. Set the Matrix ID value that has been configured for the corresponding router to be controlled by this device instance. To obtain this value, use the router’s native configuration interface.

Refer to your router’s documentation for more information about this parameter.

Set this to poll the crosspoint status at regular intervals.

Polling

Protocol The IP connection protocol.

TCP: A point-to-point connection protocol.

UDP: A stateless connection protocol that can also broadcast data to more than one device.

Use Extended Mode Set this for GV Orbit Client to try to use the extended command set of the SW-P-08 protocol with the router first. Extended commands allow routers larger than 1023  1023 to be controlled. If the router does not support extended commands, the GV Orbit Client will fallback to the standard command set and with it, the associated control limitations.

436

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Configuring a Device that Supports Audio Breakaway/Shuffling such as Audio Live

Audio breakaway and shuffling can be done by Audio Live and by GV Node. Audio Live is designed specifically for audio processing.

About Audio Live

Input Streams

Audio Live is an IP-only device that manages audio feeds only. It accepts a number of AES67 streams as inputs. Internally, it demultiplexes these inputs to obtain a series of mono PCM audio channels which then go through an audio router. Outputs from the router get multiplexed in accordance with the required output configuration. This allows Audio Live to perform breakaway and/or shuffling of mono channel audio feeds, in addition to audio format conversion.

Demultiplexers Multiplexers Output Streams

Channel 1

Channel 2

Channel 1

Channel 2

AES

Stream

Channel 16

Channel 1

Channel 2

AES

Stream

AES

Stream

Channel 16 32 32 Channel 32

Internal Audio Matrix

2048 × 2048

2017

2018

Channel 1

Channel 2

Channel 1

Channel 2

2031

2032

AES

Stream

AES

Stream

Channel 16 2048 2048 Channel 32

Example Audio Live configuration with 128  16 matrix for the input and 64  32 matrix for the output

The inputs and outputs of an Audio Live are called spigots . There are a variety of spigot configurations that are available. See also

How to Know if a Spigot is an Input or an Output , on page 370.

GV Orbit Client is able to detect the number of channels in the input spigots and will assign one of the AES67 levels to the input stream for each spigot (for example, AES67-4, AES67-8,

AES67-16, AES67-32 or AES67-64). This is conditional on having configured the input spigots in GV Orbit Client to not use the Auto setting for the number channels. This is shown in the procedure below (

Required Audio Live Configuration in the GV Orbit Client

Control Panel , on page 438).

437

Special Device Configuration Tasks

About the Routing Path of Audio Channels

GV Orbit Client Version 2.0.0

User Guide

GV Orbit Client will detect the number of channels in the output spigots and one of the

AES67 logical levels will be automatically assigned to the output stream of each output spigot (for example, AES67-4, AES67-8, AES67-16, AES67-32 or AES67-64).

Audio Live can accept audio packets with any packet time on the input. Audio Live can convert audio packet times as well as the number of channels in the streams. For example, an input spigot accepts an AES67 stream with 8 channels and packet time of 1 millisecond, and route the signals to an output spigot with 16 channels and packet time of 250 microseconds. When using audio streams with different packet times however, extra configuration steps are required: see

Required Configuration for Audio Streams with

Different Packet Times , on page 441.

About the Routing Path of Audio Channels

If there are multiple devices on the topology that can perform audio shuffling, Audio Live will not necessarily always do the shuffle. For example, if the first device reached along the path (from destination to source) is a GV Node, then the GV Node may do the shuffle. It is

GV Orbit Client that determines whether and when Audio Live is required for a given route.

To know if an Audio Live or GV Node device is currently in use for a given route, use the Path

Manager to see if there are tie-line connections to the Audio Live / GV Node device. See

Logical Level Editor Tasks

Prerequisites

Audio Live v1.5 or higher must be connected to the network, licensed, and has been previously configured with GV Orbit Client.

Required Audio Live Configuration in the GV Orbit Client Control Panel

In the Audio Live User Guide , see the following topics that must be configured according to your needs.

1 In GV Orbit Client, set the size of Audio Live’s audio matrix ( Maximum Supported

Channel Count ) and the number of channels per AES input and output streams. This setting is found under Audio Live > Setup > System Configuration > Input

Configuration and Output Configuration .

2 Stop the Audio Live server in Agent Configuration ; under Available Agents , select

Audio Live and click Stop .

438

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Prerequisites

3 Once the Status under Selected Agent becomes Stopped , click Start .

4 In GV Orbit Client, set the Channels parameter to the maximum number of channels available for each stream . This setting is found under Audio Live > Input > Source Flows

> Channels .

For each available stream, you must...

Set the number of channels to the maximum available in this dropdown. Note: the default

Auto setting will not work.

439

Special Device Configuration Tasks

Prerequisites

GV Orbit Client Version 2.0.0

User Guide

Setting the maximum number of channels is necessary as GV Orbit Client expects that all channels be available for it to use at any time.

5 Click Take .

6 In GV Orbit Client under Audio Live > Output > Dest Flows :

• Set the Channels parameter to the maximum number of channels available for each stream . This setting is found under Audio Live > Output > Dest Flows .

• Set the Packet Time parameter according to the number of channels configured for each stream . See table below. This setting is found under Audio Live > Output >

Dest Flows .

Packet Time

125us

250us

500us

1ms

4 ms

Maximum number of channels that the stream can carry up to 64 channels up to 32 channels up to 16 channels up to 8 channels up to 2 channels

7 Click Take .

Logical Levels that specifically support Audio Live

To support Audio Live’s ability to support a range of audio channels per AES stream, the following logical levels are used according to the number of channels in the AES stream.

440

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Prerequisites

See also

, on page 210 and Setting the Logical Levels to be

Displayed in the Multilevel Table , on page 265.

Logical Level

AES67-4

AES67-8

AES67-16

AES67-32

AES67-64

Description

4 mono audio channels

8 mono audio channels

16 mono audio channels

This logical level is interchangeable with the SDI audio logical level.

32 mono audio channels

64 mono audio channels

To see the number of audio channels a given logical level supports, see

Editing a Logical

Level , on page 215.

Required Configuration for Audio Streams with Different Packet Times

If for a given topology, all audio streams have the same packet time, then the automatically assigned levels to the output spigots will work. If the topology has audio streams with different packet times, you will have to configure the packet times on Audio Live’s output spigots. Currently GV Orbit Client is unaware of these settings in GV Orbit Client, so you must proceed as follows: duplicate the SDI audio level as many times as there are different

packet times. To duplicate an SDI audio level, see Duplicating a Logical Level , on page 213.

For example, to accommodate a 1 microsecond audio packet time, you duplicate the SDI audio level with the -1 suffix. To accommodate a 250 microseconds audio packet time, you again duplicate the SDI audio level with the -250 suffix.

441

Special Device Configuration Tasks

Configuring an Audio Live device in GV Orbit Client

GV Orbit Client Version 2.0.0

User Guide

You also need to set the proper AES67 levels on the Audio Live output streams in GV Orbit

Client. For example:

• If output spigot 1 has been configured with 16 channels at 250 microseconds, then the streams for output spigot 1 should be assigned the AES67-16-250 level.

• If the output spigot has been configured with 8 channels at 1 ms, then the streams for that spigot should be assigned the AES67-8-1 level.

Note: You will need to set the level on all output streams of the Audio Live configuration in GV Orbit Client if your topology uses more than one packet time value.

Configuring an Audio Live device in GV Orbit Client

To add an Audio Live device to a topology

1 Add the Audio Live device to the Topology: from the Device Library , Discovered , find an Audio Live device bubble that you want to control. See

To add a Discovered Device to a Topology , on page 227.

2 Click on the name of the device underneath the bubble to name the device or device

group. See To name a device and set the number of devices in the group , on page 225.

442

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Known Audio Live limitations

3 On the topology, connect the Audio Live device to the network switches. See

Methods to Link Devices in a Topology , on page 239.

By default, the Audio Live device is created according to the configuration defined in

GV Orbit Client. The streams are assigned the appropriate AES67 levels, based on the number of channels. The Audio Live can be used as is, without a need to modify the device properties in the Property Editor, unless you need to modify the streams to use custom levels.

4 Create the sources and destinations. See Automatically Creating AES67 Audio Channels for Sources and Destinations , on page 445.

5 Test the configuration by making takes between a logical source and destination that

use the AES67 audio levels. See Performing a Take in Router Control , on page 467.

Known Audio Live limitations

• When choosing an Audio Live spigot to use for the take, GV Orbit Client will only use an output spigot that has the same number of channels as the destination, and only use an input spigot that has the same number of channels as the source. If no such spigot is available, the take will fail. It will not try to use multiple spigots (for example, if the source/destination is 16 channels, it will not try to use 2 spigots, each with 8 channels), and it will not try to use part of a spigot (for example, if the source/destination is 8 channels, it would not try to use the first 8 channels of a 16 channel spigot).

• In the Audio Live configuration, the channel count of an Input Configuration and

Output Configuration cannot be set to Auto as GV Orbit Client does not support this setting. See

Required Audio Live Configuration in the GV Orbit Client Control Panel , on page 438.

• The number of channels on the input stream must match the number of channels on the source stream, and the number of channels on the output stream must match the number of channels on the destination stream.

• For streams that have an AES67-X level, the logical source/destination that is automatically created is not usable. Instead, you must create custom logical sources and destinations, and place the streams in the SDI Audio or audio1 to audio16 level columns instead. See

Required Configuration for Audio Streams with Different Packet

Times , on page 441.

443

Special Device Configuration Tasks

Configuring an IQAMD40 Device

GV Orbit Client Version 2.0.0

User Guide

Configuring an IQAMD40 Device

About IQAMD40

The IQAMD40 provides multichannel MADI-to-IP interfacing, and has been developed to allow high-density audio integration into Ethernet IP networks. Using industry standard

AES67 encapsulation and an IP interface enables the IQAMD40 to interface directly with many common audio desks and systems.

PREREQUISITES: IQAMD40 must be connected to the network, licensed, and has been previously configured with GV Orbit Client.

IQAMD40 Integration in GV Orbit Client

GV Orbit Client supports the routing of audio signals through an IQAMD40 card.

To add an IQAMD device to a topology

1 Add the IQAMD device to the Topology: from the Device Library , Discovered , find an

IQAMD device bubble that you want to control. See

To add a Discovered Device to a

Topology , on page 227.

444

GV Orbit Client Version 2.0.0

User Guide

Special Device Configuration Tasks

Automatically Creating AES67 Audio Channels for Sources and Destinations

2 On the topology, connect the IQAMD device to the network switches. See

Methods to

Link Devices in a Topology , on page 239.

Automatically Creating AES67 Audio Channels for Sources and Destinations

GV Orbit Client routes multiples of 16 audio channels by default. As a result, if you want to send 64 audio channels to a destination, you create four destinations with 16 audio channels each.

An automation shown in the procedure below allows you to add the all the Stream’s AES67 audio channels to the Multilevel Table in the Logical Device Table at once for AES67 sources and destinations.

To automatically create the AES67 audio channels for sources and destinations

1 In the Logical Device Table, Multilevel Table, select the Sources tab.

2 Select one or more streams in the Stream Browser (using <Ctrl> + click) for which you want to create all the source / destination audio channels.

3 Click to show the Channel Browser in the Stream Browser of the Logical Device

Table. See Stream Browser / Channel Browser , on page 260.

4 Click to select all in the Channel Browser.

445

Special Device Configuration Tasks

Automatically Creating AES67 Audio Channels for Sources and Destinations

GV Orbit Client Version 2.0.0

User Guide

5 Click automated sources / destinations in the Channel Browser to create the selected streams in the multilevel Table.

The 64 audio streams are created as four sources / destinations with 16 audio channels each.

6 Select the Destinations tab and repeat from

step 2 .

7 Test the configuration by making takes between a logical source and destination that use AES67 levels. See

Performing a Take in Router Control , on page 467.

446

Overview

The Monitoring tasks in GV Orbit Control Client are used to view information about tie line use and the source to destination path of the streams and to monitor the health of the GV

Orbit Client Controllers and the devices in the selected topology.

The GV Orbit Client Monitoring Tasks include:

•

Path Manager Tasks , on page 448

•

System Status Task , on page 455

447

Monitoring Tasks

Path Manager Tasks

GV Orbit Client Version 2.0.0

User Guide

Path Manager Tasks

Use the Path Manager task to view information about the tie-line use and the source to destination path of the streams. Tie-lines also show the current percentage of bandwidth used.

When a topology includes a DCNM Network Switch, the Path Manager shows:

• Technical information that can be used to help diagnose network connectivity and path issues (no signal or wrong signal at the destination).

• The overall health status of each Network Switch device.

DCNM

Network

Switches

Click to view more DCNM

Network Switch device detail

The DCNM Network

Switch is currently offline

Percent of currently-used bandwidth

Network Switch devices have a blue bubble that when clicked provides more information about the internal status of the DCNM Network Switch that is shown in the Status tab.

448

GV Orbit Client Version 2.0.0

User Guide

Monitoring Tasks

Accessing the Path Manager

Interpreting DCNM Network Switch Symbols

The following DCNM network switch symbols are used to represent the Network Switch device’s health.

Symbol Description

The DCNM network switch device is healthy.

Connection to the DCNM network switch device is offline.

To diagnose: Select this device and select the Status tab to view more technical information that can be used to troubleshoot the issue in the DCNM Web interface

(by looking at the host policy / flow policy / flow status).

For a system-level health status, see

Accessing the Path Manager

To access the Path Manager Task

1 Open GV Orbit Control Client Stage. See

2 Select the required Area. See Selecting an Area , on page 203.

3 Select the required topology. See Selecting a Graph , on page 204.

4 Make the topology active. See

Activating a Topology , on page 253.

5 Select Monitoring > Path Manager .

449

Monitoring Tasks

Viewing Information about the Tie-lines

The Path Manager task opens:

GV Orbit Client Version 2.0.0

User Guide

Under Path Management, click any of the following tabs for more information:

• Tie-lines

• Streams

• Destinations

• Status

Path Manager Topology Menu

The Path Manager Topology menu has the following menu options.

Icon

Refresh

Description

Reloads the Topology’s contents. See

Refreshing the Topology , on page 222.

Shows the top level of the topology.

Overview

Refresh Tielines Allows you to recompute the tielines usage based on the current crosspoints in each device, in case the tieline status in the control system has become out-of-sync with what is actually routed.

During tieline refresh, all tielines are locked and you can not perform any takes. Only use this feature during off hours as this can take up to

30 seconds to complete.

Viewing Information about the Tie-lines

To view information about the tie-lines

1 Open the Path Manager for the selected topology. See Accessing the Path Manager , on page 449.

2 Click Overview if available.

The tie-lines show their currently-used capacity in percent.

450

GV Orbit Client Version 2.0.0

User Guide

3 Select a tie line in the Topology.

Monitoring Tasks

Viewing Information about the Streams

In the Tie-lines tab, the source and destination information is displayed under the following headings:

• Tie line Name

• Tie line Source: Device, Port, Capacity (bps), BW (bps)

• Tie line Destination: Device, Port, Capacity (bps), BW (bps)

• Source

• Destination

Viewing Information about the Streams

To view information about the streams

1 Open the Path Manager for the selected topology. See Accessing the Path Manager , on page 449.

2 Click Overview if available.

3 Select a tie line in the Topology.

4 Select the Streams tab.

5 In Tie-lines, select a tie-line that you want more information on its streams.

The stream information is displayed under the following headings:

• Stream

• IP address

• BW (bps)

• Source

• Destination

Viewing Information about the Destinations

This tab shows the path for a signal to a destination. If a destination is showing the wrong signal, use this tab to trace the destination signal back to the source or to start fault-finding.

451

Monitoring Tasks

Viewing Information about the Destinations

GV Orbit Client Version 2.0.0

User Guide

When a topology includes a GV Fabric / DCNM Network Switch, this tab shows operational status information about the path used by a signal to a destination through the GV Fabric /

DCNM Network Switches, GV Node senders and receivers for example. When you select a

Network Switch device that is in alarm, more information about the internal status of the

GV Fabric / DCNM Network Switch is shown in the Status tab.

To view information about the destinations

1 Open the Path Manager for the selected topology. See Accessing the Path Manager , on page 449.

2 Select the Destinations tab.

All the destinations are listed on the right.

3 Select a destination. The path details to that destination are shown.

If the topology includes a DCNM Network Switch, the path details will include the spine and leaf connections within the DCNM network. This can be used to diagnose issues with the DCNM network switch or any other signal path issue. For example, the figure below shows that the RED network is in alarm and as such no signal is passing through this part of the switch’s fabric.

452

To know more about the DCNM Network switch symbols that are used for health monitoring, see

Interpreting DCNM Network Switch Symbols , on page 449

GV Orbit Client Version 2.0.0

User Guide

Monitoring Tasks

Viewing Information about the Status

4 If a DCNM network switch is in alarm, select it and more specific diagnostic information for the related flow shown under the Path Management , Status tab.

Use this information to diagnose path issues, for example, through the switch’s or

GV Node’s native configuration interface.

5 Click Overview to view a highlighted path between the source, shown in green, and the destination, shown in brown.

Viewing Information about the Status

When a topology includes a DCNM Network Switch, this tab shows more technical information about the DCNM Network Switches such as the Network Switch device’s operational status that can be used to diagnose the issue in the path issue, for example, through the switch’s or GV Node’s native configuration interface.

To view information about the status

1 Open the Path Manager for the selected topology. See Accessing the Path Manager , on page 449.

2 Select the Status tab.

The flow status of the DCNM Network Switches are displayed, if applicable.

DCNM

Network

Switches

Click to view more DCNM

Network Switch device detail

The DCNM Network

Switch is currently offline

Percent of currently-used bandwidth

453

Monitoring Tasks

Viewing Information about the Status

GV Orbit Client Version 2.0.0

User Guide

Network Switch devices have a link that when clicked shows the exploded network switch showing more information about spine and leaves, and the bandwidth capacity for each specific link.

Click each switch to see its health of the switch (as report by the switch itself).

Disabled Ports shows a list of all the switch’s disconnected or unused ports that are currently disabled by the switch.

454

GV Orbit Client Version 2.0.0

User Guide

Monitoring Tasks

System Status Task

Use the System Status Task to monitor the health of the GV Orbit Client Controllers and the devices in the selected topology. You can also perform a manual failover from this task.

Accessing the System Status Task

To access the System Status Task

1 Open GV Orbit Control Client Stage. See

2 Select the required Area. See Selecting an Area , on page 203.

3 Select the required topology. See Selecting a Graph , on page 204.

4 Select Monitoring > System Status .

The System Status task opens:

In this configuration, Controller 1 is the active controller and Controller 2 is not present.

The System Status task displays the following information for both GV Orbit Client controllers: Controller 1 and Controller 2 . Depending on the server hardware model

455

Monitoring Tasks

Accessing the System Status Task

GV Orbit Client Version 2.0.0

User Guide and the software applications that are currently installed, certain status parameters shown in the table below will not be displayed.

Parameter

Status

Description

The current controller’s IP address.

The current status of GV Orbit Client Controller 1 and Controller 2 (if equipped):

Active: All GV Orbit Client task are being processed by this controller.

Ina ctive: This controller is in hot standby. It is ready to take over from the active controller.

Force Active:

Make this controller the active controller. See Forcing the

Inactive Controller to be the Active Controller , on page 457.

Health

The current controller’s health metric:

A green bar indicates that the controller’s overall health is good.

Identifies the members of a cluster:

1: The server that the administrator logged in to when creating the cluster.

This is the first server of the cluster.

2: The second server that was added by an administrator who was logged in to the first server when creating the cluster.

CPU and Memory The current GV Orbit Client server’s CPU and memory usage show the current level of activity.

Orbit Control

Memory

The current GV Orbit Client server’s memory usage for the local GV Orbit

Client application. l

Densité Memory The current GV Orbit Client server’s memory usage for the local Densité application. The percentage reflects the memory used out of its allocated heap size of 8 GB.

Fans

PSU

The current controller’s cooling fan health:

A green box indicates that the controller’s fans are operating correctly.

Green : the PSU is plugged and detects power.

Red : the PSU doesn't detect power. Possibly the power cable is unplugged.

Gray or no status: the server doesn't detect correctly the PSU unit because the unit is physically removed or the initialization isn’t done. In this second case, shutdown the server, disconnect both power cables, physically remove both power supply units, re-insert them both and apply power to both. Then start the server.

Network Interface The current controller’s Ethernet interface names and health:

A green box indicates that the controller’s Ethernet interfaces are operating correctly.

Devices The current status of the devices:

Active: This device is in active operation.

Standby : This device is in hot standby. It is ready to take over from the active device.

Faults A list of any current faults.

456

GV Orbit Client Version 2.0.0

User Guide

Monitoring Tasks

Forcing the Inactive Controller to be the Active Controller

For more information about the health status of a DCNM Network Switch device, see Path

Manager Tasks , on page 448.

Forcing the Inactive Controller to be the Active Controller

If two controllers are configured in a redundant configuration, then during the normal course of operations, one controller is active and the other is inactive at all times.

If a problem occurs, such as network loss or connectivity issues, the inactive controller

(Controller 2) becomes the active controller. The controller that was formerly active

(Controller 1) reboots. This is an automatic failover. You can perform a manual failover if you have administrator rights in the selected Area. See

1 Open the System Status task for the required topology. See Accessing the System

To perform a manual failover

Status Task , on page 455.

2 Click the Force Active button for the Inactive Controller.

A confirmation message appears.

3 Click OK to continue.

457

Monitoring Tasks

Forcing the Inactive Controller to be the Active Controller

GV Orbit Client Version 2.0.0

User Guide

The controllers switch states. The formerly inactive controller (Controller 2) becomes active. The formerly active controller (Controller 1) reboots. As it shuts down, the following changes occur and are reflected on the System Status task.

• The Status of the Controller 1 is now Inactive .

• A red bar is displayed for the Health of Controller 1, indicating it is not good.

• The CPU and Memory are at 0% .

• The Fans and Network Interface are blank.

• The Status of the Controller 2 is now Active .

• A green bar is displayed for the Health of Controller 2, indicating it is good.

• The CPU and Memory fields show their level of activity.

• The Fans are green, indicating health.

• The Network Interface displays the Management Interface port name (em1).

• The status of all devices controlled by Controller 1 is unknown .

• The status of all devices controlled by Controller 2 is active .

458

GV Orbit Client Version 2.0.0

User Guide

Monitoring Tasks

Forcing the Inactive Controller to be the Active Controller

When Controller 1 comes back, the following changes occur and are reflected in the interface.

• The status of Controller 1 is now Inactive .

• The health field for Controller 1 displays a green bar indicating it is good.

• The CPU and Memory fields for both controllers show the current level of activity.

• The fans for both controllers show green boxes indicating health.

• The Network Interface port of both controllers is displayed, em1 .

• The status of the devices on Controller 1 is unknown .

• The status of the devices on Controller 2 is active .

Finally, when Controller 1 is fully rebooted, the following changes occur:

459

Monitoring Tasks

Permissions

GV Orbit Client Version 2.0.0

User Guide

• The status of the devices on Controller 1 is standby .

Permissions

Only users who are assigned to Administrators role in the selected area have View, Edit, and

Delete permissions in the System Status task. Users who are assigned to Engineers,

Operators, and Maintenance roles have view rights only. See

Alias Editor Tasks , on page 462

460

Overview

The GV Orbit Client Control Tasks include:

•

•

Router Control Tasks , on page 466

461

Control Tasks

Alias Editor Tasks

GV Orbit Client Version 2.0.0

User Guide

Alias Editor Tasks

Use the Alias Editor to assign aliases to sources and destinations. More than one set of aliases can be created to allow the source / destination naming conventions to be changed on the fly, for example, to change the interface for different programs or production staff, or to support another language(s).

Accessing Alias Editor Tasks

To access the Alias Editor

1 Open GV Orbit Client Stage. See

2 Select the required Area. See Selecting an Area , on page 203.

3 Select the required topology. See Selecting a Graph , on page 204.

4 Select Control > Alias Editor .

The Alias Editor task opens.

462

The Alias Editor has tabs for Source and Destination IDs.

Alias Editor Menu

The Alias Editor menu has the following menu options.

Icon

Refresh

Cut

Copy

Paste

Description

Reloads the Alias Editor’s contents.

Cuts the selected contents from an alias column.

Copies the selected contents from an alias column.

Pastes the clipboard contents to the alias column.

GV Orbit Client Version 2.0.0

User Guide

Control Tasks

About External IDs and Northbound Control Interfaces

Icon label

Restore default

New

Delete

Description

When a selected alias has been renamed, this resets the name to its original label.

Adds an alias column. See

Adding Aliases , on page 463.

Removes the selected alias column.

About External IDs and Northbound Control Interfaces

External IDs are shown by setting Show External ID Columns . External IDs are used for

Northbound control interfaces that use ID-based protocols.

Certain control protocols require that the numbering of external IDs must be contiguous. In this case, if they are not sequential, click Re-Index Ext. IDs .

GV Orbit Client can use the GV Orbit Control Client External ID's when Show External IDs is set to True ; see

Step 7.3.1: Project Variables (Project -> Edit Variables) , on page 76. If

Show

External IDs is set to False , and you click Re-Index Ext. IDs , then you will need to make sure that any external system that relies on this updated index will still have the correct associations for their external IDs, including GV Orbit Client.

External IDs that are larger than the total number of sources or destinations will not status northbound.

GV Orbit Client must have status for all destinations within GV Orbit Client or they will not report northbound for that external ID. For example, if a take has never been made to a destination, that destination will not have its status set. This behavior is different from a physical router where all destinations have a status set by default.

Adding Aliases

These aliases can be used in router control to change the name of sources and destinations from short labels to the labels of the corresponding alias. The alias can be composed of up to 24 characters to create a more descriptive name than its equivalent short label. Aliases

can also be used with panels; see Creating a New Panel

, on page 296. See also Using Source and Destination Aliases with a Panel , on page 309.

Once an alias column has been added, you can also copy/paste a list of values from an

Microsoft Excel spreadsheet column into the alias column to bulk name the sources and destinations.

Aliases created here can be selected in GV Orbit Client’s user interface where sources and destinations are used with the Select Alias option. For example, in the Category

Configurator; see

Category Configurator Tasks , on page 287.

To Add Aliases

1 Open the Alias Editor. See Accessing Alias Editor Tasks , on page 462.

The Alias Editor task opens.

463

Control Tasks

Renaming Source and Destination Labels

GV Orbit Client Version 2.0.0

User Guide

The Alias Editor has tabs for Source and Destination IDs.

2 Select Show External ID Columns columns if necessary.

The aliases are now available to be used with router control and panels. If aliases are used with a panel and they are longer than 8 characters, consider setting the Display 24 characters option for the panel in the Panel’s Property Editor

. See Creating a New Panel , on page 296. The alias to be used in the Category Configurator can be selected; see

Sources &

Destinations Menu , on page 288.

Renaming Source and Destination Labels

Source and destination labels can be renamed. You can also copy/paste a list of values from an Microsoft Excel spreadsheet column into the Name or Alias columns to bulk rename the sources and destinations. Or you can copy the content of one column and paste it into another column.

To rename Source and Destination Labels

1 Open the Alias Editor. See Accessing Alias Editor Tasks , on page 462.

The Alias Editor task opens.

464

GV Orbit Client Version 2.0.0

User Guide

Control Tasks

Renaming Source and Destination Labels

The Alias Editor has tabs for Source and Destination IDs.

2 Rename the source or destination by slow clicking it twice. Or paste a list of names from an Microsoft Excel spreadsheet column into the Name or Alias column to bulk rename them.

Source and Destination labels in the Alias Editor may be shown as grayed out and they cannot be edited. These devices’ configuration properties come from GV Orbit Client.

See

Synchronization of Discovered GVOP Devices, Source, Destination, and Spigot

Names made in GV Orbit Client , on page 229.

465

Control Tasks

Router Control Tasks

GV Orbit Client Version 2.0.0

User Guide

Router Control Tasks

Use the Router Control task to control the sources and destination in an active topology.

Accessing the Router Control Task

To access the Router Control task

1 Open GV Orbit Client Stage. See

2 Select the required Area. See Selecting an Area , on page 203.

3 Select the required topology. See Selecting a Graph , on page 204.

4 Select Control > Router Control .

The Router Control task opens

466

The sources are listed on the left under Logical Router. The destinations are listed in the center. The right hand column displays the actions you can perform.

Router Control Menu

The Router Control menu has the following menu options.

Icon

Select All

Clear All

Description

Selects all source or destination items.

Deselects all source or destination items.

Sort Ascending Sort the source or destination items in alphabetical order from A to Z.

GV Orbit Client Version 2.0.0

User Guide

Control Tasks

Performing a Take in Router Control

Icon Description

Sort Descending Sort the source or destination items in alphabetical order from Z to A.

Use Wide Widgets Doubles the source or destination display width to accommodate longer labels.

This option setting is remembered for the currently logged in user on the current client PC.

Select Alias Select the Alias you want to use to identify Source and Destination streams in GV Orbit Client’s interface.

Aliases are created in the Alias Editor. See Adding Aliases , on page 463.

Performing a Take in Router Control

You can perform a take in Router Control as follows.

1 Under Logical Router , select a source, shown in green.

2 Select a destination, shown in brown.

3 Under Router Control , Control tab, click Take .

467

Control Tasks

Performing a Take in Router Control

GV Orbit Client Version 2.0.0

User Guide

468

Parameter

Take / Auto-Take /

Salvos radio buttons

Take button

Cancel button

Lock button

Protect button

Description

Sets the router control mode:

• Take: Once the source and destination has been selected, you then click Take to make the take.

• Auto-Take: Once the source and destination has been selected, the take is automatically made.

• Salvos:

Trigger previously-configured salvos. See also Creating

Salvos , on page 470.

Makes the connection between the currently selected source and destination. In salvo mode, it triggers the selected salvo.

Cancels the current selection.

Will lock the current destination to not allow the source to be changed by any user. High Tally when enabled on selected destination. See also

About Lock, Protect, and Release , on page 468.

Will protect the current destination to not allow the source to be changed by a user other than the current user. High Tally when enabled on selected destination.

Releases lock or protect on the selected destination.

To minimize the destinations within the selected virtual XPT b .

Release button

Virtual XPT >

Minimize Virtual XPT a

Virtual XPT > Expand

Virtual XPT a

Virtual XPT > Reset

XPT a

To show all the destinations within the selected virtual XPT, including

the nested destinations of all other virtual XPTs b

Initialize the selected virtual XPT. This will route the appropriate virtual source to the logical destinations that were configured for the virtual

XPT in the logical device table.

a.This becomes available when virtual XPTs have been previously configured (see Configuring Virtual

Crosspoints (XPTs) , on page 276). You must select a destination that is part of a virtual destination in

the router control grid or select a virtual destination in the router control grid.

b.See

Minimize and Expand Virtual XPT Destinations , on page 283 for more information.

About Lock, Protect, and Release

The following topics provide a detailed look at how GV Orbit Control manages Lock,

Protect, and Release.

LIMITATIONS:

• iControl matrices do not support protect.

GV Orbit Client Version 2.0.0

User Guide

Control Tasks

Performing a Take in Router Control

• Lock and protect currently affects all levels of the destination and does not consider individual levels. Locking one level locks all destination levels and the control system does not currently support specific lock levels.

Ability to Override a Lock or Protect according to User Rights

When logged in to GV Orbit Control, the permissions assigned to your user profile determine whether you can override a Lock or Protect made by other users. For example, when a user has admin or Operator rights, the user can override any lock or protection made by:

• Any other user. See

Lock/Protect enabled for a Router using NP0016 router control protocol , on page 433.

• A third-party control system that uses NP0017 to control GV Orbit Control.

• A third-party control system that placed a lock on a device which is also controlled by

GV Orbit Control and for which in router lock and protect is enabled. See

About In router

• A panel used to set a lock.

Otherwise, without admin or Operator rights, you will not be able to override a Lock or

Protect set by other users.

See

Administration Tasks , on page 473 for more information about how to create users and

how to set a user’s permissions to allow or deny them from overriding a Lock or Protect set by another user. The following user permissions control the ability to override a Lock or

Protect.

• Force Unlock

• Force Unprotect

For example, the admin user has the user permissions for both Force Unlock and Force

Unprotect. Therefore, an admin user can override any other user who has set a Lock or

Protect on a destination.

Using a Panel to Override a Lock or Protect

If a configured panel in GV Orbit Client is used, a user must be assigned to it. Assign a user to a panel through the Panel User parameter (see

Adding the New Panel to the Topology , on page 316). It is the user rights that are associated to the user selected in the

Panel User parameter that determines the panel’s priority to override a lock or protect made by another panel user. This can be used to prevent other users from being able to remove a lock. When the Panel User parameter is set to a user that has admin or Operator rights, the panel can be used to override any lock or protection made by:

• Any other user. See

Lock/Protect enabled for a Router using NP0016 router control protocol , on page 433.

• A third-party control system that uses NP0017 to control GV Orbit Control.

• A third-party control system that placed a lock on a device which is also controlled by

GV Orbit Control and for which in router lock and protect is enabled. See

About In router

• Another panel used to set a lock.

469

Control Tasks

Creating Salvos

GV Orbit Client Version 2.0.0

User Guide

Identifying the User who has Locked a Destination

To see who has locked a destination, try to make a take to the destination in the Router

Control task. See

Router Control Tasks , on page 466. The user locking / protecting the

destination is then shown in the lower left corner. If the user is admin , then this could be the result of a third-party control system having locked or protected a destination in the router.

How is Lock, Protect, and Release Implemented?

The router protocol and the GV Orbit Control’s router control port configuration can affect how the Lock, Protect, and Release are implemented. For a further explanation, refer to the router protocol you are using.

Router Control Protocol See

NP0016 Compact Router

About In router Lock/Protect enabled for a Router using NP0016

NP0016 Enterprise Router

router control protocol , on page 433

NV9000 TCP/IP (NP0017 southbound)

Lock, Protect, and Release with the NV9000 Control Port , on page 435

NP0016 Enterprise Router

Lock, Protect, and Release with the NP0016 / NS-Bus / SAM SW-P-

NS-BUS

08 Control Ports , on page 470

SAM SW-P-08 TCP/IP

Lock, Protect, and Release with the NP0016 / NS-Bus / SAM SW-P-08 Control Ports

GV Orbit Client stores the locks in its database and they are preserved after a restart/reboot.

As such, destinations will remain locked/protected. GV Orbit Client system does not read a lock from a router and does not control a lock in the router.

Creating Salvos

When a salvo is triggered, it executes a list of pre-configured actions. You can create a salvo as follows.

1 Under Router Control , Salvo Editor tab, click New .

2 Enter a name and description for the salvo in the Salvos list.

470

GV Orbit Client Version 2.0.0

User Guide

Control Tasks

Creating Salvos

Salvos

Salvo Action

List

Icon

New

Duplicate

Delete

Take

Lock

Protect

Release

Pause

Append

Insert

Description

Create a new salvo and associated salvo action list.

Make a copy of the currently-selected salvo.

Remove the currently-selected salvo / take.

Add the currently-selected source and destination as a take action to the salvo list. The following functional behaviors are by design:

• If multiple destinations are selected, then there will be multiple take actions added to the salvo list.

• If there is only one source and multiple destinations selected, then that source is routed to all destinations.

• If multiple sources are selected (for example, Source1, Source2,

Source3) and multiple destinations are selected (for example,

Destination1, Destination2, Destination3, and Destination4), then the takes added to the salvo list are Source1 to

Destination1, Source2 to Destination2, Source3 to

Destination3.

Lock the currently selected destination. See also

About Lock, Protect, and Release , on page 468.

Protect the currently selected destination.

Release the currently selected destination.

The wait time in milliseconds that can be added to the list of operations.

In this mode, any new salvo operation will be added to the end of the salvo action list.

In this mode, any new salvo operation will be inserted at the currently selected spot in the salvo action list.

471

Control Tasks

Selecting the Name of Sources and Destinations

GV Orbit Client Version 2.0.0

User Guide

Icon

Replace

Move Up

Move Down

Description

In this mode, any new salvo operation will replace the currentlyselected salvo action from the salvo action list.

Move the selected salvo action up in the salvo action list.

Move the selected salvo action down in the salvo action list.

3 Under Logical Router , select a source, shown in green.

4 Select a destination, shown in brown.

5 Under the salvo action list, click Take .

Selecting the Name of Sources and Destinations

When a source or destination has been assigned an alias, you can select the alias to be

shown through the Alias drop-down menu. To create aliases, see Alias Editor Tasks , on page 462.

1 Select a source or destination under Logical Router .

2 Click the alias drop-down menu and select an alias option.

The label for the selected source or destination changes to the selected option.

472

User Management is the only Administration task. Only administrators have access to it.

User Management Task

As an administrator, you have access to the User Management Task. This is used for:

• Creating, editing, and deleting user profiles. See

Creating User Profiles , on page 475.

• Managing access rights to the areas in your system. See

Granting Access Permissions to an Area , on page 477.

• Viewing and assigning permissions according to predefined user roles. See Viewing

Permissions by Role , on page 480.

473

Administration Tasks

The User Management Task Overview

GV Orbit Client Version 2.0.0

User Guide

The User Management Task Overview

Note: Before you assign access permissions, you must create areas in your system.

For details, see Area Configurator Tasks , on page 197.

When you first log in to the User Management Task, the admin tile appears in the Users section.

The User Management Task UI has four columns:

• Users : The column displays a tile for each user who has access to your system. See

Creating User Profiles , on page 475.

• Areas

: The column displays a tile for each area defined in your system. See Granting

Access Permissions to an Area , on page 477.

• Roles : The column displays a tile for each of the predefined roles: Administrator,

Engineer, Operator, Maintenance, and Guest.

Permissions to view, edit, and delete within each client task vary by role. These permissions can be seen when you select the role in the Roles column; for example,

Administrator is selected in the screen shot above. The permissions granted to the administrator role are shown in the Permissions column. (Members of the administrator role have full access permissions to all areas in the system). See

Viewing Permissions by

Role , on page 480 for a list of the permissions available to each role.

• Permissions : The column displays a tile for the tasks that users can perform within the areas in your system according to the selected User, Area, and Role. View, edit and delete icons show the current user’s rights for the task.

474

GV Orbit Client Version 2.0.0

User Guide

Administration Tasks

Creating User Profiles

The first step is to create your user profiles.

Note : To access the user profiles, you must belong to the administrator role.

Otherwise, Administration tasks are not visible in GV Orbit Control Client Stage.

To create a new user account:

1 Launch GV Orbit Control Client.

2 Log in as an administrator.

3 Select Administration > User Management .

The User Management window appears.

4 Click the Add button in the top left corner.

The user configuration window appears.

5 Enter the required information in the User ID , First Name , Last Name , Password , and

Confirm Password fields.

6 If this user is to represent an external northbound routing device for Lock, Protect, and

Release with the NP0016 / NP0017 router control protocol, set the External ID that this

475

Administration Tasks

Creating User Profiles

GV Orbit Client Version 2.0.0

User Guide device uses in its NP0017 router protocol communications with GV Orbit Control. This

value is an unsigned integer. See Setting a User ID for Lock, Protect, and Release with

NDAC NP0016 / NP0017 Northbound Interfaces , on page 483 for more information.

Note: User databases are not synchronized between the GV Orbit Client and GV Orbit Control Client. You must assign the same ID to the same user in both the GV Orbit Client and GV Orbit Control Client.

In all cases, you must ensure that user IDs are coherent between GV Orbit Client and

GV Orbit Control Client.

Equivalent Parameter in GV Orbit Client Equivalent Parameter in GV Orbit Control Client

User name

Control External Id

User ID

External Id

See

How to Add a User , on page 179 for how to set these parameters in GV Orbit Client.

7 Click OK .

A new tile representing the new user account appears in the Users section.

In addition, you can perform the following procedures in the Users section:

• Edit: Select the icon for the user and click Edit to modify the user’s credentials.

• Delete: Select the icon for the user and click Delete to remove the user account. There is no confirmation when you click Delete . The user profile is immediately removed.

See also

•

Switching User Profiles , on page 191

476

GV Orbit Client Version 2.0.0

User Guide

Administration Tasks

Granting Access Permissions to an Area

Users are granted access to each area via a predefined role. The procedure is as follows:

To grant access to an area

1 Launch GV Orbit Control Client.

2 Log in as an administrator.

3 Select Administration > User Management .

The User Management task appears.

The Users column displays tiles for all the users who have access to the system.

4 Select the applicable user tile in the Users section.

The Areas column displays tiles for all the areas defined in your system.

477

Administration Tasks

Granting Access Permissions to an Area

GV Orbit Client Version 2.0.0

User Guide

5 Select an area tile in the Areas section while keeping the user tile selected.

The Roles column displays tiles for all the roles when both the user tile and the area tile are selected, at the same time.

6 Select a role tile and drag it on top of the area tile.

This action gives the user all the permissions defined for the role in the selected area.

478

GV Orbit Client Version 2.0.0

User Guide

Administration Tasks

Granting Access Permissions to an Area

When you select the user tile in the Users section, the user’s role in the area is displayed at the bottom right of the Area tile.

The permissions granted to the selected role; for example, view, edit, delete, are displayed on the Permissions tile in the Permissions column.

These are listed in the next section.

479

Administration Tasks

Viewing Permissions by Role

GV Orbit Client Version 2.0.0

User Guide

Viewing Permissions by Role

Users are granted access to the areas in the system via their assigned roles. The following rules apply:

• Users can be assigned to different roles in different areas.

• Users cannot be granted permissions as individuals, only according to role.

• The roles are predefined, as follows: Administrator, Engineer, Operator, Maintenance, and Guest. The roles cannot be modified.

• Administrators have full access to all tasks in all areas. Guests have the least permissions. The Engineer, Operator, and Maintenance roles have various permissions, as listed in the following table:

The permissions granted to each role can be viewed on the tiles in the Permissions list book of the User Management task. These can be viewed when the user, the area, and the role are all selected at the same time.

Task

Area configurator

Logical Level Editor

Topology Configurator

Category Configurator

Role

Administrator

Engineer

Operator

Maintenance

Guest

Administrator

Engineer

Operator

Maintenance

Guest

Administrator

Engineer

Operator

Maintenance

Guest

Administrator

Engineer

Operator

Maintenance

Guest

Permissions

View, Edit, Delete

No access

View, Edit, Delete

No access

View, Edit, Delete

View

No access

View, Edit, Delete

No access

480

GV Orbit Client Version 2.0.0

User Guide

Task

Logical Device Table

Panel Configurator

User Management

Path Manager

System Status

Alias Editor

Router Control

Maintenance

Guest

Administrator

Engineer

Operator

Maintenance

Guest

Administrator

Engineer

Operator

Maintenance

Guest

Administrator

Engineer

Operator

Maintenance

Role

Administrator

Engineer

Operator

Maintenance

Guest

Administrator

Engineer

Operator

Maintenance

Guest

Administrator

Engineer

Operator

Guest

Administrator

Engineer

Operator

Maintenance

Guest

Administration Tasks

Viewing Permissions by Role

Permissions

View, Edit, Delete

No access

View, Edit, Delete

No access

View, Edit, Delete

No access

View

No access

View, Edit, Delete

View

No access

View, Edit, Delete

No access

View, Edit, Delete

View

No access

481

Administration Tasks

Viewing Permissions by Role

Task Role

Maintenance & Deployment Administrator

Engineer

Operator

Maintenance

Guest

Router Force Unlock

Setting a User ID for Lock,

Protect, and Release with

NDAC NP0016 / NP0017

Northbound Interfaces , on page 483.

Router Force Unprotect

Administrator

Engineer

Operator

Maintenance

Guest

Protect, and Release with

NDAC NP0016 / NP0017

Northbound Interfaces , on page 483.

External ID

, on page 468 and

Setting a User ID for Lock,

Administrator

Engineer

Operator

Maintenance

Guest

Administrator

Engineer

Operator

Maintenance

Guest

GV Orbit Client Version 2.0.0

User Guide

Permissions

View, Edit, Delete

No access

View

No access

View, Edit, Delete

No access

View, Edit, Delete

No access

View, Edit, Delete

No access

View, Edit, Delete

No access

View, Edit, Delete

No access

482

GV Orbit Client Version 2.0.0

User Guide

Administration Tasks

Setting a User ID for Lock, Protect, and Release with NDAC NP0016 / NP0017 Northbound Interfaces

Setting a User ID for Lock, Protect, and Release with NDAC NP0016

/ NP0017 Northbound Interfaces

With the NP0016 and NP0017 router control protocols, Lock/Protect commands require a

User ID. So that users with different User IDs cannot release a destination locked by another user or panel user; in GV Orbit Control and GV Orbit Client, each user can be assigned a different External ID / Control External Id parameter value. Users with a different External

ID / Control External Id cannot release a destination locked by another user with a different

External ID / Control External Id , unless they have admin or Operator rights.

The NP0016 and NP0017 router control protocol User ID should be set in:

• GV Orbit Control: as of GV Orbit Control version 1.7.0 and above, the User ID provided in northbound commands is taken into account as follows:

• You map this User ID to the External Id parameter of a GV Orbit Control user set in

User Management .

• If this GV Orbit Control user has its External Id parameter value configured to the same value as the User ID in a command, the operation will be performed internally using the alias of the matching user with the user’s associated privileges with respect to Lock, Protect, and Release.

• If this GV Orbit Control user does not have admin or Operator rights, the third-party control system that uses NP0016 / NP0017 to control GV Orbit Control cannot override the lock or Protect set by other GV Orbit Control users. See

Viewing

Permissions by Role , on page 480..

• If no GV Orbit Control user has an External Id parameter value matching the command's user ID, the operation is performed internally as the GV Orbit Control admin user.

• GV Orbit Client: as of GV Orbit Client version 2.0.0 and above, the User ID provided in northbound commands from the GV Orbit Routing service is taken into account as follows:

• You map this User ID to the Control External Id parameter of a GV Orbit Client user set in the User tab.

• This user then issues NP0017 router control protocol communications with the

User ID from the user’s Control External Id value.

• The admin user or a user with an Control External Id set to 0 can override locks set by any other user.

The User ID / External ID / Control External Id parameter is an unsigned integer.

To create a User to represent external northbound routing device in GV Orbit Control

Client

Proceed as follows.

1 In GV Orbit Control, create a new user to represent the third-party control system. See

Creating User Profiles , on page 475.

483

Administration Tasks GV Orbit Client Version 2.0.0

Setting a User ID for Lock, Protect, and Release with NDAC NP0016 / NP0017 Northbound Interfaces User Guide

2 In GV Orbit Control, set the External Id parameter to that of the user ID used by the third-party control system in its NP0016 / NP0017 router control protocol.

3 In GV Orbit Control, assign the privileges to this new user. See Granting Access

Permissions to an Area , on page 477:

• Assign Engineer or Maintenance rights to this new user to prevent the third-party control system from overriding the lock or Protect set by other GV Orbit Control users.

• Assign admin or Operator rights to this new user to allow the third-party control system to override the lock or Protect set by other GV Orbit Control users.

If the third-party control system’s NP0016 / NP0017 router control protocol,

Lock/Protect commands use a user ID that GV Orbit Control cannot match to the

External Id value of any GV Orbit Control user, the Lock/Protect commands will be carried out as an Admin user (which has the Router Force Unlock and Router Force

Unprotect privileges), thereby allowing the external control system to overrride the locks of other GV Orbit Control users.

Protect, and Release works with other users and other GV Orbit Control components such as panels.

GV Orbit Client stores the locks in its database and they are preserved after a restart/reboot. As such, destinations will remain locked/protected. GV Orbit Client system does not read a lock from a router and does not control a lock in the router.

4 In GV Orbit Client, create a new user to represent the same user name you created in

GV Orbit Control above. See How to Add a User , on page 179.

5 In GV Orbit Client, set the Control External Id parameter to the same User ID value you set above in the External Id parameter above.

484

GV Orbit Client Version 2.0.0

User Guide

Administration Tasks

Setting a User ID for Lock, Protect, and Release with NDAC NP0016 / NP0017 Northbound Interfaces

485

Administration Tasks GV Orbit Client Version 2.0.0

Setting a User ID for Lock, Protect, and Release with NDAC NP0016 / NP0017 Northbound Interfaces User Guide

486

Introduction

GV Orbit Client has user router control functionality and offers the following routing control panels:

•

Routing Control - Bulk Routing Panel

(see this chapter) - a simple, non-editable soft panel for fast control of all router cross-points.

•

Routing Control - XY Routing Panel - an editable and customizable soft panel, typically

used for small custom panels for specific routing needs.

This chapter describes the Bulk Routing Panel .

GV Orbit System

Routing control panels (soft or hard) connect to a GV Orbit Routing service running on a GV

Orbit server.

Controller-specific connection protocol:

• SW-P-08; or

• NP-0017

GV Orbit server

GVOP protocol

GV Orbit Routing Panel

GV Orbit Client

Fig. 11-1: GV Orbit Routing Panel, Routing Service and Router Controller

A GV Orbit system has one or more GV Orbit servers which run GV Orbit services. Routing panels in a GV Orbit Client connect to a router controller device via the GV Orbit Routing service. Router controllers include GV Orbit itself, a Grass Valley Router Controller device, or

487

Routing Control - Bulk Routing Panel

Prerequisites

GV Orbit Client Version 2.0.0

User Guide

GV Convergent. The Routing service provides source/destination information to the client

and acts on routing commands from the client. See Figure 11-2.

Fig. 11-2: GV Orbit System Diagram

Prerequisites

A GV Orbit server is required, running:

• A GV Orbit Control application.

• A GV Orbit Routing service configured for connection to a Router Controller using either NP0017 or SW-P-08 protocol.

488

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

What is a Bulk Routing Panel?

The GV Orbit Bulk Routing panel is accessible from the GV Orbit Client application. This is a simple, quick, non-editable panel which has been designed to allow fast control of router cross-points and facilitate both keyboard and mouse navigation.

Fig. 11-3: Bulk Routing Panel Example

Key Features

• Keyboard navigation.

• Single source to single destination.

• Single source to multiple destinations.

• Multiple sources to multiple destinations.

• Copy Paste

• Take and Auto Take.

• Lock and Protect.

• Salvos.

•

List View mode for level-focused routing.

• Shuffles and Breakaways.

• Filter Sources, Destinations, Levels and Salvos.

• Custom filtering.

• Filter destinations by routed source.

• Sort (ascending and descending).

• Source and Source-Level Dial-up.

489

Routing Control - Bulk Routing Panel

Open a Bulk Routing Panel

GV Orbit Client Version 2.0.0

User Guide

Open a Bulk Routing Panel

The GV Orbit Bulk Routing Panel is accessible from the GV Orbit Client application:

•

From the Workflow Window

•

From the Network Window

Note: The Bulk Routing Panel is best viewed in full-screen on a 1080P 16:9 monitor screen with GV Orbit Client.

From the Workflow Window

To open the Bulk Routing Panel from the Workflow window:

1 Open a GV Orbit C&M project in GV Orbit Client and adjust the window size to be fullscreen.

Full-size is the recommended window size for operation; all controls are visible.

2 Ensure the GVOP client domain is set to be the same as that being used by the GV Orbit

Routing service on the GV Orbit server. (Main menu: ‘Connections > GVOP’.)

3 In the Workflow window, click on the Bulk Routing

icon. (See Figure 11-4.)

Click on Bulk Routing icon.

Fig. 11-4: Open a Bulk Routing Panel

The Bulk Routing Panel is opened. See Figure 11-6 for a sample Bulk Routing Panel.

From the Network Window

To open the Bulk Routing Panel from the Network window:

1 Open a GV Orbit C&M project in GV Orbit Client and set the window size to be fullscreen.

2 Ensure the GVOP client domain is set to be the same as that being used by the GV Orbit

Routing service on the GV Orbit server. (Main menu: ‘Connections > GVOP’.)

3 Locate the Routing service item in the Network window of GV Orbit Client.

And right-click on the item and select ‘Open Panel’. See Figure 11-5.

490

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

From the Network Window

Right-click on the

Routing service item and select ‘Open Panel’.

Fig. 11-5: Open a Bulk Routing Panel

Note: A ‘Routing service’ item in the Network window is formed when a

Routing service is running on the GV Orbit server and is configured to talk to a router controller.

An example Bulk Routing Panel is shown in Figure 11-6.

491

Routing Control - Bulk Routing Panel

From the Network Window

GV Orbit Client Version 2.0.0

User Guide

492

Fig. 11-6: Example Bulk Routing Panel

GV Orbit Client Version 2.0.0

User Guide

Bulk Routing Panel Layout and Controls

Routing Control - Bulk Routing Panel

Bulk Routing Panel Layout and Controls

Keyboard Shortcuts icon

(1) Source Grid

(3) Destination Grid

(5) Router Control

(6) Salvos

Splitter handles

(2) Source Levels Grid

(4) Destination Levels Grid

Fig. 11-7: Bulk Routing Panel Layout

The panel is laid out as six grids/panes (see Figure 11-7):

• (1) Source Grid – Scrollable list of all available sources.

• (2) Source Levels Grid – Scrollable list of available levels for selected source(s).

• (3) Destination Grid – Scrollable list of all available destinations.

• (4) Destination Levels Grid – Scrollable list of available levels for selected destination(s).

• (5) Router Control Pane – Take, Lock, and Protect functionality.

• (6) Salvos Pane – List of available Salvos when connected over the NP0017 protocol.

Vertical sizing of the Source and Destination grids can be altered by dragging a splitter handle up/down the screen. Horizontal sizing and sizing of the Router Control and Salvos panes can be altered by dragging a splitter handle left/right. Other sizing is handled

automatically. See Figure 11-7.

493

Routing Control - Bulk Routing Panel

What are the Operational Keyboard Shortcuts?

GV Orbit Client Version 2.0.0

User Guide

What are the Operational Keyboard Shortcuts?

Keyboard shortcuts are available when navigating and operating the Bulk Routing Panel, in addition to using a mouse. The user can freely mix ‘mouse’ and ‘keyboard’ methods.

A list of keyboard shortcuts may be displayed in a movable window which can remain on display while using the Bulk Routing Panel.

To see a list of keyboard shortcuts:

1 Click on the ‘Keyboard Shortcuts’ icon in the tool bar of the Router Control pane.

The Bulk Routing Keyboard Shortcuts

window is shown, see Figure 11-8. This window lists the keyboard shortcuts. It remains

on display and may be moved.

494

Fig. 11-8: Bulk Routing Keyboard Shortcuts Movable Window

Equivalent mouse clicks for some keyboard shortcuts are listed in Table 11-1.

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

What are the Operational Keyboard Shortcuts?

Table 11-1: Bulk Routing Panel Operational Keys / Mouse operations

Operation

Toggle Selection

Take

Panel Button Focus

Panel/Grid Focus

Keyboard

Space bar

Enter

Cursor Arrow Keys

CTRL + Arrow Keys

Mouse

Mouse click

Click Take

Mouse movement/click

SHIFT + Mouse click Add a series of items to/remove from a multiple selection

Add distinct items to/remove from a multiple selection

SHIFT + Cursor keys

CTRL + Space bar

Select Range

(Select a contiguous range)

Paste Series

Space bar on first item then

SHIFT + space bar on last item.

Take

Dial Source

Dial Source-Level

Cancel

Select All in the focused panel

Select None in focused panel

Copy a Destination

CTRL + Mouse click

Mouse click on first item then

SHIFT click on last item.

Alt-CTRL + V when a range of destinations are selected.

Click ‘Paste Series’ icon in panel.

See

What is Copy-and-Paste Series Routing?

, on page 519.

Return / Enter Double-click

N/A Begin to type the name of a

Source when a destination is selected.

See

Dial Source Dialog , on page 509.

Press any single alpha-numeric key when a destination and (one or more) levels are selected.

See

Dial Source-Level Dialog , on page 510.

Escape

N/A

CTRL + A

CTRL + D

Click ‘Cancel’ button in the Router

Control pane.

Click ‘Select All’ icon in panel.

Click ‘Select None’ icon in panel.

Click ‘Copy’ icon in panel

Paste a Destination

CTRL + C when a destination is selected

CTRL + V when target destination, or destinations, are selected

Click on ‘Paste’ icon in panel

495

Routing Control - Bulk Routing Panel

Select/Focus in a Bulk Routing Panel

GV Orbit Client Version 2.0.0

User Guide

Select/Focus in a Bulk Routing Panel

Current Button-Focus

When the mouse cursor is moved over a button, or control item, the button/item is highlighted indicating the current item is in focus.

Selected Destination

Current Button- Focus

Navigate with:

Cursor Keys, or use the mouse

Fig. 11-9: Current Button-Focus Item

Select a Button

To select a button:

• click on a button; or

• press the space-bar key when a button is the current focus item.

De-select Buttons

To deselect all buttons:

• click Cancel in the Router Control pane; or

• press the ESC key.

Move Focus Between Grids/Panels of the Bulk Routing Panel

To move the focus between a grid/panel of the Bulk Routing panel:

• Use the CTRL key and one of the cursor arrow keys.

Focus is indicated by a border around the focused grid.

496

GV Orbit Client Version 2.0.0

User Guide

Pre-selected Source

Currently-routed

Source

Current

Button-Focus

Routing Control - Bulk Routing Panel

Select/Focus in a Bulk Routing Panel

Fig. 11-10: Current Panel/Grid Focus Item

Current Panel/Grid Focus

Navigate with:

Control-Cursor Keys, or use the mouse

497

Routing Control - Bulk Routing Panel

Selecting Multiple Items

GV Orbit Client Version 2.0.0

User Guide

Selecting Multiple Items

Select Multiple Items (CTRL select)

Select multiple items (such as destinations, or sources, etc.) by selecting the first item and

CTRL-selecting the others. For example, to select multiple destinations:

1 Select the first destination by clicking on the destination selection button.

2 CTRL-click on the next destination to add that to the selection.

3 Add other destinations.

Select Multiple - Alternative Method

Multiple items can be selected using the Control key, the Cursor Arrow keys and the Enter key.

1 With the cursor over the first item to be selected, press enter to select it.

2 Use the cursor arrow keys to move to the next item.

3 Select it with CTRL-Enter. This adds to the selection.

4 Add other items similarly.

Select a Range of Items (SHIFT select)

When selecting multiple items (such as destinations, or sources etc.), a range may be selected by selecting:

1 The first destination in the range by clicking on the destination selection button.

2 Selecting the last destination by SHIFT + clicking on its destination button.

Source ranges can be selected similarly.

Select a Range - Alternative Method

A range of consecutive sources or destinations can be selected using the Shift key, Cursor

Arrow keys, and Enter key.

1 With the cursor over the first item to be selected, press Enter to select it.

2 Move to the last item in the range with the cursor keys.

3 Hold down the SHIFT key and press Enter to select it.

The last item and all the items from the first to the last are added to the selection.

498

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Source/Destination Grid Buttons

The source/destination selection grid buttons and level-selection buttons are annotated to reflect the source/destination name or the level name. Additionally, the destination buttons may show the currently-routed source and currently-selected source for the selected destination. Buttons also change shape and are highlighted to show if they are selected or

if sources are currently-routed or currently-selected. See Figure 11-11.

Note:

See

Breakaway and Levels

and Shuffle and Levels

for examples of selecting levels.

Source Name Destination Name

Currently-Routed Source

Currently-Routed Source Name

Pre-Selected Source Name

Selected Destination

Pre-Selected Source

Source Level Name

Destination Level Name

Pre-Selected Source Level Name

Pre-Selected Source Name

Fig. 11-11: Selection Buttons

Note: Select a Destination or a Source to see the corresponding Level selection buttons.

499

Routing Control - Bulk Routing Panel

Level Selection

GV Orbit Client Version 2.0.0

User Guide

Level Selection

When a source or a destination is selected, the associated levels are shown in the corresponding ‘Levels’ grid. If multiple sources or destinations are selected, then only their common levels are shown.

All levels are selected by default. If the user selects one or more levels, then all other levels are deselected.

Keep Last Level Selection After Take

When a different source or destination is selected after a ‘Take’, the level selection is normally cleared. To keep the selected levels, select the Keep Last Selection button in the

‘Levels Grid’ pane tool bar (see Figure 11-12).

Keep Last Selection toggle buttons

Source Levels Grid

Fig. 11-12: Keep Last Selection Buttons

Destination Levels Grid

500

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Router Control Pane

The Router Control pane in the Bulk Routing Panel contains the Take , Lock and Protect functions.

Click icon to see a list of keyboard shortcuts.

Select Auto-Take to make a route as soon as source(s) and destination(s) are selected.

Click Cancel to cancel all selections.

With a destination selected, Lock and Protect buttons are active.

a) No Selections Made b) Destination Selected

After destination(s) and source(s) are selected, the Take button goes active ( red ). c) After Destination and Source Selection

Fig. 11-13: Router Control Pane: a) No Selections Made; b) Destination Selected; c) Destination and Source Selected.

501

Routing Control - Bulk Routing Panel

Tool Bars in a Bulk Routing Panel

GV Orbit Client Version 2.0.0

User Guide

Tool Bars in a Bulk Routing Panel

There is a small tool bar at the top of each grid/pane containing controls for selection/deselection, sorting and filtering.

Source Selection Grid Tool Bar

Click to see drop-down menu of tool bar items.

Click to Select all sources.

Click to Deselect all sources.

Click to Sort sources A-Z.

Click to Sort sources Z-A.

Click to toggle the optional display of Wide Source and

Destination Selection Buttons

Filter control, see

Fig. 11-14: Source Selection Grid - Tool Bar

Source Levels Grid Tool Bar

Click to see drop-down menu of tool bar items.

Click to Select all levels.

Click to Deselect all levels.

Click to keep the Levels selection after a Take.

Click to Sort levels A-Z.

Click to Sort levels Z-A.

Filter control, see What is Bulk Routing

Panel Filtering?

, on page 533.

Fig. 11-15: Source Level Selection Grid - Tool Bar

502

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Tool Bars in a Bulk Routing Panel

Destination Grid Tool Bar

Click to:

• See a drop-down menu of all tool bar items.

• Copy routing information of a Destination selection.

• Paste routing information to a Destination.

• Paste a series of sources to a Destination range.

(See

What is Copy-and-Paste Routing?

, on page 517.)

• Select all destinations.

• Deselect all destinations.

• Sort destinations A-Z.

• Sort destinations Z-A.

• Toggle display of wide selection buttons.

• Toggle Hide Sources . See

Hide Sources , on page 548.

• Toggle List View

mode. See List View , on page 550.

Filter control, see

What is Bulk

Routing Panel Filtering?

, on page 533.

Fig. 11-16: Destination Selection Grid - Tool Bar

503

Routing Control - Bulk Routing Panel

Tool Bars in a Bulk Routing Panel

Destination Levels Grid Tool Bar

Click to see drop-down menu of tool bar items.

Click to Select all level.

Click to Deselect all levels.

Click to keep the Levels selection after a Take.

Click to Sort levels A-Z.

Click to Sort levels Z-A.

GV Orbit Client Version 2.0.0

User Guide

Filter control, see

What is Bulk Routing

Panel Filtering?

, on page 533.

Fig. 11-17: Destination Level Selection Grid - Tool Bar

Router Control Pane Tool Bar

Keyboard Shortcuts icon

Fig. 11-18: Router Control Pane - Tool Bar

504

GV Orbit Client Version 2.0.0

User Guide

Salvos Pane Tool Bar

Click to see drop-down menu of tool bar items

Click to sort sources A-Z

Click to sort sources Z-A

Routing Control - Bulk Routing Panel

Tool Bars in a Bulk Routing Panel

Filter control, see

What is Bulk Routing Panel Filtering?

, on page 533

Fig. 11-19: Salvos Pane - Tool Bar

505

Routing Control - Bulk Routing Panel

Wide Source and Destination Selection Buttons

GV Orbit Client Version 2.0.0

User Guide

Wide Source and Destination Selection Buttons

To facilitate the display of longer source or destination names on selection buttons, there is a

‘wide button’ display option. This is selectable in the Source Grid and, independently, in the

Destination Grid. The option is selected with a toggle button in the tool bar of each grid. See

Figure 11-20.

The display option persists between sessions with the Bulk Routing Panel.

Click to toggle display of normal and wide buttons.

Fig. 11-20: Wide Buttons (Source Grid Shown)

506

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Panel Pop-Up Items

Right-Click in a Bulk Routing Panel

Right-click on the Bulk Routing Panel to display a pop-up context menu. See Figure 11-21.

Fig. 11-21: Right-Click Context Menu

Table 11-2: Right-Click Context Menu Items

Dock/Undock

Window

Item Keyboard

Undock or dock the Bulk Routing Panel window from/to the GV

Orbit Client window.

Full Screen The Bulk Routing Panel window is shown full-screen.

The control toggles full screen mode on/off.

Copy

Deselect All

Lock/Unlock

Same as:

• clicking on Copy icon in grid/pane tool bar; or

• pressing Ctrl-C.

Deselects all items.

Click to lock panel. When panel is locked, controls are grayed-out and user operation is disabled. The control toggles lock on/off

Set Timeout

Copy As Widgets

Click to set a timeout (in seconds) for confirmation from the router controller of routing actions (that is setting the router’s crosspoints).

If the timeout is exceeded, a timeout notification is shown on screen. See

Pop-up Notification Messages

Click to copy a selection of one or more buttons to the GV Orbit

Client’s copy-buffer.

(This is used when designing an XY Routing Panel. See Chapter 12,

Routing Control - XY Routing Panel

, Quick Port-per-Button

Assignment , on page 617.)

507

Routing Control - Bulk Routing Panel

Pop-up Notification Messages

GV Orbit Client Version 2.0.0

User Guide

Pop-up Notification Messages

During Bulk Routing Panel operation, notification messages may pop up at the foot of the

GV Orbit Client application window. These messages are informative to the user, advising, for example, on the setting up of a route, or of a broken/re-made Routing service

connection. See Figure 11-22 for some example messages.

Click OK to clear a message.

508

Fig. 11-22: Notification Message Examples

Click OK to clear the message.

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Dial Source and Dial Source-Level Dialogs

To help with source and source level selection when making a route, a ‘dial-up’ dialog allows the user to begin to type in a source name and see a filtered list of sources and source levels.

There are two ‘dial-up’ dialogs

•

Dial Source Dialog

for Source selection.

•

Dial Source-Level Dialog

for Source and Level selection.

These dialogs enable a user to select a source and/or level and route it to a destination.

Note: To clear a ‘dial-up’ dialog before making a route, click the ESC key.

Dial Source Dialog

Dial Source is a quick way of selecting a Source for a destination and routing it.

With a Destination selected, a Source may then be found by typing a part of a source name with the keyboard’s alpha-numeric keys. A Dial Source dialog is displayed and, as characters are entered:

• Sources matching the entered characters are displayed in a drop down list; and the

• Source Grid is correspondingly filtered.

After a valid Source has been selected, a route can be made by pressing the Enter key.

Example

To see and use the Dial Source dialog:

1 Select a Destination .

2 Begin to type in a Source name.

A Dial Source

dialog pops up. (See Figure 11-23.)

3 Continue typing in a valid source name and press Enter; and/or select a source from the (scrollable) filtered list in the dialog.

A route is made from the selected Source to the selected Destination . No ‘Take’ is required.

Note: Enter will execute the route if a valid source has been selected. A mouse click on a source will also execute the route.

509

Routing Control - Bulk Routing Panel

Dial Source and Dial Source-Level Dialogs

Selected

Destination

GV Orbit Client Version 2.0.0

User Guide

Pop-up Dial Source dialog

Type in Source name, or select Source name.

510

Fig. 11-23: Dial Source Dialog

Further routing examples can be found at:

•

Route with Dial Source , on page 514.

Dial Source-Level Dialog

Dial Source-Level is a quick way of selecting a Source and a Level for a destination and routing it. By default, the Dial Source-Level dialog shows the currently-routed Source and

Source-Level.

With a Destination and a Destination Level selected, type a single alpha-numeric character to display the default Dial Source-Level dialog.

A Source may then be found by starting to type a source name. As the Source name is typed, the Sources listed in the dialog are filtered.

After a valid Source has been highlighted, press Tab to select a valid Source Level and a route can be made by pressing the Enter key.

Routing a level from a different source to a destination forms a breakaway (see Breakaway and Levels

). Routing a different level from the same source forms a shuffle (see Shuffle and

Levels

Example

To see and use the Dial Source-Level dialog:

1 Select a Destination .

2 Select one or more Destination Levels .

3 Type a single alpha-numeric character.

A default Dial Source-Level dialog pops up and shows the currently-routed Source

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Dial Source and Dial Source-Level Dialogs

name and Level. (See Figure 11-24.)

( Note: It is assumed that level-based routing is required.)

Selected

Destination

Selected

Destination

Levels

Pop-up dialog

Dial Source-Level

Type in a valid Source name; and press Tab key to toggle focus to Levels.

Type in Level name; and/or select Level name.

Fig. 11-24: Dial Source-Level Dialog

4 If a different Source Name is required, begin to enter the required Source name.

The list of Source names is filtered on the typed text.

5 Either:

• continue typing in a valid Source name (but do not press the Enter key); or

• highlight a Source name in the list (do not select it).

6 When the required (and valid) Source name is in the upper text box of the dialog,

press the Tab key. (See Figure 11-24.)

This toggles focus from ‘Sources’ to ‘Levels’; the filtered list changes to listing Levels.

Note: To clear a ‘dial-up’ dialog before making a route, click the ESC key.

7 Type in the Level name required and press Enter; and/or select the Level from the filtered list in the dialog.

A route is made from the (one) selected Source Level to the selected Destination

Level(s) . No ‘Take’ is required.

511

Routing Control - Bulk Routing Panel

Dial Source and Dial Source-Level Dialogs

GV Orbit Client Version 2.0.0

User Guide

Note: Enter will execute the route if a valid source and level has been selected. A mouse click on a source or source level will also execute the route.

Further routing examples can be found at:

•

Quick Breakaway with Dial Source-Level , on page 525.

•

Quick One-Level Shuffle with Dial Source-Level , on page 531.

512

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Bulk Routing Panel Operation

Make a Simple Route

To make a simple route:

1 Select a Destination .

The source currently routed to the selected destination is automatically highlighted in the Source Grid.

2 Select a Source to be routed to the selected destination.

See Figure 11-25.

Click Take to make route

Before a Take , the Levels Grids show level information for the selected source and destination.

Fig. 11-25: Make a Route Example - Before TAKE.

3 Click Take . (Click Cancel , to deselect the source/destination.)

The selected source (all of its levels) is routed to the selected destination. See Figure 11-

26.

513

Routing Control - Bulk Routing Panel

Route with Dial Source

GV Orbit Client Version 2.0.0

User Guide

After the TAKE, the new source of the destination and its levels is shown in the Destination Grid and

Destination Levels Grid .

Fig. 11-26: Make a Route Example - After TAKE.

Simple Route - Alternative Method

Also, to make a route, the source may be selected first:

1 Select a Source .

2 Select a Destination .

3 Click Take .

Route with Dial Source

See

Dial Source Dialog , on page 509, for more information. To make a simple route:

1 Select a Destination .

2 Begin to type in a Source name.

A Dial Source dialog pops up.

3 Continue typing in a source name and press Enter; and/or select a source from the (scrollable) filtered list in the dialog.

A route is made from the selected Source to the selected Destination . No ‘Take’ is required.

514

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Route One Source to Multiple Destinations

One to many.

Note: The Bulk Routing Panel may be operated with a mouse, or using keyboard shortcuts, or by using a mixture of both.

To route a single source to multiple destinations:

1 Select a Destination by clicking on the destination selection button.

(Equivalent keyboard shortcuts = cursor arrow keys and space-bar.)

2 Select a second Destination by CTRL + clicking on a destination button.

(Equivalent keyboard shortcuts = cursor arrow keys and CTRL-Space-Bar.)

3 Select further destinations with CTRL + click.

A selection of destinations has been made.

Note: Alternatively, a range selection may be made by:

• Selecting the first destination; and then

• SHIFT-selecting the last one.

This selects a sequential range of destinations, from first to last.

When all destinations have been selected:

4 Select a Source .

(Equivalent keyboard shortcuts:

Change to Source grid = CTRL-Cursor arrow keys.

Select Source = cursor arrow keys and space bar.)

5 Click Take .

(Equivalent keyboard shortcuts = Enter.)

The selected source is routed to all selected destinations.

One Source to Multiple Destinations - Alternative Method

Alternatively, the source may be selected first:

1 Select a Source .

2 Make a selection of Destinations (by CTRL-clicking, or SHIFT-clicking, or a combination).

3 Click Take .

515

Routing Control - Bulk Routing Panel

Route Multiple Sources to Multiple Destinations

GV Orbit Client Version 2.0.0

User Guide

Route Multiple Sources to Multiple Destinations

May to many.

To route multiple sources to multiple destinations:

1 Select a Destination by clicking on the destination selection button.

2 Select a second Destination by CTRL + clicking on a destination button.

3 Select further destinations with CTRL + click.

Note: Alternatively, a range selection may be made by:

• Selecting the first Destination; and then

• SHIFT-selecting the last one.

This selects a range, from first to last.

When all destinations have been selected:

4 Select a Source by clicking on the source selection button.

5 Select a second Source by CTRL + clicking on a source button.

6 Select further sources with CTRL + click.

Note: Alternatively, a range selection may be made by selecting the first

Source and then SHIFT-selecting the last one. This selects a range, from first to last.

Note: Select the same number of sources as there are selected destinations.

A reminding, pop-up notification message will appear.

7 Click Take .

The source is routed to all selected destinations.

Multiple Sources to Multiple Destinations - Alternative Method

Alternatively, the source may be selected first:

1 Select multiple sources.

2 Select multiple destinations.

3 Click Take .

Multiple Selection Type and Routing Order

Routing multiple Sources and/or multiple Destinations requires a selection of Sources and of Destinations to be made. This can be done as:

• a selection of multiple items (see

Select Multiple Items (CTRL select) , on page 498); or

• a range selection of multiple items (see

Select a Range of Items (SHIFT select) , on page 498).

The selection order is different in each case and affects routing order.

516

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

What is Copy-and-Paste Routing?

CTRL-Selection Type Order

When routing multiple sources to multiple destinations and selecting multiple items with

CTRL-clicks (that is, not by using a range selection), then the order of selection is significant and affects the order in which routing is done.

For example, to route sources 1 to 8 to destinations 8 to 1:

• Select sources 1 to 8 by CTRL-clicking on each source button in the order 1 to 8.

• Select destinations 8 to 1 in that order by CTRL+clicking on each destination button in the order 8 to 1.

• Click Take .

SHIFT-Selection (Range) Type Order

When routing multiple sources to multiple destinations and using a selection range (a selection made with ‘SHIFT’), then selection order is from the first to the last item of the range, in the order that the items (Source or Destination buttons) are shown. This is the routing order used.

What is Copy-and-Paste Routing?

Copy and paste allow routing information from one destination to be copied onto another destination. The Copy and Paste controls are in the Destination Grid tool bar.

Copy

Paste

Fig. 11-27: Destination Grid Copy and Paste Controls

To Perform Copy-and-Paste Routing

1 Select a Destination .

2 Click the Copy icon in the tool bar of the Destination Grid , or press ‘CTRL +C’.

The copy-selected Destination is shown highlighted with a ‘crawling’, dashed outline.

See Figure 11-28.

517

Routing Control - Bulk Routing Panel

What is Copy-and-Paste Routing?

GV Orbit Client Version 2.0.0

User Guide

‘Copy-Selected’ Destination

Fig. 11-28: Copy-Selected Destination

Then:

3 Select a different Destination (the one to copy to).

4 Click the Paste icon, or press ‘CTRL + V’.

The routing of the first destination is applied to the second destination and a route is made automatically. The routing done is ‘all-levels’.

The copy-selection is still selected (the dashed outline indicates this), so further pastes can be made. To paste the same to further Destination(s):

5 Select a Destination (or select multiple destinations) and click on the Paste icon (or press ‘CTRL-V’.)

6 Repeat for any further Destinations.

Finally:

7 To clear the copy selection, press ESC. (This can be done at any time.)

518

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

What is Copy-and-Paste Series Routing?

Paste Series fills a range of Destinations with a consecutive series of Sources .

To Perform Copy-and-Paste Series Routing

1 Select a Destination .

2 Click the Copy icon, or press ‘CTRL +C’.

The routing information of the selected destination is copied.

3 Select a range of Destinations .

4 Click the Paste Series icon, or press ‘SHIFT + V’.

Paste Series icon

Fig. 11-29: Paste Series Icon

The routing of the first, ‘copy-selected’ destination is applied to the first destination in the selected range.

The next sequential source is routed to the next destination in the range and so on.

Routing is done automatically (no Take required).

Paste Series Example

1 Select destination 1 and click Copy .

2 Select destination range 11 up to 19 . (Select first and Shift-select last.)

3 Click Paste Series .

The following routing is done:

Source 1 to destination 11 , source 2 to 12 , 3 to 13 , 4 to 14 , ... , 9 to 19 .

Note: The rules of selection type and order apply. See

Multiple Selection

Type and Routing Order , on page 516.

519

Routing Control - Bulk Routing Panel

What is Quick 1-to-1 Routing?

GV Orbit Client Version 2.0.0

User Guide

What is Quick 1-to-1 Routing?

Quick 1-to-1 routing can be used to make 1-to-1 routes quickly. This can be useful at system set up. For example, for the first 100 sources routed to the first 100 destinations.

To Perform Quick 1-to-1 Routing

To make a set of quick 1-to-1 routes:

1 Select destination 1 , select Source 1 , and click Take .

This routes the first destination.

2 Click Copy .

Destination 1 ’s routing information is copied.

3 Select destination range 1 to 100 . (Select first and Shift-select last.)

4 Click Paste Series .

The following routing is done:

Source 1 to 1 , source 2 to 2 , 3 to 3 , ... , 99 to 99 , and 100 to 100 .

This has quickly copied Sources to all selected Destinations.

520

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Destination Protect

What is Destination Protect?

When a destination is protected by a user, users of other types of routing control panel cannot route to it.

This means that users of Bulk Routing Panels in GV Orbit Clients would be able to route to a destination protected by another such Bulk Routing Panel. But hardware panel users would not be able to route to a destination protected by a Bulk Routing Panel. (And vice versa.)

To Protect a Destination

1 Select a Destination.

2 Click the Protect button in the Router Control pane.

The destination is protected.

Protect button

Protected

Destination, selected

A Protected

Destination, not selected

Selected

Destination’s levels are also shown as protected

Fig. 11-30: Protected Destination

To Un-Protect a Destination

1 Select the protected destination.

2 Click the Release button in the Router Control pane.

The destination protection is removed from the selected destination.

521

Routing Control - Bulk Routing Panel

Destination Lock

What is Destination Lock?

When a destination is locked, it cannot be routed to by any user.

To Lock a Destination

1 Select a destination.

2 Click Lock in the Router Control pane.

The destination is locked.

Lock button

Selected

Destination, Locked

GV Orbit Client Version 2.0.0

User Guide

Locked

Destination’s levels are also shown as locked

Fig. 11-31: Locked Destination

To Unlock a Destination

1 Select the locked destination.

2 Click the Release button in the Router Control pane.

The destination lock is removed from the selected destination.

522

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Breakaway and Levels

What is a Breakaway?

A ‘breakaway’ occurs when all levels of a destinations do not come from the same source.

This is also referred to as the destination being ‘unmarried’.

Breakaway example shown:

Two audio channels of Destination B (A1 and A2) are obtained from a different source (Source C).

Fig. 11-32: Breakaway

Destinations which are ‘unmarried’ are indicated with a breakaway icon (Figure 11-33c) on

the destination button.

523

Routing Control - Bulk Routing Panel

Perform a Breakaway

GV Orbit Client Version 2.0.0

User Guide

Perform a Breakaway

To perform a breakaway:

1 Select a Destination .

2 Select the Destination Levels to make a route to (for example, audio channels A1 and

A2). (See Figure 11-33a.)

3 Select a new Source .

4 Click Take .

The corresponding levels of the selected source are routed to the selected destination

levels and a breakaway is formed. Figure 11-33b shows the breakaway result.

2 a) Before TAKE:

• Destination MV10-9 is currently all routed from source

S10-9

(as shown in the Destination Levels Grid ).

• Destinations levels A1 and A2 are selected.

• S10-18 is the currently-selected source.

b) After TAKE:

• Destination MV10-9 is routed partly from source S10-9 and partly from S10-18 (levels A1 and A2).

• This breakaway situation is indicated with a Breakaway icon on the destination button.

• The source of each destination level is shown in the

Destination Levels Grid .

c) Breakaway icon on button

Fig. 11-33: Breakaway Example: a) Before TAKE; b) After TAKE; c) Breakaway Icon on

Button.

524

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Quick Breakaway with Dial Source-Level

Breakaway - Alternative Method

Also, to perform a breakaway, the source may be selected first:

1 Select a Source .

2 Select a Destination .

3 Select the Destination Levels to route.

4 Click Take .

Note:

A ‘breakaway’ occurs when not all of a destination’s levels are selected for routing.

This can also happen if a source with fewer levels than the selected destination is routed, this will result in a ‘breakaway’ (without selecting destination levels).

Quick Breakaway with Dial Source-Level

A quick single-level breakaway method uses the

Dial Source-Level Dialog

To perform a quick video-level breakaway:

1 Select a Destination .

2 Select a Destination Level

. (See Figure 11-34.)

Selected Destination

Selected Video Level

Fig. 11-34: Selected A Destination and a Level

3 Type a single alpha-numeric character.

A default Dial Source-Level dialog box appears showing the currently-routed Source and Level.

525

Routing Control - Bulk Routing Panel

Quick Breakaway with Dial Source-Level

GV Orbit Client Version 2.0.0

User Guide

4 Begin to type a (new) Source name at the keyboard.

(For example, type “s” or “S” if source names begin with “S” - “S10-10”, “S10-11”, etc.)

A Dial Source-Level

dialog box appears. See Figure 11-35.

Type Source name

Source name text entry box

Level text entry box

Fig. 11-35: Dial Source-Level Dialog

5 Type the new Source name into the dialog box. But do not press the Enter key yet.

6 When the Source name is typed, press the Tab key.

This toggles focus from ‘Sources’ to ‘Levels’ and to the lower dialog text entry box.

526

Press Tab key to toggle focus to the Level text entry box

Typed in source name

Fig. 11-36: Source and Level are Dialed-up

7 Type in the Level name, for example “V” and press the Enter key when done.

Or select a level from the filtered list.

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Quick Breakaway with Dial Source-Level

The route is made, connecting the dialed-up Source Level to the selected Destination

Level and forming a breakaway. See Figure 11-37.

Video Level sourced from a different source. (Breakaway)

(Level sources:

‘Video’ - now from S10-111,

‘other’ - unchanged, S10-10.)

Fig. 11-37: Resulting Video Level Breakaway

Use this method to set up any breakaways (or shuffles, see

Quick One-Level Shuffle with

Dial Source-Level , on page 531) required.

527

Routing Control - Bulk Routing Panel

Shuffle and Levels

GV Orbit Client Version 2.0.0

User Guide

Shuffle and Levels

What is a Shuffle?

A destination is said to be ‘shuffled’ when one of its levels is routed from another level of the same source . For example, destination audio channel 5 from source audio channel 4. When this occurs, the Bulk Routing Panel indicates a ‘shuffled’ destination with a Shuffle icon on the destination button.

Shuffle example shown:

Audio channels of Destination B (A1 and

A2) are obtained from a source (Source

A) but not all levels are mapped “1 to 1”.

A source is routed to a destination and audio channels are ‘shuffled’ around; they are not routed ‘1-to-1’.

Fig. 11-38: Shuffles

To Perform a Shuffle

1 Select a Destination .

2 Select the Destination Levels .

For example, in Figure 11-40a, levels A1, A2, A3 and A4 are selected

in that order .

3 Select a Source .

4 Now select the Source Levels in the order in which they shall apply to the destination

Levels.

For example, in Figure 11-40a, levels A4, A3, A2 and A1 are selected

in that order .

Note: Selecting just one source level will route this to all selected destination levels.

Otherwise select the same number of source levels as destination levels. A notification prompt appears at the bottom of the GV

Orbit Client window, reminding the user to select source levels

(see Figure 11-39).

528

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

To Perform a Shuffle

Notification prompt.

Fig. 11-39: Select Levels Notification

5 Click Take .

The selected source levels are routed to the selected destination levels and a shuffle is

formed. Figure 11-40 shows a shuffle example reversing the order of the four audio

channels (A1 to A4).

529

Routing Control - Bulk Routing Panel

To Perform a Shuffle

GV Orbit Client Version 2.0.0

User Guide

4 2 a) Before TAKE:

• Destination MV10-9 is currently all routed from source

S10-9

(as shown in the Destination Levels Grid ).

• Destinations levels A1 , A2 , A3 and A4 are selected.

• Source S10-9 is selected.

• Source Levels A4 , A3 , A2 and A1 have been selected

(in that reversed order).

b) After TAKE:

• Destination MV10-9 is still all routed from source S10-9 .

• This ‘shuffled’ situation is indicated with a Shuffle icon on the destination button.

• The source of each destination level is shown in the

Destination Levels Grid .

In particular, the destination’s A1, A2, A3 and A4 are now routed from A4, A3, A2, and A1 respectively.

c) Shuffle icon on button

Fig. 11-40: Shuffle Example: a) Before TAKE; b) After TAKE; c) Shuffle Icon on Dest. Button.

530

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Quick One-Level Shuffle with Dial Source-Level

To shuffle (route) one level using the Dial Source-Level Dialog :

1 Select a Destination .

2 Select a Destination Level .

A Destination and one Level are now selected.

3 Type a single alpha-numeric character.

A default Dial Source-Level dialog appears and showing a filtered list of source names.

The currently-routed Source and Level are shown.

Do not click; do not press Enter at this time.

Note: The currently-routed Source name is shown in the default dialog.

4 Press the ‘ Tab ’ key.

Focus then moves (toggles) from Source to Levels in the dialog.

Current Source routed to selected Destination

Selected Destination

Dial Source-Level dialog

Source name

Selected Source Level

Selected Destination Level

Fig. 11-41: Dial Source-Level Dialog

5 Type in a new Level name and press Enter, or select a new Level item in the filtered list, click to select.

A route is performed, connecting the selected Source Level to the selected Destination

Level. A shuffle is made, see Figure 11-42.

531

Routing Control - Bulk Routing Panel

Quick One-Level Shuffle with Dial Source-Level

GV Orbit Client Version 2.0.0

User Guide

Shuffle now made, audio level A11 at destination comes from audio level A7.

Fig. 11-42: Shuffle Routed

Note: Using this method, one Source Level can be routed to one or more

Destination Levels.

Use this method to set up any shuffles (or breakaways, see

Quick Breakaway with Dial

Source-Level , on page 525) required.

532

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Filtering

What is Bulk Routing Panel Filtering?

Most grids/panes of the Bulk Routing Panel have a filter control on their tool bar. The filters control what items are shown in the grid/pane. Filters can be applied to the

Source/Destination grids, the Level Selection grids and the Salvos pane. Custom filters can be created and applied. For destinations, filtering can also be by (routed) source.

By default, level filtering is set up to show the usual video and audio levels.

Note: Filtered Lists:

When a filter is applied, a filtered (reduced) set of items is shown in a grid/pane.

Subsequent actions, such as ‘select all items’ or ‘selecting a range’, then all operate on the filtered items shown and not on the full list of items.

What are the Filter Controls in a Bulk Routing Panel?

Each grid/pane contains a similar filter text box and icon. These access a filter items list (also accessed by typing Ctrl-F when in a grid/pane), and filter options menu respectively.

Filter search text box Click the Filter icon to show the Filter options menu.

a) Filter Controls - Text Entry Box

Destination Grid’s Filter options menu b) Filter Drop-Down Menu

Filter items list c) Filter Drop-Down Menu - for the Destination Selection Grid

Note: The default ‘Levels’ filter list shows one video level and 16 audio channels.

d) Levels Grid Filter Default

Fig. 11-43: Filter Controls: a) Filter Text Entry Box; b) Filter Drop-Down Options Menu; c) Drop-Down Menu for Destination Grid; d) Level Grid Filter Items List (Default).

533

Routing Control - Bulk Routing Panel

Filtering Actions

GV Orbit Client Version 2.0.0

User Guide

Filtering Actions

Simple Filtering by Name

To simply filter items in a grid or pane by name:

1 Select the Filter text entry box.

2 Enter a filter search term into the Filter text box.

For example, type ‘S11’ to only show source names starting with ‘S11’.

As the filter search term is typed, the number of displayed items in the Grid/Pane is reduced (filtered). The reduced number of items gives a preview of the filter’s action.

3 To abort the filter set up, press the ESC key.

4 When the required filtering is reached, press the Return/Enter key to apply the filter.

The filter has been applied to the grid. Then only filtered items are shown in the grid/pane, with names which contain the search term.

Filter search term

534

Fig. 11-44: Example of Simple Filtering Applied to a Grid/Pane (Search Term = “S11”)

Clear Applied Filtering in a Grid/Pane

To clear filtering that has been applied in a grid or pane:

1 Either:

• click on the Filter icon ( ) in the grid/pane’s tool bar; or

• in the Filter text entry box, press the Tab key.

And then select ‘Clear Filter’.

The filtering is removed and all grid/pane items are shown.

The filter search term is also cleared and the Filter items drop-down list is shown.

2 At this point, a new search term may be entered.

Or the filter clearing action can be aborted by pressing the ESC key.

If no further filter set up is required:

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Filtering Actions

3 Press the Enter/Return key to remove the Filtering and the Filter items drop-down list.

Set Level Filtering in a Grid/Pane

To set any applied Level filtering back to its ‘default’:

1 Either:

• click on the Filter icon ( ) in the Level grid/pane’s tool bar; or

• in the Filter text entry box, press the Tab key,

And select ‘Video, Audio 1 to 16’.

Select ‘Video, Audio 1 to 16’

Fig. 11-45: Set Level Filtering to Default

Any filtering is replaced by the default ‘Video, Audio 1 to 16’ filtering and the filter search term reflects this.

Fig. 11-46: Level Filtering Default

2 Press Enter to apply this change (or press ESC to cancel this filter change).

Fig. 11-47: Level Filtering Default Applied

535

Routing Control - Bulk Routing Panel

Filtering Actions

GV Orbit Client Version 2.0.0

User Guide

Dynamic Filtering By Name

Filter search term List of names containing the search term (scrollable).

a) Enter Search Term and Select b) Selected Item(s) Displayed

Fig. 11-48: Dynamic Filtering (Source Names Example): a) Enter Search Term and Select. b) Selected Item Displayed

To dynamically filter items by their name:

1 Enter the filter search term into the Filter text box.

GV Orbit looks for names which contain the filter search term.

A drop-down, scrollable filtered list of names is presented.

The list dynamically changes with the search term.

2 Find a name in the list by scrolling through the items.

(Use a mouse wheel, the scroll-bars, or up/down arrow keys to scroll through the list.)

3 Select an item.

(Click on it, or press the Return/Enter key when item is highlighted.)

The result of the selected filter item is shown in the grid.

536

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Filtering Destinations by Source

Filtering of items by their names has been described so far. The filtering is extended for

Destinations to enable Destination names to be filtered by the names of the sources that are routed to them. The filter drop-down menu of the Destination Grid contains an extra item, for this, ‘Filter by Source’.

1 In the Destination Grid, click on the Filter icon ( ) and select Filter by Source .

‘Filter by Source’ is selected

Fig. 11-49: Filtering of Destinations by Source is Enabled

2 Enter a search term in the Filter text box.

Filter search term.

Fig. 11-50: Filter Destinations by Source

3 Press the Enter/Return key to apply the filtering.

With the Filter by Source option selected, the Destination Grid will show only destinations which have a filter-matching source routed to them.

537

Routing Control - Bulk Routing Panel

Preset Level Filters

GV Orbit Client Version 2.0.0

User Guide

Search term

‘Filter by Source’ is selected

Destinations shown have

Source names matching the filter search criteria.

Fig. 11-51: Example Destination ‘Filter by Source’

Preset Level Filters

The Source Level and Destination Level grids offer some preset filters to filter audio/video levels. For example, ‘Video, Audio 1 to 16’ which is for video and 16 audio channels. This preset filter is listed in the drop-down Filter items list, along with the names of the items

(levels).

Custom Filters

What is a Custom Filter in a Bulk Routing Panel?

GV Orbit allows more complex and custom filters to be created. This can be done for any of the filterable grids/panes.

A custom filter can be:

• Created, given a name and saved.

• Edited or deleted.

• Re-named.

A custom filter is applied by entering the start of the custom filter name into the filter text box. The custom filter name will appear in the Filter items drop-down list for selection.

Select the custom filter name to apply it.

Custom filters are stored in the GV Orbit Routing service for the currently-logged-in GV

Orbit user. In this way, the filter will be available to the same user on other machines.

Note: Custom filters will not be seen by other users on other machines.

What is a Custom Filter Rule?

Filter expressions can be defined and combined together to form complex filter conditions, filter rules. The filter rule of a custom filter is designed in a Filter dialog.

538

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Custom Filtering

Expressions can be combined to make rules by ANDing and ORing them together:

• AND - filter condition is met if both filter expressions are satisfied.

• OR - filter condition is met if either filter expression is satisfied.

Custom Filtering

Creating a Custom Filter

In a grid/pane:

1 Click on the Filter tool bar icon and select ‘Create Filter’.

An empty Filter

dialog is shown. See Figure 11-52.

Custom filter rule to be defined here.

Fig. 11-52: Filter Dialog

2 Enter a Filter name for the filter.

Filter name entered

Fig. 11-53: Saving New Custom Filter

3 Click Save .

A new Custom Filter has been created.

539

Routing Control - Bulk Routing Panel

Custom Filtering

GV Orbit Client Version 2.0.0

User Guide

Selecting a Custom Filter

A Custom Filter is listed in the drop-down Filter items list:

1 In the Filter text box, start to type the name of a Custom Filter .

The Filter items drop-down list contains the Custom Filter name.

Select a Custom Filter name

Fig. 11-54: Custom Filter in Filter Items List

Constructing the Rules for a Custom Filter

See

Filter Dialog and Custom Filter Rules , on page 542, for adding filter rules with the dialog

to construct the filter.

To Edit an Existing Custom Filter

1 Click on the Filter tool bar icon and select Edit Filter .

A Custom Filter name a) Select Edit Filter name b) Select which Custom Filter to Edit

Fig. 11-55: Select Custom Filter to Edit

2 Select the filter to edit from the list shown. (See Figure 11-55b.)

The Filter dialog is shown for the selected custom filter.

540

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Custom Filtering

To Delete a Custom Filter

1 Click on the Filter tool bar icon and select Delete Filter .

2 Select the filter to delete from the list shown.

The filter is deleted when the selection is made.

541

Routing Control - Bulk Routing Panel

Filter Dialog and Custom Filter Rules

GV Orbit Client Version 2.0.0

User Guide

Filter Dialog and Custom Filter Rules

The filter rule of a custom filter is designed in the Filter

dialog (see Figure 11-56). A rule is

formed from the logical combination of filter expressions. Expressions can be ANDed or

ORed together and complex AND/OR configurations can be defined for a custom filter:

• AND - filter condition is met if both filter expressions are satisfied.

• OR - filter condition is met if either filter expression is satisfied.

A worked example is given ( Example Custom Filter , on page 543) which shows how to

construct Filter rules with the Filter dialog.

Click to Add Expression item under an AND/OR item.

Custom Filter name (editable)

Click to Add AND/OR item under an AND/OR item.

Logical AND/OR combination item

Defines the logical

AND/OR structure

Delete AND/Or item and items beneath it .

Delete Expression item

AND/OR item

Expression item

Select the target of the expression,

(Destination) ‘Name’ or ‘Source’

Enter operand

Operator, see Table 11-3

Click to save the custom filter and close the dialog.

Click to apply custom filter.

Fig. 11-56: Filter Dialog - Custom Filter Example

Logical AND / OR Combining

The Custom Filter being designed must be expressible in the form of a logical expression so that it can be captured in the Filter dialog.

A rule might be designed to filter:

• destination names that both start with a ‘C’ and contain a ‘6’.

• destination names that either end with a ‘4’ or end with a ‘5’.

• destinations whose source names start with ‘Cam’.

• destinations whose names end with a ‘X’ and whose source names are ‘Cam12’.

542

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Example Custom Filter

Filter Expressions

An expression tests a Destination Name or Source Name with an operator and an operand.

Filter Expression Operators

The operators include:

Table 11-3: Operators - Name/Source and Operand

Operation

Equals

Not Equals

Name matches.

No match.

StartsWith

EndsWith

Contains

NotContains

Starts with the operand.

Ends with the operand.

Contains the operand.

True when...

Does not contain the operand.

Greater Than

Less Than

GreaterThanEqual

LessThanEqual

Numerical part of name is greater than the operand.

Numerical part of name is less than the operand.

Numerical part of name is greater than or equal to the operand.

Numerical part of name is less than or equal to the operand.

Example Custom Filter

This section explains

What the Filter Should Do

and Defining the Custom Filter Example via

the Filter dialog.

What the Filter Should Do

“Display two destinations only if they have certain sources currently routed to them.“

(Destinations Mon1 and Mon2 and sources Cam1 and Cam2 are used in this example.)

The filter for this example may be written:

“Show a destination if the destination name is Mon1 or Mon2 , and its routed source name is Cam1 or Cam2 .”

This may be written out to show its logical expression structure.

Show a destination if the following is true:

Destination name is Mon1

Destination name is Mon2

AND its routed Source name is Cam1

OR its routed Source name is Cam2

543

Routing Control - Bulk Routing Panel

Example Custom Filter

GV Orbit Client Version 2.0.0

User Guide

Defining the Custom Filter Example

This example Custom Filter filter may be entered into the Filter dialog as follows:

1 Click on the Destination Grid’s Filter tool bar icon and select Create Filter .

An empty Filter

dialog is shown. See Figure 11-52 on page 539.

2 Enter a Filter Name for the filter.

3 Select AND as the first (top-level) logical combination item with the drop-down menu

button. See Figure 11-57.

Filter Name entered

Fig. 11-57: Select AND

4 Click the Add AND/OR icon.

An indented AND/OR item appears.

An expression item also appears below the OR. See

Figure 11-58.

5 Select OR as the new, indented logical combination item.

Expression item

Fig. 11-58: Select OR

6 Click the new Add Expression icon.

A second expression item appears

under the OR. See Figure 11-59.

Fig. 11-59: Added a Second Expression Item

7 Click the first Add AND/OR icon again.

This add a second OR logical combination item

indented under the AND. See Figure 11-60.

Second expression item

544

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Example Custom Filter

Fig. 11-60: Second OR Logical Combination Item Added

8 Add a second expression item under the new OR item. See Figure 11-61.

Operator

Fig. 11-61: Second Expression Item Added

The basic ‘AND-OR-OR’ logical combination structure for the example has now been entered for the Filter rule.

The next step completes the expression item and saves the filter:

9 Set up the expressions as shown in Figure 11-62.

Filter Name

Expressions

Fig. 11-62: Completed Custom Filter

10 Click Save in the Filter dialog to save the custom filter and close the dialog.

Custom filter rules have been entered; the Custom Filter has been created, ready to use.

See

Using a Custom Filter .

545

Routing Control - Bulk Routing Panel

Example Custom Filter

GV Orbit Client Version 2.0.0

User Guide

Using a Custom Filter

To use the custom filter ‘My Custom Filter 1’:

1 Start entering the custom filter name into the Filter text box.

(‘My’ in this example.) A list of possible matching custom filters is presented.

Fig. 11-63: Select Custom Filter

2 Select the ‘My Custom Filter 1’ item.

The filter is applied.

In this example, only destinations ‘Mon1’ or ‘Mon2’ are shown if they have sources

‘Cam1’ or ‘Cam2’ routed to them. See Figure 11-64.

(The Custom Filter displays only destinations

‘Mon1’ and ‘Mon2’ - which happen to be locked.)

Fig. 11-64: Applied Custom Filter

To clear the filtering:

3 Click on the Filter tool bar icon and select Clear Filter .

546

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Salvos

What is a Salvo?

Salvos are created and defined in Grass Valley’s GV Orbit product and are available to the

Bulk Routing Panel through the GV Orbit Routing service that the Bulk Routing Panel is connected to.

Salvos are shown in the Salvos pane of the Bulk Routing Panel. The list of Salvo names can be filtered using the tool bar controls. Filters can be set up in a similar way to the other grids/panes of the Bulk Routing Panel.

Fig. 11-65: Salvos Pane with Salvo Buttons

Executing Salvos

To Execute a Salvo

Either:

• double-click on the Salvo button; or,

• select the Salvo button (single-click) and click Take .

To Execute multiple Salvos

1 Select the first Salvo .

2 Select other Salvos with CTRL-click.

3 Press Take .

547

Routing Control - Bulk Routing Panel

Hide Sources

GV Orbit Client Version 2.0.0

User Guide

Hide Sources

What is the Hide Sources Mode?

In Hide Sources mode, the Source Selection and Source Level Selection grids may be hidden from view. Thus displays more destinations are shown to the user.

The Hide Sources icon in the Destination Grid’s tool bar enables this mode.

Fig. 11-66: Hide Sources Icon in Destination Grid Tool Bar

Enter Hide Sources Mode

Toggle Hide Sources on/off by:

• Click the Hide Sources icon in the Destination Selection grid tool bar.

The Bulk Routing Panel hides the Sources and more Destinations are shown. See

Figure 11-67b on page 549 .

Routing in Hide Sources Mode

Use the Dial Source or Dial Source-Level facility to route source signals and/or levels to

destinations. See Dial Source Dialog , on page 509 and

Dial Source-Level Dialog , on page 510.

548

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Routing in Hide Sources Mode a) Sources Shown b) Hide Sources

Fig. 11-67: Bulk Routing Panel: a) Sources and Destinations Shown; b) Hide Sources.

549

Routing Control - Bulk Routing Panel

List View

GV Orbit Client Version 2.0.0

User Guide

List View

What is List View Mode?

List View is a level-centric view of a Bulk Routing Panel, allowing a user to focus on routing to Destination Levels. List View hides Sources and Source Levels and presents all of the destinations in a ‘list’ format; each list item is a Destination with all of its Levels.

Figure 11-68a shows a normal Bulk Routing Panel view and Figure 11-68b shows a

List

View .

Click icon to toggle between views a) Normal Bulk Routing Panel View

Destination Levels Grid

Focus is on

Destinations

List b) List View

Fig. 11-68: Bulk Routing Panel: a) Normal View; b) List View

550

Scrollable list of destinations

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Selection in List View

Focus between the Destination and Destination Levels sections can be moved with the

CTRL-Cursor-arrow-keys, as usual. Focus is shown with a thin blue bounding box.

List View Tool Bar

The List View tool bar is an amalgamation of the tool bars of the normal Destination pane and Destination Level grid of a Bulk Routing Panel. Icons may be grayed-out according to

panel focus. See Figure 11-69.

Icons, some may be grayed-out depending on panel focus.

Two filter boxes, for Destination filtering and Destination Level filtering

Fig. 11-69: List View Tool Bar

Destination Filtering

There are two filter boxes and these are for: Destination filter and Destination Level filter.

See Figure 11-69.

List View presents all of the destinations in a scrollable list. To aid selection of destinations and levels, and navigation of the list, the filter facility can be used to limit what is listed:

• Destination filtering may be done by name or by their routed Source.

• Destination Level filtering may be done by Level name.

See

Filtering , on page 533, for more information about using the filter facility.

A filter may be invoked by pressing CTRL-F according to where your panel focus is. In List

View, with panel focus on:

• the Destination column, then CTRL-F invokes Destination filter; or on

• the Level grid, then CTRL-F invokes Destination Level filter.

Selection in List View

Select a Destination

1 Click on a Destination.

(Or move focus to the level with the cursor keys and press Space-Bar.)

All of the destination’s levels are automatically selected.

551

Routing Control - Bulk Routing Panel

Selection in List View

GV Orbit Client Version 2.0.0

User Guide

Select a Destination, then all Levels are selected

Fig. 11-70: Select a Destination

Select Multiple Destinations

1 Click on a Destination to select it.

(Or move focus onto the Destination with the cursor arrow keys and press the Space-

Bar key.)

2 CTRL-click to add other Destinations.

(Or focus on another Destination and press CTRL-Space-Bar.)

Alternatively or additionally, SHIFT-select can be used when selecting a range.

Select a Destination Level

1 Click on a Destination Level.

The Level is selected and the Destination is selected automatically. No other Levels are selected.

Select a Level, then the Destination is selected.

Fig. 11-71: Select a Destination Level

Select Multiple Destination Levels

CTRL-Selecting

1 Select a Destination Level.

2 CTRL-Select other Levels to add further Levels to the selection.

552

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Selection in List View

Select a Level, then CTRL-Select others.

Fig. 11-72: Select Multiple Destination Levels

SHIFT-Selecting a Range of Destination Levels

To select a range of Levels:

1 Select the first Level in the range.

(Move button focus onto a Level and click on it, or press Space-Bar.)

2 SHIFT-Select the last Level in the range.

(To move focus from the first Level to the last, use the mouse or use SHIFT-cursorleft/right arrow keys. To select, click or press Space-Bar.)

Levels from the first to the last are selected.

Select the first Level, then SHIFT-Select the last.

Fig. 11-73: Select a Range of Destination Levels

SHIFT-Selecting a Block of Destination Levels

A block of Levels may be selected. This is similar to selecting a range, but it goes across more than one destination. To select a block of Levels:

1 Select the first, ‘top-left’ Level in the block.

2 SHIFT-Select the last, ‘bottom-right’ Level in the block.

Levels from the first selection to the last in a block are selected.

553

Routing Control - Bulk Routing Panel

Routing in List View

GV Orbit Client Version 2.0.0

User Guide

Select the first, ‘top-left’ Level, then SHIFT-Select the last, ‘bottom-right’.

Fig. 11-74: Select a Block of Destination Levels

Selecting Source and/or Source Level

Source and Source Level selection is done via the Dial Source and Dial Source-Level dialup dialog facility. After the required Destination(s) or Destination Level(s) are selected type

in an alpha-numeric character to open one of the dial-up dialogs. (See Dial Source and Dial

Source-Level Dialogs , on page 509.)

For normal routing operation in List View mode, only a single Source or a Single Source

Level can be selected.

Routing in List View

Routing in List View is done by selecting a Destination (and Levels) and then selecting a

Source and Source Levels via the Dial Source and Dial Source-Level facility. (See

Dial

Source and Dial Source-Level Dialogs , on page 509.)

Some Routing examples are provided, see:

•

Routing Examples - ‘All Levels’ , on page 555.

•

List View Routing Examples - One-Level , on page 557.

•

List View Routing Examples - Destination Copy-Paste , on page 562.

•

List View Routing Examples - Copy-Paste Levels , on page 565.

A brief summary of these examples is found at

List View Routing Summary , on page 568.

554

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Routing Examples - ‘All Levels’

Several routing examples are presented:

•

Simple Route, One Source to One Destination (‘All-Levels’) .

•

One Source to Multiple Destinations (‘All-Levels’) .

Routing utilizes the

Dial Source and Dial Source-Level Dialogs

Simple Route, One Source to One Destination (‘All-Levels’)

To make a simple ‘all-levels’ route in List View :

1 Select a Destination.

Fig. 11-75: Destination Selected

2 Begin to type a Source name, for example, ‘S10-’.

A Dial Source dialog appears. Source names are listed in the dialog and are filtered on

the typed text. See Figure 11-76.

Typed in text

Fig. 11-76: Dial Source Dialog

Filtered Source List

3 Continue to type in (‘dial-up’) a Source Name and press Return; and/or select the required Source name from the filtered Source list in the Dial Source dialog. For example, ‘S10-22’.

555

Routing Control - Bulk Routing Panel

Routing Examples - ‘All Levels’

An ‘all-levels’ route is made to the selected Destination.

New source is routed to the destination, all levels.

GV Orbit Client Version 2.0.0

User Guide

Fig. 11-77: Routed All-Levels

An ‘all-levels’ route has been made.

One Source to Multiple Destinations (‘All-Levels’)

To make a simple ‘all-levels’ route from one Source to multiple Destinations:

1 Select the first Destination.

2 CTRL-Select and/or SHIFT-Select other Destinations.

When all Destinations have been selected:

3 Begin to type a Source name, for example, ‘S10’.

A Dial Source dialog appears. Source names are listed in the dialog and are filtered on the typed text.

4 Proceed to ‘dial up’ a Source name, as described in

Simple Route, One Source to One

Destination (‘All-Levels’)

5 Select a Source to make the route.

An ‘all-levels’ route is made to multiple Destinations.

556

GV Orbit Client Version 2.0.0

User Guide

List View Routing Examples - One-Level

Several routing level-based examples are presented:

•

Simple One-Level Route (Breakaway)

•

One-Level Shuffle

•

One Level to Multiple Levels .

Simple One-Level Route (Breakaway)

To make a ‘one-level’ route in List View :

1 Select a Destination Level.

Routing Control - Bulk Routing Panel

List View Routing Examples - One-Level

Fig. 11-78: Destination Level Selected

The corresponding Destination is also selected.

2 Type a single alpha-numeric character.

A default Dial Source-Level dialog appears. User focus is in the (upper, Source-name) text entry box. The dialog shows the currently-routed Source name and Level.

3 Begin to enter a new Source name into the upper text entry box, for example, ‘S11-’.

Source names are listed, filtered on the typed text. See Figure 11-79.

Select a Source, or type in the name fully and press Enter.

Fig. 11-79: Select a Source Name

4 Either:

• select the required Source name in the filtered list; or

• finish entering the Source name into the dialog and press Enter.

557

Routing Control - Bulk Routing Panel

List View Routing Examples - One-Level

GV Orbit Client Version 2.0.0

User Guide

A ‘one-level’ route is made to the selected Destination Level from the selected Source, on the same Level. This forms a Breakaway.

Fig. 11-80: One Level Routed from a Different Source, Breakaway

A one-level, breakaway, route has been made.

558

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

List View Routing Examples - One-Level

One-Level Shuffle

A shuffle is similar to a breakaway and, in List View mode, is routed is a similar way to

Simple One-Level Route (Breakaway)

Note: When a Dial Source-Level dialog first appears, it shows the currently-routed Source and Level. For a Shuffle, the Source name simply needs to remain the currently-routed Source.

(Refer to

What is a Breakaway?

, on page 523, and What is a Shuffle?

, on page 528, for

general information.)

To do a one-level route:

1 Select a Destination Level.

The corresponding Destination is also selected.

2 Type a single alpha-numeric character.

A default Dial Source-Level dialog appears. User focus is in the (upper, Source-name) text entry box. The dialog shows the currently-routed Source and Level.

Note: The default dialog already shows the currently-routed Source name and Level name, regardless of the single alpha-numeric character typed.

3 Press the Tab key.

In the dialog, user focus changes from the (upper Source name) text entry box to the

(lower, Source-Level-name) text entry box.

4 Either:

• begin to type in a (new) Source Level name and then select the required Source

Level in the list (by clicking on it, or by highlighting the Level and pressing the

Enter key); or

• fully type in the Source Level name (for example, ‘A2’) and press the Enter key.

A ‘one-level’ route is made from the selected |Source Level to the selected Destination

Level, which forms a one-level Shuffle in this case.

A one-level shuffle route has been made.

559

Routing Control - Bulk Routing Panel

List View Routing Examples - One-Level

GV Orbit Client Version 2.0.0

User Guide

Channel-Swap Shuffle

To do a channel-swap in List View

, carry out two One-Level Shuffle

routes. See Figure 11-

81.

a) Before one-Level routing b) After first one-Level route

Routed-Source’s channel A3 is routed to Destination’s Channel A2 c) After second one-Level route

Routed-Source’s channel A2 is routed to Destination’s Channel A3, and vice versa

Fig. 11-81: Forming a Channel-Swap Shuffle: a) Before any one-Level routing; b) After first one-Level route; c) After second one-Level route.

One Level to Multiple Levels

To route one Source Level to multiple Destination Levels:

1 Select a Destination Level.

2 CTRL-Select and/or SHIFT-Select other Destination Levels.

( Note: These Levels do not have to belong to the same Destination.)

Figure 11-82a gives an example of multiple selected Destination Levels.

This has selected the Destination Levels required.

Then:

3 Type a single alpha-numeric character.

A default Dial Source-Level dialog appears. User focus is in the (upper, Source-name)

560

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

List View Routing Examples - One-Level text entry box. The dialog shows the currently-routed Source and Level.

Note: The default dialog already shows the currently-routed Source name and Level name, regardless of the single alpha-numeric character typed.

4 Dial-up a Source Level with the Dial Source-Level dialog, see

Simple One-Level Route

(Breakaway) and make a one-Level route to all selected Destination Levels.

Figure 11-82b shows an example with Figure 11-82c showing the resulting route made.

a) Multiple Selected Destination Levels b) Dialing Up the Source Level c) Routed Levels

Fig. 11-82: One Level to Multiple Levels: a) Multiple Selected Destination Levels; b) Dialing Up the Source Level; c) Routed Levels.

561

Routing Control - Bulk Routing Panel

List View Routing Examples - Destination Copy-Paste

GV Orbit Client Version 2.0.0

User Guide

List View Routing Examples - Destination Copy-Paste

With Copy-Paste routing, the Source assignments of a Destination (that is, the current routing to all the Levels of a Destination) can be copied to other Destinations. Alternatively, the routing to just one or more Destination Levels can be copy-pasted to other Destination

Levels.

Several routing Copy-Paste examples are presented:

•

Destination Copy-Paste .

•

Destination Paste-Series

Destination Copy-Paste

The routing to a Destination can be copied to one or more other Destinations. This operates on all levels and allows a routing to be quickly copied to other Destinations:

1 Select a Destination. (See Figure 11-83a.)

2 Copy the Destination by, either:

• CTRL-C; or

• right-click and select ‘Copy’; or

• click on the ‘Copy’ icon in the List View tool bar.

The selected Destination (with its Levels) is outlined with a ‘crawling’ dashed line. (See

Figure 11-83b.)

a) Selected Destination b) Destination Copied

Fig. 11-83: Destination Copy-Paste: a) Selected Destination; b) Destination Copied.

3 Select a Destination to ‘copy to’. (See Figure 11-84.)

562

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

List View Routing Examples - Destination Copy-Paste

Fig. 11-84: ‘Copy’To’ Destination Selected

4 If required, further ‘copy-to’ Destinations can be added to the selection with CTRL-Select and/or

SHIFT-Select.

When all ‘copy to’ Destinations are selected, to paste the ‘copied’ Destination’s routing to the selection:

5 Paste the ‘copied’ Destination’s routing to the selection by either:

• pressing CTRL-V; or

• right-click and select ‘Paste’; or

• click the ‘Paste’ icon in the List View tool bar.

The routes are made (all levels) and the original copied Destination’s routing is applied

(pasted) onto all the selected Destination(s). (See Figure 11-85.)

Fig. 11-85: Routing Pasted onto a Destination

Destination Paste-Series

Destination Copy-Paste applies the copied Destination into all of the selected ‘Copy to’

Destinations. Alternatively, a series of sources can be applied to several selected ‘Copy to’

Destinations. The series starts from the ‘Copied’ Destination’s currently-routed Source and the Source increments.

The operation is similar to Destination Copy-Paste

. To paste a series onto a selection of

‘Copy to’ Destinations:

1 Select a Destination and copy it.

2 Select a first ‘Copy to’ Destination and select a range of these by SHIFT-Selecting the last ‘Copy to’ Destination.

This has selected the ‘Copy to’ range.

563

Routing Control - Bulk Routing Panel

List View Routing Examples - Destination Copy-Paste

GV Orbit Client Version 2.0.0

User Guide

Currently-routed

Source of the copied Destination

Currently-routed

Source applied to first ‘Copy to’

Destination.

Next Source applied to next

Destination.

And so on.

At this point (with a Destination copied and several ‘Copy to’ destinations selected) a normal ‘paste’ would result in the copied routing being applied to all ‘Copy to’ Destinations.

But, instead, to Paste Series :

3 Press Alt-CTRL-V, or click the Paste Series icon in the List View tool bar.

The currently-routed Source of the copied Destination is applied to the first ‘Copy to’

Destination in our ‘Copy to’ range. The next Source is applied to the next ‘Copy to’

Destination in the range, etc. See Figure 11-86 for an example.

Fig. 11-86: Result of Destination Paste-Series

564

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

List View Routing Examples - Copy-Paste Levels

The routing to one or more selected Destination Levels can be copied and pasted onto other Destination Levels. This allows a user to set up levels quickly on one or more

Destinations.

The copy-paste is a two-step process:

1 Copy - Destination Levels are selected and copied.

2 Paste - A paste ‘starting Level’ is selected and pasting is done from this ‘starting Level’.

With more than one Destination Level copied, the pasting of routing onto ‘Copy to’

Destination Levels can be done in two ways:

•

Paste Levels with CTRL-V - pastes with no gaps.

•

Paste Levels with Alt-CTRL-R - pastes preserving gaps.

Both paste types are done in the Levels grid from the ‘starting Level’.

When pasting to more than one ‘starting Level’, a warning is given if there are any pasting conflicts. See

Levels Copy-Paste Footprint

and Levels Paste Warning

Paste Levels with CTRL-V

1 Select Destination Levels and copy them. For example, A3, A4, A6 and A8, see

Figure 11-87.

This has copied the routing of these selected Destination Levels.

2 Select one ‘Copy to’ Destination Level. This is the ‘starting Level’.

And click the Paste icon, or press CTRL-V, or select right-click ‘Paste’.

Routes are made to consecutive Destination Levels and the copied routing is applied to the ‘Copy to’ Destination Level and to subsequent, consecutive Destination Levels.

See Figure 11-87 for the result of CTRL-V paste from the copied Destination Levels.

One selected ‘Copy to’ Level,

‘starting Level’

Selected Destination Levels

Fig. 11-87: Result of CTRL-V Paste

Routes made to consecutive Levels

565

Routing Control - Bulk Routing Panel

List View Routing Examples - Copy-Paste Levels

GV Orbit Client Version 2.0.0

User Guide

Paste Levels with Alt-CTRL-R

The CTRL-V pasting pastes into consecutive Destination Levels and ignores any gaps there might be in the original copied Levels. Whereas, pasting with Alt-CTRL-R retains the original copied Levels pattern, preserving any gaps in the original pattern. Pasting is still done from a ‘starting Level’.

To paste and preserve gaps:

1 Select Destination Levels and copy them. For example, A3, A4, A6 and A8, see

Figure 11-88.

2 Select one ‘Copy to’ Destination Level. This is the ‘starting Level’.

And press Alt-CTRL-R.

Routes are made and the routing of the copied Levels is applied to the ‘Copy to’ Destination

Level (‘starting Level’) and to subsequent Levels with any gaps preserved. See Figure 11-88

for the result of an ALT-CTRL-R paste from the two copied Destination Levels.

One selected ‘Copy to’ Level,

‘starting Level’

Selected Destination Levels

566

Routes made to Levels and the original copied pattern is retained, gaps are preserved.

Fig. 11-88: Result of Alt-CTRL-V Paste

Levels Copy-Paste Footprint

The copied Levels pattern and the pasting type determine a pasting ‘footprint’ in the List

View Levels grid. The pasting footprint pattern

• retains or ignores any gaps in the copied Levels pattern, depending on pasting type

(CTRL-V or Alt-CTRL-R);

• is applied in the List View Levels grid and is based at each ‘starting Level’ in turn, starting with the first ‘starting Level’.

( Note: It is possible to select more than one ‘starting Level’.)

Figure 11-89 shows 2x1 copied Levels pasted with various ‘Copy to’ starting Levels. In

Figure 11-89d, the pasting footprints overlap.

• Figure 11-89a - Single starting Level and a resulting 2x1 pasting.

• Figure 11-89b - One column of four starting Levels which result in four 2x1 pasting

footprints.

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

List View Routing Examples - Copy-Paste Levels

• Figure 11-89c - Two columns of four starting Levels which result in two columns of four

2x1 pasting footprints, which do not overlap.

• Figure 11-89d - Two

adjacent columns of four starting Levels which results in two columns of four 2x1 pasting footprints which do overlap. The overlap is warned with a

pop-up Levels Paste message, see Levels Paste Warning .

Copied Levels, a ‘2x1’ shape.

a) Single starting Level and resulting ‘2x1’ pasting.

Fig. 11-89: Example Level Pasting c) d)

Paste footprint overlaps

Levels Paste Warning

For a Levels Copy-Paste operation which has more than one ‘starting Level’, if the

operation will result in overlapping paste footprints (see Figure 11-89d), a

Levels Paste

warning pops up. See Figure 11-90.

Fig. 11-90: Level Paste Warning

The user can choose to not paste, or to paste anyway, in which case the paste footprints are applied sequentially, starting with the first ‘starting Level’ in the selection. If there is overlap, then some of the Levels Copy-Paste routing may be overwritten. The later routing wins.

567

Routing Control - Bulk Routing Panel

List View Routing Summary

GV Orbit Client Version 2.0.0

User Guide

List View Routing Summary

List View Routing Summary - All-Levels

One Source to One Destinations One Source to Multiple Destinations

To make: An ‘all-levels’ route to a destination:

1 Select a single Destination .

2 -

An ‘all-levels’ route to multiple destinations:

Select a Destination .

Select further with CTRL-Select and/or

SHIFT-Select.)

Begin to type a Source name.

A Dial Source dialog appears.

Proceed to ‘dial up’ a Source name.

Then either:

• select the typed-in Source by pressing Enter/Return; and/or:

• select a Source from the Dial Source filtered source list.

Result: An ‘all-levels’ route is made to the destination.

An ‘all-levels’ route is made to the destinations.

568

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

List View Routing Summary - One-Level

Simple One-Level (Breakaway) Simple One-level (Shuffle)

To route: One level from another source:

One level from same destination.

Select a single Destination Level .

2 Type a single alpha-numeric character.

3 Begin to enter a new

A default Dial Source-Level dialog appears showing currentlyrouted Source and Level .

Source dialog’s upper text entry box.

name into the Press the Tab key.

4 Then in the dialog, either:

• select the required or

Source name;

• finish entering the Source name and press Enter/Return.

Result: A one-level, breakaway route has been

made. (For a channel-swap, do 2x Simple

One-level (Shuffle)

User focus changes to the lower text entry box in the dialog, for Source Level entry.

Then in the dialog, either:

• begin to type in a (new) Source

Level name and then select the required Source Level in the list; or

• fully type in the (new) Source Level name (for example, ‘A2’) and press the Enter/Return key.

A one-level, shuffle route has been made.

One Level to Multiple Levels

To route: One level to multiple destination levels:

1 Select a Destination Level .

2 And select further with CTRL-Select and/or SHIFT-Select.

3 Type any single alpha-numeric character.

A Dial Source-Level dialog appears showing currently-routed Source and Level .

4 Press the Tab key.

User focus changes to the lower text entry box in the dialog.

5 Then, either:

• begin to type in a (new) Source Level name and then select the required

Source Level in the list; or

• fully type in the (new) Source Level name (for example, ‘A2’) and press the

Enter/Return key.

Result: A one-level route is made to all selected Destination Levels .

569

Routing Control - Bulk Routing Panel

List View Routing Summary - Destination Copy

GV Orbit Client Version 2.0.0

User Guide

List View Routing Summary - Destination Copy

Destination Copy-Paste

To: Copy a Destination’s Source-assignments to another Destination:

Destination Paste-Series

‘Copy-Paste’ a series of Destinations:

Select a single Destination .

2 Either:

• type CTRL-C; or

• right-click ‘ Copy ’; or

• click on the ‘ Copy ’ icon in the List View tool bar.

The Destination ’s routing (all levels) is

‘copied’ and is outlined with a ‘crawling’ dashed line.

3 Select a Destination to ‘copy to’.

The Destination is copied.

4 (Optionally, select further ‘copy-to’

Destinations

SHIFT-Select.)

with CTRL-Select and/or

5 Either:

• press CTRL-V; or

• right-click ‘ Paste ’; or

• click the ‘ Paste ’ icon in the List

View tool bar.

Result: The ‘copied’ routing (all levels) is pasted to the selected Destination (s).

Select the first Destination in the range to

‘copy to’.

SHIFT-Select the last Destination in the range to ‘copy to’.

This has selected the ‘Copy to’ range.

Then either:

• press Alt-CTRL-V; or

• click the

List View

Paste Series

tool bar.

icon in the

The currently-routed Source of the copied

Destination is applied to the first

Destination in our ‘Copy to’ range. The next

Source is applied to the next Destination in the ‘Copy to’ range, etc.

570

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

List View Routing Summary - Paste Levels

Paste Levels with CTRL-V Paste Levels with Alt-CTRL-R

To: Copy multiple Destination Level s’ routing and to consecutive Destination Levels with no gaps

Copy multiple and to

Destination Level

Destination Levels s’ routing

.with gaps.

Select a Destination Level .

Select further with CTRL-Select and/or SHIFT-Select.

3 Then either:

• press CTRL-C; or

• right-click ‘ Copy ’; or

• click on the ‘ Copy ’ icon in the List View tool bar.

The routing of the Destination Levels is copied along with the pattern of levels.

5 And then either:

Select one ‘Copy to’ Destination Level (the ‘starting level’).

And press Alt-CTRL-R

• click the Paste icon; or

• press CTRL-V; or

• select right-click ‘ Paste ’.

Result: The copied routing is applied to the ‘Copy to’ Destination Level (‘starting level’) and to subsequent, consecutive Destination

Levels . Any gaps in the copied pattern are not preserved.

The copied routing is applied to the ‘Copy to’ Destination Level (‘starting Level’) and to subsequent Levels with any pattern gaps preserved.

571

Routing Control - Bulk Routing Panel

GV Orbit Custom User Panels

GV Orbit Client Version 2.0.0

User Guide

GV Orbit Custom User Panels

Can a Bulk Routing Panel be Opened from a Custom User Panel?

The Bulk Routing Panel may be opened from a GV Orbit custom user panel (created as part of a GV Orbit control and monitoring, C&M, project).

When the custom user panel is designed, a ‘Load Panel’ GV Orbit Routing Behaviour is used to invoke the Bulk Routing Panel when the custom user panel is run.

Typically, this GV Orbit ‘Behaviour’ would be invoked upon the press of a button on an GV

Orbit C&M project custom user panel.

See:

•

Amend an Existing GV Orbit C&M Project

•

Exercise the C&M Custom Screen

Amend an Existing GV Orbit C&M Project

To prepare a GV Orbit C&M project to be able to open a Bulk Routing Panel:

1 Open/create a GV Orbit C&M project.

2 In the main menu, click on Control and Monitoring > Connections > GVOP and set the Client Domain to a domain with an GV Orbit Routing Service running.

3 Create a New Screen . For example, in the Project window: expand the project item, right-click on ‘screens’, and select ‘New Screen’, enter a name, and click OK.

A new blank C&M project screen opens as a tabbed screen.

4 In the new C&M project screen, add a Button widget. For example, drag on a Button widget from the widget icons along the bottom edge of the GV Orbit Client application window.

5 Edit the Button widget’s Caption

property. See Figure 11-91.

572

GV Orbit Client Version 2.0.0

User Guide

Project item expanded in Project window

Routing Control - Bulk Routing Panel

Amend an Existing GV Orbit C&M Project

Button widget on screen

Edit Behaviours button

Button widget icon Set

Fig. 11-91: C&M Project Screen with Button Widget

Button widget’s Caption property

6 Select the Button widget on screen.

7 Click on the Edit Behaviours button.

The ‘Behaviour and Bindings’ graphical editor is shown. See Figure 11-92.

In the ‘Behaviour and Binding’ graphical editor:

8 Select to show ‘Routing’ Behaviours and click on the ‘Load Panel’ item.

A Load Panel Behaviour and a configured Click Handler Binding is automatically placed into the graphical editor.

See Figure 11-92.

573

Routing Control - Bulk Routing Panel

Amend an Existing GV Orbit C&M Project

GV Orbit Client Version 2.0.0

User Guide

‘Behaviour and Binding graphical editor’

Select ‘Routing’

Select ‘Open Panel’ item (single-click) to add a Load Panel Behaviour.

574

Fig. 11-92: Behaviour and Bindings Graphical Editor

9 Double-click on the added Load Panel Behaviour.

The Behaviour’s configuration screen is shown in the graphical editor.

In the Network window:

10 Expand and locate the Routing service of the GV Orbit server being used.

11 Right-click on the Routing service item and select ‘Copy > Address’.

This copies the RollCall address of the Routing service.

In the graphical editor:

12 Paste the copied address into the ‘Address’ property of the Load Panel configuration.

See Figure 11-93.

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Amend an Existing GV Orbit C&M Project

Right-click on a ‘Routing Service’ item in the Network window.

Select ‘Copy > Address’.

Paste the address into the ‘Address’ property of the Load Panel configuration screen.

Click Close in the Load Panel configuration screen.

Fig. 11-93: Setting Load Panel Behaviour’s RollCall Address

13 Click Close in the configuration screen.

To save this project change:

14 Click Project > Save File in the main menu

15 Click Project > Save Project .

This has designed (a simple) C&M custom screen which contains a button which will open the Bulk Routing Panel.

575

Routing Control - Bulk Routing Panel

Exercise the C&M Custom Screen

GV Orbit Client Version 2.0.0

User Guide

Exercise the C&M Custom Screen

With the designed C&M custom screen open in GV Orbit Client:

1 Click the Design/Run Mode button in the main tool bar of the GV Orbit Client

application window. See Figure 11-96a.

Click to enter Run mode.

Click to enter Design mode.

Fig. 11-94: Design/Run Mode Icon (in Main Tool Bar)

The GV Orbit Client enters Run

mode and the custom screen is run. See Figure 11-96b.

Design/Run Mode icon indicates GV Orbit is in Design mode.

576 a) Click to Enter Run Mode

Design/Run Mode icon indicates GV Orbit is in Run mode.

Click on the Button widget to open the Bulk Routing Panel.

b) Screen is running.

Fig. 11-95: Running the Custom Screen

GV Orbit Client Version 2.0.0

User Guide

Routing Control - Bulk Routing Panel

Exercise the C&M Custom Screen

2 Click on the Button widget to open a new tab containing an Bulk Routing Panel. See

Figure 11-96.

Tab running C&M Custom Panel Tab running the opened Bulk Routing Panel

Fig. 11-96: Bulk Routing Panel Opened in a Tab

577

Routing Control - Bulk Routing Panel

Exercise the C&M Custom Screen

GV Orbit Client Version 2.0.0

User Guide

578

Introduction

GV Orbit Client has user router control functionality and offers the following routing control panels:

•

Routing Control - Bulk Routing Panel

- a simple, non-editable soft panel for fast control of all router cross-points.

•

Routing Control - XY Routing Panel (this chapter) - an editable and customizable soft

panel, typically used for small custom panels for specific routing needs.

This chapter describes the XY Routing Panel .

GV Orbit System

Routing control panels connect to a GV Orbit Routing service running on a GV Orbit server.

Controller-specific connection protocol:

• SW-P-08; or

• NP-0017

GV Orbit server

GVOP protocol

GV Orbit Routing Panel

GV Orbit Client

Fig. 12-1: GV Orbit Routing Panel, Routing Service and Router Controller

GV Convergent. The Routing service provides source/destination information to the client

and acts on routing commands from the client. See Figure 12-2.

579

Routing Control - XY Routing Panel

Prerequisites

GV Orbit Client Version 2.0.0

User Guide

Fig. 12-2: GV Orbit System Diagram

Prerequisites

A GV Orbit server is required, running:

• A GV Orbit Control application.

• A GV Orbit Routing service configured for connection to a Router Controller using either NP0017 or SW-P-08 protocol.

580

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

What is an XY Routing Panel?

An XY Routing Panel runs in the GV Orbit Client application. It is editable and customizable and is typically used for small, purpose-built routing panels for specific routing needs. It can be part of a custom soft user/operator panel in GV Orbit Client.

It can be created with a wizard and tailored to most needs. It is a flexible soft routing control panel which may be:

• Created with a wizard and used.

• Created and then edited for customized use.

• Created from scratch with the GV Orbit Client, in a similar way to a GV Orbit Client C&M project user/operator soft control panel.

XY panels can also be embedded in GV Orbit soft custom operator/user panels. a) Example XY Routing Panel from the Wizard b) Example Customized XY Routing Panel

Fig. 12-3: XY Routing Panel Examples c) Example with Customized Layout

581

Routing Control - XY Routing Panel

Key Features

GV Orbit Client Version 2.0.0

User Guide

• X/Y panel wizard.

• Source and Destination filtering.

• Take, Auto-take, Cancel.

• Shuffles and Breakaways.

• Panel Lock.

• Customizable, editable.

• Source and Destination selection:

• paged access to all ports; or

• definable port-per-button.

This Chapter

This chapter describes:

•

How to Create a New XY Panel , on page 583.

•

Customizing with the XY Wizard , on page 586.

•

XY Panel Layout , on page 592.

•

Getting XY Routing Panel Running , on page 600.

•

XY Panel Operation , on page 604.

•

Assigning Ports to a Port-per-Button XY Panel , on page 613, including:

•

Assigning Port-per-Button , on page 613.

•

Assign Ports to Individual Buttons , on page 613.

•

Quick Port-per-Button Assignment , on page 617.

•

Customizing an XY Panel , on page 621, including:

•

Further Editing an XY Panel , on page 621.

•

Creating a Custom XY Panel from Scratch , on page 622.

•

Creating a Custom BPX Panel , on page 630.

•

Enhancing the Appearance of a Panel , on page 636.

•

How to Embed an XY Panel into a Custom User Panel , on page 643.

582

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

How to Create a New XY Panel

One or more XY Routing Panels can be created in a GV Orbit C&M project.

XY Routing Panels are created in GV Orbit Client Client and stored in a ‘panels’ folder in the

Project window. (If your project does not contain a ‘panels’ folder, see

Creating a ‘panels’

Folder for Early GV Orbit Client Projects , on page 583 for instructions on creating one.)

For instructions on creating a new XY Panel, see

Create a New XY Routing Panel , on page 584.

Creating a ‘panels’ Folder for Early GV Orbit Client Projects

Some early GV Orbit C&M projects do not contain a ‘panels’ folder in the Project window. If this is the case, then one may be created. See below.

If your project does

have a ‘panels’ folder in the Project window, go on to Create a New XY

Routing Panel , on page 584.

To create a missing ‘panels’ folder:

1 Open a C&M project in the GV Orbit Client application.

2 Right-click on the project name item in the Project window and select ‘New Folder’.

Fig. 12-4: Creating a New ‘panels’ Folder’

3 Enter ‘panels’ as the folder name, and click OK .

A new folder called ‘panels’ is added into the Project window.

Fig. 12-5: New ‘panels’ Folder’

4 Click Save File . Click Save Project .

This has created a default new ‘panels’ folder in the project.

Now go on to

Create a New XY Routing Panel , on page 584.

Note: A project folder named ‘panels’:

• allows only files of type ‘panel’;

• displays a ‘New Panel’ right-click menu item.

The folder name is case-sensitive.

583

Routing Control - XY Routing Panel

Create a New XY Routing Panel

GV Orbit Client Version 2.0.0

User Guide

Create a New XY Routing Panel

To create an XY panel in a C&M project in the GV Orbit Client application:

1 Expand the project name in the Project window and look for the ‘panels’ sub-folder.

2 Right-click on the ‘panels’ folder and select ‘New Panel’. See Figure 12-6.

The New X/Y Panel dialog is shown.

Project window

Right-click and select ‘New Panel’.

584

Fig. 12-6: Create a New XY Routing Panel

3 Enter a name for the new XY Panel in the New X/Y Panel dialog.

4 And click OK .

A new panel item is then added into the ‘panels’ folder and a new generic XY Panel is shown in a tab.

Figure 12-7 shows an example with GV Orbit shown in ‘Design Mode’ (not ‘Run Mode’).

5 Click Save File . Click Save Project .

This has created a default new, generic XY Panel (see example in Figure 12-7) which is

editable and customizable, see

Customizing with the XY Wizard , on page 586. Various

button types can be shown/hidden on the panel with the wizard.

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Create a New XY Routing Panel

GV Orbit Client Client shown in ‘Design Mode’

Fig. 12-7: Example New Generic XY Routing Panel

585

Routing Control - XY Routing Panel

Customizing with the XY Wizard

GV Orbit Client Version 2.0.0

User Guide

Customizing with the XY Wizard

A default new, generic XY Panel can be created (see How to Create a New XY Panel , on page 583) which is editable and customizable. When an XY Panel is open in GV Orbit Client,

the panel is editable with the client in ‘Design Mode’ (rather than in ‘Run’ mode).

Customizing may be done with the XY Wizard and editable items include the:

• panel size;

• number of and arrangement of Sources/Destinations; and

• enabling/disabling of other controls.

Use the XY Wizard on new, generic XY Panels.

To Open the XY Wizard

To open the XY Wizard for an XY Panel:

1 Open the XY Panel and go to ‘Design’ mode in GV Orbit Client Client.

2 Click XY Wizard

button. See Figure 12-8.

‘Design’ mode indicated

XY Panel open in GV Orbit Client

Click XY Wizard to open the XY Wizard dialog.

Fig. 12-8: XY Wizard Button

The XY Wizard dialog is displayed for editing the XY panel. For a new XY Panel, it is

generic XY panel settings that are shown selected. See Figure 12-9.

586

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

To Open the XY Wizard b) Corresponding XY Panel a) Settings of a new, generic XY Panel

Fig. 12-9: XY Wizard Dialog (a) and Panel (b, New, Generic Panel Settings Shown)

Note:

Some settings are not currently applicable to a GV Orbit Client system, these include:

Undo, Re-do, Protect and Dial.

Recommendation:

Deselect these settings for GV Orbit Client systems. See Figure 12-10.

= Deselected for GV Orbit Client system cases a) Deselected Settings for GV Orbit Client b) Corresponding XY Panel

Fig. 12-10: XY Wizard Dialog and Panel (Deselected Settings Shown for a GV Orbit Client System)

587

Routing Control - XY Routing Panel

XY Wizard Settings

GV Orbit Client Version 2.0.0

User Guide

3 Deselect the wizard options that are not applicable to GV Orbit Client. See Figure 12-

10a.

The panel appearance changes in response to the settings changes as they are made.

See Figure 12-10b.

For the remaining settings, these may be selected/deselected and configured as required:

4 Change the XY panel setting as required.

(See XY Wizard Settings and Table 12-1 for descriptions of each

XY Wizard setting.)

The panel appearance changes in response to the settings changes as they are made.

5 Close the XY Wizard dialog when finished changing settings.

(This dialog can always be re-opened if required.)

6 Click Save File . Click Save Project .

The modified XY Panel has been saved.

XY Wizard Settings

Panel Size:

Item

Table 12-1: XY Wizard Dialog Settings

For GV

Orbit

Client

Description

Sets the overall size of the XY Panel (in pixels).

Normally, set this to be the size of the monitor used to display the panel.

Width  Text box.

Enter the panel screen width (pixels). Default = 1920.

Height  Text box.

Enter the panel screen height (lines). Default = 1080.

Layout  Select the left-right/top-bottom layout arrangement of the

Source/Source-level and Destination/Destination-level grids:

Sources

Destinations

Source Levels

Destination Levels

Columns

For selection buttons on the XY panel:



Text box.

Select the number of items to control. (Sources, Destinations, etc.)

Text box.

Select the number of columns used to display items.

588

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

XY Wizard Settings

Auto

Item

Table 12-1: XY Wizard Dialog Settings (continued)

For GV

Orbit

Client



Description

Check box.

• Select to automatically arrange the items in columns.

Control:

Enable Take

Enable Undo





Enable various ‘Routing Control’ controls.

Note: Some items do not apply to GV Orbit Client systems and should be deselected.

Check box.

• Select to enable a Take button.

This does not apply to GV Orbit Client systems.

Check box.

• Select to enable an Undo button.

• Deselect for GV Orbit Client systems.

Enable Protect 

Enable Redo

Enable Panel Lock

Enable Cancel





This does not apply to GV Orbit Client systems.

Check box.

• Select to enable a Protect button.

• Deselect for GV Orbit Client systems.

This does not apply to GV Orbit Client systems.

Check box.

• Select to enable a Redo button.

• Deselect for GV Orbit Client systems.

Check box.

• Select to enable a Panel Lock button.

Check box.

• Select to enable a Cancel button.

Display:

Port Numbers  Check box.

• Select to show router port numbers on Source/Destination selection buttons.

589

Routing Control - XY Routing Panel

XY Wizard Settings

GV Orbit Client Version 2.0.0

User Guide

Paging:

Item

Table 12-1: XY Wizard Dialog Settings (continued)

For GV

Orbit

Client

Page Sources 

Description

The Source selection and Destination selection button-grids can be independently configured for either:

• paging through all of the respective router sources/destination ports; or for

• accessing a specific router source/destination port per button.

Check box.

Control Source button-grid configuration:

• Select for ‘Paged’:

Paged Source port selection. Button-grid gives paged access to all router Sources, indexed.

See

Paged Ports , on page 594.

• Deselect for ‘Port-per-Button’:

A ‘fixed’ specific Source port is assignable per button. Each button accesses a specific Source port, non-indexed.

See

Port-per-Button , on page 594.

Page Destinations  Check box.

Control Destination button-grid configuration:

• Select for ‘Paged’:

Paged Destination port selection. Button-grid gives paged access to all router Destinations, indexed.

See

Paged Ports , on page 594.

• Deselect for ‘Port-per-Button’:

A ‘fixed, specific Destination port is assignable per button.

Each button accesses a specific Destination port, non-indexed.

See

Port-per-Button , on page 594.

Filtering:

Filter Sources 

Filter Destinations

Dialing:



Check box.

• Select to show Sources filter control.

Check box.

• Select to show Destinations filter control.

For dial-up selection of a Source or a Destination via its router port number.

Note: Dialing does not apply to GV Orbit Client systems and these controls should be deselected.

590

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

XY Wizard Settings

Item

Table 12-1: XY Wizard Dialog Settings (continued)

For GV

Orbit

Client

Dial Sources 

Dial Destinations 

Description

This does not apply to GV Orbit Client systems.

Check box.

• Select to show Sources dial-up controls.

• Deselect for GV Orbit Client systems.

This does not apply to GV Orbit Client systems.

Check box.

• Select to show Destinations dial-up controls.

• Deselect for GV Orbit Client systems.

Invert Keypads  This does not apply to GV Orbit Client systems.

Check box.

• Select to show Dial-up numeric keypads with 7,8,9 on top row.

• Deselect to show 1,2,3 on top row.

591

Routing Control - XY Routing Panel

XY Panel Layout

GV Orbit Client Version 2.0.0

User Guide

XY Panel Layout

The layout and controls of a newly-created XY Panel are shown in Figure 12-11.

592

Fig. 12-11: Example New XY Panel Layout

An XY Routing Panel is designed in and run from the Client application. Figure 12-11 shows

a view of the XY Panel in ‘Design Mode’ and Figure 12-12 shows an annotated view in ‘Run’

mode.

The panel is laid out with the following main grids/areas (see Figure 12-12):

• Source Grid – Sources are presented here, configurable in the XY Wizard to be a:

• Paged list of all available sources.

• Sub-set of defined sources.

• Source Levels Grid – List of available levels for selected source(s).

• Destination Grid – Destinations are presented here, configurable in the XY Wizard to be a:

• Paged list of all available destinations.

• Sub-set of defined destinations.

• Destination Levels Grid – List of available levels for selected destination(s).

• Routing Controls – Buttons are configured as shown/hidden in the XY Wizard , and include: ‘Undo’, ‘Redo’, ‘Protect’, ‘Take’, ‘Panel Lock’ and ‘Cancel’.

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

XY Panel Layout

Source grid paging control Sources filter box Destination grid paging control Destinations filter box

(2)

Source Grid

(3)

Destination Grid

(1)

(4)

Routing

Controls

Source Levels Grid Destination Levels Grid

Shown when a Source is selected Shown when a Destination is selected

Click to toggle

Source Port Dial Grid on/off.

Click to toggle

Destination Port

Dial Grid on/off.

Note: Dial Grids are not applicable to GV Orbit

Client systems.

Button face legend:

(1) Destination selected.

(2) Currently-routed Source shown.

(3) New Source pre-selected.

(4) Click Take to make route.

Buttons show names and router port numbers.,see Figure 12-15.

Fig. 12-12: New XY Panel Layout and Controls (Annotated, ‘Run’ Mode)

Note: The following controls on a newly-created XY Panel are not applicable to GV Orbit Client systems:

• Undo, Re-do, and Protect buttons; and

• Source and Destination Dial Grids.

593

Routing Control - XY Routing Panel

Source and Destination Selection Button-Grids

GV Orbit Client Version 2.0.0

User Guide

Source and Destination Selection Button-Grids

The Source and Destination button-grids can be independently configured with the XY

Wizard Settings for either:

•

Paged Ports

operation; or for

•

Port-per-Button operation.

When an XY Panel is running, buttons are annotated to reflect the source/destination

names, see Source/Destination Button Annotations

Paged Ports

A Source or Destination button-grid can be configured for paging through all of the respective router sources/destination ports. (Configuration is done in the

XY Wizard

Settings .)

Figure 12-13 shows a running example XY Panel with 12-button button-grids configured

for ‘paged ports’ operation. Each paged button grid has paging controls to access all router ports (source or destinations accordingly). Page 1 starts at port 1 and shows consecutive ports on the button grid buttons.

594

Paging controls

Fig. 12-13: Example Paged Ports Button Grid

Port-per-Button

A Source or Destination button-grid can be configured for accessing a ‘fixed’, specific router source/destination port per button. (Configuration is done in the

XY Wizard Settings , on page 588.)

Figure 12-14 shows an example XY Panel with 12-button button-grids configured for ‘port

per button’ operation. There is no paging here.

The example XY Panel is shown both in ‘Design’ mode and in ‘Run’ mode. This example has an initial, default assignment (from the XY Wizard) of ports-to-buttons, where buttons in each grid access ports starting from 1 onwards.

Each button can be further configured to access a specific port, as required. See

Assigning

Port-per-Button , on page 613.

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Source and Destination Selection Button-Grids a) Wizard settings used in the example here

By default, buttons are assigned ports starting from 1 onwards.

b) Example XY Panel, Port-per-Button, ‘Design’ mode

Buttons show router port names etc. when panel is running.

c) Example XY Panel, Port-per-Button, ‘Run’ mode

Fig. 12-14: Example Port-per-Button

595

Routing Control - XY Routing Panel

Source/Destination Button Annotations

GV Orbit Client Version 2.0.0

User Guide

Source/Destination Button Annotations

The source/destination selection and source/destination level selection buttons in ‘Run’ mode are annotated to reflect the source/destination name or level name etc. when the panel is running.

Additionally, when making a route, the selected destination button shows the currentlyrouted source and the current (pre-)selected source for that destination.

Buttons can be configured to show router port numbers and port names, see XY Wizard

Settings , on page 588.

Figure 12-15 shows button-face annotations.

Source name

Source Button:

Port number

Destination Button:

Currently-Routed Source name

Pre-selected Source name

Destination Name name

Port number

Source Level Button:

Level name

Destination Level Button:

Currently-Routed Source Level name

Pre-selected Source Level name

Destination Level name

Fig. 12-15: XY Panel Buttons on a Running XY Panel

Routing Control Buttons

Note: Undo , Redo , Protect functions are not currently available in an XY

Panel for GV Orbit systems. (Use the Bulk Routing Panel for these functions.)

Depending on the settings in the XY Wizard, the Routing Control section of the panel contains:

• Take button.

Click to make a route to the selected Destination from a pre-selected Source.

• Cancel button.

Click to deselect all Destinations and Sources.

• Lock button.

Click to lock the XY panel controls. Click again to unlock.

596

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

XY Routing Panel- Operational Keys

Table 12-2: XY Panel Operational Keys

Operation

Select

Select a Range

Mouse

Mouse click on a Source or Destination.

Mouse click on first item then

SHIFT click on last item.

Add to/remove from a multiple selection CTRL + Mouse click

Paste Series Click ‘Paste Series’ icon in panel.

Take Double-click on pre-selected Source;

Cancel or click Take button.

Click ‘Cancel’ button.

XY Panel Level Selection

When a source or a destination is selected, the associated levels are shown in the corresponding ‘Levels Grid’ panel. If multiple sources or destinations are selected, then only their common levels are shown.

All levels are selected by default. If the user selects one or more levels, then all other levels are deselected.

XY Panel Right-Click Menus

Right-click on background of a XY Routing Panel to show a drop-down context menu. See

Figure 12-16.

597

Routing Control - XY Routing Panel

XY Panel Right-Click Menus

GV Orbit Client Version 2.0.0

User Guide a) In ‘Run’ mode’ b) In ‘Design’ mode

Fig. 12-16: XY Panel Background Right-Click Menu: a) in ‘Run’ Mode; b) in ‘Design’ Mode.

Window

Item

Dock/Undock

Full Screen

Exit Run Mode

Enter Run Mode

Scale to Fit

Select All

Deselect All

Table 12-3: XY Panel Right-Click Menu Items

Shown in

‘ Run ’

Mode

‘ Design ’

Mode



Description

Undock or dock the XY Routing Panel window from the GV Orbit

Client window.

Show the XY Routing Panel window full-screen.

When full-screen, right-click > Exit Full Screen .

Click to exit ‘Run’ mode and enter GV Orbit ‘Design’ mode.



Click to enter GV Orbit ‘Run’ mode.

Click to fit the panel to the window.

Selects all items.

Deselects all items.

598

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

XY Panel Right-Click Menus

Item

Lock/unlock

Table 12-3: XY Panel Right-Click Menu Items (continued)

Shown in Description

‘ Run ’

Mode

‘ Design ’

Mode

  Click to toggle locking/unlocking the panel.

When the panel is locked, user operation is disabled.

Note: Clicking the ‘Lock’ icon in the GV Orbit Client main tool bar also toggles panel lock.

Resize to Widgets

Reset Panel Styles to Default

Variables...

Connection Mode



Click to resize the XY panel background to fit to its constituent widgets.

Click to set widget styles all to ‘default’.

Click to show the Variables dialog.

Note: The Variables dialog is not editable in ‘Run Mode’.

Note: This item is a generic widget feature, not routing-specific.

Widget feature:

When designing C&M project screens or XY Panels, the graphical widgets used may be shown to be visually connected together by a curved line.

Click Connection Mode to show connection points on the widgets.

Edit Behaviours  Click to toggle showing the Behaviours and Bindings graphical editor.

599

Routing Control - XY Routing Panel

Getting XY Routing Panel Running

GV Orbit Client Version 2.0.0

User Guide

Getting XY Routing Panel Running

When an XY Panel runs on the GV Orbit Client Client in a C&M project, it controls signal routing via the Routing service running on a GV Orbit Client server.

What is a Routing Service?

As part of setting up a GV Orbit Client system, a Routing service must be configured with a

RollCall address and a GVOP domain, and started up to run on a GV Orbit Client server. The

Routing service uses its RollCall address and is visible in the Network window of a GV Orbit

Client and see Figure 12-17.

Right-click and select ‘Info’ to see details of the Routing service item

600

Routing service RollCall address’.

To copy this address, right-click in Network window and select ‘Copy > Address’.

Fig. 12-17: Routing Service in Network Window

Note: The GVOP domain of the GV Orbit C&M project and the GVOP domain of the Routing service must be the same.

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

How to Connect an XY Panel to a Routing Service

Automatic Setup

To run in GV Orbit Client Client, an XY Panel must point at a Routing service on a GV Orbit

Client server. This is usually automatically set up for the user, including:

• GV Orbit Client C&M project GVOP domain the same as the Routing service. This should be set automatically.

(To see the project’s GVOP domain number, go to the main menu item

‘Connections > GV Orbit Server’, and look at the ‘Client domain’ setting.

Edit the domain number here if required.)

• XY Panel set with a RollCall address of the Routing service. This should be set automatically.

To do this, the XY Panel’s ‘Address’ variable must be set to be the RollCall address of the target Routing service.

Manual Setup

To manually set up the XY Panel to point at a Routing service:

1 In the Network window, right-click on the Routing service item, and select ‘Copy > Address’.

This copies the RollCall address of the service into your copy buffer.

2 Go to the XY Panel and right-click on the XY Panel background and select ‘Variables...’.

The Variables

dialog is shown. See Figure 12-18.

Paste copied address into ‘Address’ value field

Fig. 12-18: Setting Routing Service RollCall Address for XY Panel

601

Routing Control - XY Routing Panel

To Run an XY Panel

GV Orbit Client Version 2.0.0

User Guide

3 In the Variables dialog, paste in the copied RollCall address into the value of the ‘Address’ variable.

See Figure 12-18. (Alternatively, simply enter the address manually.)

4 Click OK .

5 Click Save File . Click Save Project .

This has manually pointed an XY Panel at a Routing service.

To Run an XY Panel

When an XY Panel runs, it connects to the Routing service and collects routing information and data (Source names/port numbers, Destination names/port numbers, routed source names etc.) and populates the panel buttons with names and router port numbers etc.

To run an XY panel:

1 Open the panel in GV Orbit Client and click on the ‘Run’ mode/’Design’ mode main tool

bar icon to enter ‘Run’ mode. See Figure 12-20.

Click to enter ‘Run’ mode (from ‘Design’ mode)’ Buttons show actual source and destinations name s etc.

a) XY Panel in ‘Design’ mode

Fig. 12-19: Enter Run Mode b) XY Panel in ‘Run’ mode

The XY Panel run and connects to the Routing service and gets source and Destination

names etc. See Figure 12-20.

602

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

To Run an XY Panel

(3)

(2)

(1)

(4)

(1) Destination selected.

(2) Current Source shown.

(3) New Source pre-selected.

(4) Click Take to make route.

Note: Routing Control buttons can be shown/hidden with the XY Wizard tool.

(See

Customizing with the XY Wizard , on page 586.)

Fig. 12-20: Running XY Panel Example

603

Routing Control - XY Routing Panel

XY Panel Operation

GV Orbit Client Version 2.0.0

User Guide

XY Panel Operation

Make a Simple Route with an XY Routing Panel

Simple Route

To make a simple route:

1 Select a Destination .

The currently-routed Source is shown.

2 Select a Source .

The pre-selected Source is shown.

3 Click Take . (Click Cancel , to deselect the source/destination.)

The selected source is routed to the selected destination. The route is made.

Alternatively, select the Source first.

1) Select Destination

Currently-routed Source is shown.

2) Select Source

3) Take

1) 1)

Fig. 12-21: Making a Simple Route

604

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Route One Source to Multiple Destinations

1 Select a Destination by clicking on the destination selection button.

2 Select a second Destination by CTRL + clicking on a destination button.

3 Select further destinations with CTRL + click.

4 Select one Source .

5 Click Take .

The source is routed to all selected destinations.

Note: A contiguous range of Destinations (or Sources) can be selected by clicking the first Destination (or Source) in the range and then SHIFTclick on the last Destination (or Source) in the range.

Pre-selected Source Selected Destinations

Currently-routed Sources shown

Routed result

Fig. 12-22: One Source Routed to Multiple Destinations

Alternatively, the source may be selected first.

605

Routing Control - XY Routing Panel

Route Multiple Sources to Multiple Destinations

GV Orbit Client Version 2.0.0

User Guide

Route Multiple Sources to Multiple Destinations

1 Select a Destination by clicking on the destination selection button.

2 Select a second Destination by CTRL + clicking on a destination button.

And select any further destinations with CTRL + click.

3 Select a Source by clicking on the source selection button.

4 Select a second Source by CTRL + clicking on a source button.

And select any further sources with CTRL + click.

Note: Select the same number of sources as there are selected destinations.

5 Click Take .

The source is routed to all selected destinations.

Selected Destinations

Currently-routed Sources are shown

Pre-selected Sources

606

Routed result

Fig. 12-23: Making Multiple Routes

Alternatively, the Sources may be selected first.

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Route Multiple Sources to Multiple Destinations

Note: Source or Destination CTRL-selection Order:

When routing many sources to many destinations and making selections with CTRL-clicks, then the order of selection is significant and affects the order in which the routing is done.

For example, to route sources 1 to 8 to destinations 8 to 1:

• Select Destinations 1 to 8 by ‘CTRL-clicking’ on each button in the order 1 to 8.

• Select Sources 8 to 1by ‘CTRL-clicking’ on each button in the order 8 to 1.

• Click Take .

Note: With the contiguous SHIFT-selection, the order used is that of the buttons on the panel, not the order of selection of buttons.

607

Routing Control - XY Routing Panel

Breakaway

GV Orbit Client Version 2.0.0

User Guide

Breakaway

What is a Breakaway?

See

What is a Breakaway?

, on page 523, for an explanation of a breakaway.

Note: Implied Breakaway:

A ‘breakaway’ occurs when not all of a destination’s levels are selected for routing. This can happen if a source with fewer levels than the selected destination is routed, this will result in a ‘breakaway’ (without explicitly selecting destination levels when routing).

Note:

Performing a ‘normal’ route to a Destination which already has a ‘Breakaway’ will over-ride the breakaway on the Destination, resulting in no ‘Breakaway’.

Perform a Breakaway

To perform a breakaway (see Figure 12-24):

1 Select a Destination .

2 Select one or more Destination Levels to route (for example, audio channels A1 and

A2).

3 Select a new Source . (Pre-selected source)

4 Click Take .

A routing is made: The selected Destination Levels have corresponding levels from the preselected Source

routed to them. See Figure 12-24b.

The Destination button shows a ‘Breakaway’ symbol.

608

GV Orbit Client Version 2.0.0

User Guide

Currently-routed Source shown

Routing Control - XY Routing Panel

Breakaway

Selected Destination

Selected Destination Level(s)

Pre-selected Source a) Before TAKE

Take

Breakaway symbol shown on button

Audio channels shown routed from another Source b) After TAKE

Fig. 12-24: Breakaway Example: a) Before TAKE; b) After TAKE.

As an alternative, to perform a breakaway, the source may be selected first.

609

Routing Control - XY Routing Panel

Shuffle

GV Orbit Client Version 2.0.0

User Guide

What is a Shuffle?

See

What is a Shuffle?

, on page 528, for an explanation of a shuffle.

Note: A shuffle is applied to a destination and stays with that destination when other routes are made to it until the shuffle is explicitly undone.

Example Shuffle

This example swaps two audio channels pairs.

Fig. 12-25: Swap Two Audio Channel Pairs

1 Select a Destination .

2 Select one or more Destination Levels . (For example, click on audio channels A5, A6,

A7 and A8. See Figure 12-26.)

3 Select the currently-routed Source .

4 Select the Source Levels in the order in which they shall apply to the destination

Levels.

(For example, audio channels A7, A8, A5 and A6 in that order .)

Note: Selecting just one level will route this to all selected destination levels.

5 Click Take .

The selected source levels are routed to the selected destination levels and a shuffle is

formed. Figure 12-26 shows a shuffle example, swapping the order of two audio

channel pairs, as per Figure 12-25.

610

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Shuffle

Select the currently-routed Source

Select Source Levels A7, A8, A5 and A6 in that order.

Selected Destination

Selected Destination Level(s) A5 to A8 a) Before TAKE

Take

‘Shuffle’ symbol shown on button b) After TAKE

Audio channels shown shuffled

Fig. 12-26: Shuffle Example: a) Before TAKE. b) After TAKE.

611

Routing Control - XY Routing Panel

Shuffle

GV Orbit Client Version 2.0.0

User Guide

Routing to a Shuffled Destination

When routing to a shuffled Destination , the ‘Shuffle’ persists.

For example, when a routing Source ‘Cam S10’ to the already-shuffled destination ‘Mon1’,

created in Example Shuffle

, the Source is routed and the audio stereo pair swapping of

Figure 12-25 still exists (but with the new source).

A ‘Shuffle’ persists on a Destination until it is explicitly undone with a new routing operation.

Undo Shuffle

This example describes a new routing operation to undo the shuffle of the

Example Shuffle , on page 610.

1 Click Cancel to cancel any selections already made.

2 Select the ‘already-shuffled’ Destination .

3 Select the shuffled Destination Levels .

4 Select the currently-routed Source .

5 Select the Source Levels in the order in which they shall apply to the Destination

Levels .

So, to undo our

Example Shuffle , on page 610,

select audio channels A5, A6, A7 and A8 in that order.

6 Click Take .

The selected Source Levels are routed to the selected Destination Levels , undoing the shuffle. The ‘shuffle’ symbol no longer appears on the Destination button.

612

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Assigning Ports to a Port-per-Button XY Panel

When creating an XY Panel, a Source button-grid or Destination button-grid can be defined for accessing a ‘fixed’, specific router source/destination port per button. (This ‘fixed’ definition is done in the

XY Wizard Settings

Following definition with the XY Wizard, each button of a ‘port-per-button’ button-grid then can be configured to access a specific port. This port assignment is described here.

Assigning Port-per-Button

Following creation from the XY Wizard, buttons in a ‘Port-per-Button’ button-grid can be assigned specific ports on a per button basis, as required.

There are two ways to perform the port assignments to the buttons:

Assign Ports to Individual Buttons , on page 613. This describes individual assignment

of ports to buttons.

Quick Port-per-Button Assignment , on page 617. This describes selecting all ports with

the Bulk Routing panel and copy-pasting this into the XY Panel.

Assign Ports to Individual Buttons

Assigning individual buttons done in the XY Panel in ‘Design’ mode.

The example of Figure 12-14 shall be used to show how to assign a port to a button:

1 In ‘Design‘ mode, select the Source button-grid and ‘Alt-select’ its first button.

The first button is selected. See Figure 12-27a.

2 Click on the Edit Behaviours button in the Properties

box. See Figure 12-27a.

The graphical Behaviours and Bindings editor is opened. See Figure 12-27b.

The editor shows the Behaviours and Bindings linked to the selected button widget.

613

Routing Control - XY Routing Panel

Assign Ports to Individual Buttons

Source button selected

GV Orbit Client Version 2.0.0

User Guide

Edit Behaviours button a) First Source button selected, click Edit Behaviours

Behaviour

Binding

Selected Widget b) Graphical Behaviours and Bindings Editor

Fig. 12-27: Open Behaviour and Bindings Editor

3 Double-click on the Behaviour linked to the selected widget.

The properties of the Behaviour are shown. See Figure 12-28a.

4 Select the value of the ‘Source’ property (see Figure 12-28a)

and enter a router port to use:

• enter a port name and/or port number; or

• click on the icon and select a Source name from the filterable list; or

• enter a GV Orbit Client variable. (For example, {My_Source_Port} )

A new ‘Source’ property value has been entered.

614

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Assign Ports to Individual Buttons

Note: The entered router port may be:

• a port number;

• a port name; or

• a ‘Number:Name’, for example, 12:Cam1; or

• a GV Orbit Client variable.

In the case of a port name, the name is looked up automatically to find the port number to assign.

In the case of ‘Number:Name’, then the port number is used to assign with.

In the case of a user variable, this should be defined as a port number.

Note: To select a router port from a filterable list:

• Click on the icon at the far end of the Source/Destination

property value field (see Figure 12-28 a).

The Source/Destination Picker dialog is shown and displays a

list of Sources/Destinations. See Figure 12-28b.

• The list is filterable.

• Select a Source/Destination name from the filterable list.

• Click OK when done.

615

Routing Control - XY Routing Panel

Assign Ports to Individual Buttons

GV Orbit Client Version 2.0.0

User Guide

Enter a Port Number, or Name, or Number: Name.

Alternatively, click on the icon.

a) Setting ‘Source’ property of the Behaviour

616 b) Source Picker Dialog ( Destination Picker is similar)

Fig. 12-28: Setting ‘Source’ or ‘Destination’ Property Value

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Quick Port-per-Button Assignment

Fig. 12-29: New ‘Source’ Property Value

5 Click Close .

6 Click Save File . Click Save Project .

7 Enter ‘Run’ mode.

8 The XY Panel runs and the newly-assigned Source is assigned to the Source button, see

Figure 12-30.

Fig. 12-30: Running XY Panel

Thus, a Source button can have a port assigned to it.

Destinations buttons are assigned similarly.

Assign all buttons as required.

There is a quicker way to make these assignments, which uses the help of the Bulk Routing

Panel. See Quick Port-per-Button Assignment .

Quick Port-per-Button Assignment

This describes a quicker method of assigning buttons to ‘Port-per-Button’ XY Panel buttongrids. All ports are selected via the Bulk Routing panel and then simply ‘copy-pasted’ into the XY Panel.

Prerequisites:

• A new XY Panel with one or more button grids set to be ‘Port-per-Button’ (not ‘Paged

Ports’, see ‘Paging’ setting in

XY Wizard Settings , on page 588).

The following example assumes that the buttons of both the Source button-grid and of the

Destination button-grid require setting up in for ‘Port-per-Button’ operation. If an XY Panel just has one such button-grid, then that grid may be quickly set up in a similar way.

To quickly make port-to-button assignments:

617

Routing Control - XY Routing Panel

Quick Port-per-Button Assignment

GV Orbit Client Version 2.0.0

1 Open a Bulk Routing Panel.

(Click the ‘Bulk Routing’ icon on the Routing Workflow, see Figure 12-31.)

User Guide

Fig. 12-31: Open Bulk Routing Panel

2 Select all the Destination and Source ports required.

Note: When selecting the ports in the Bulk Routing panel, the filtering may be used and ranges of ports and individual ports can be selected.

Selected Sources and selected Destinations

618

Right-click and select ‘Copy as Widgets’.

Fig. 12-32: Copy As Widgets in Bulk Routing Panel

3 When all ports are selected, right-click in the background of the Bulk Routing panel and select ‘Copy as Widgets’.

The selected buttons (Source and Destination ones in this example) are copied to your

GV Orbit Client Client’s copy-buffer.

4 Open the target XY Panel.

5 Enter ‘Design’ mode in GV Orbit Client Client.

6 Right-click in the background of the XY Panel and select ‘Paste’.

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Quick Port-per-Button Assignment

The copied buttons are pasted into the XY Panel. See Figure 12-33.

Pasted buttons ‘Design’ mode is shown

Right-click and select ‘Copy as Widgets’.

Fig. 12-33: Paste Buttons in from Bulk Routing Panel ‘Copy as Widgets’

7 The buttons now in the XY Panel can be arranged as required and any previouslyexisting Source/Destination buttons may be deleted if required.

8 Click Save File . Click Save Project .

9 Go to ‘Run’ mode to exercise the XY Panel.

Fig. 12-34: XY Panel with Quick-Assigned Ports

Port-per-Button Pasting into C&M Custom Soft Panel

The example in Quick Port-per-Button Assignment

pastes selected button widgets from a

Bulk Routing Panel into an XY Panel. This selection of buttons may also be pasted into a GV

Orbit Client C&M user/operator custom panel.

619

Routing Control - XY Routing Panel

Quick Port-per-Button Assignment

GV Orbit Client Version 2.0.0

User Guide

Note:

In the GV Orbit Client Client Project window:

• XY Panels are listed in the ‘panels’ folder; and

• Custom user/operator soft panels are listed in the ’screens’ folder.

In this case, the pasted buttons are still functional and will select Destinations and Sources when

the soft panel is run. There is no ‘Take’ button and ‘auto-take’ applies. See Figure 12-35

Selected Destination

Routed Source

Pre-selected Source

Route automatically made to destination

Fig. 12-35: Auto-Take with Pasted-in Routing Buttons (Running)

620

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Customizing an XY Panel

An XY Panel may be modified and customized by simply using the XY Wizard. Additionally, an XY Panel may be further modified and customized by:

• Using the XY Wizard and then further editing the XY panel,

see Further Editing an XY Panel , on page 621.

An XY Panel may also be created from scratch without using the XY Wizard.

This is done with GV Orbit graphical widgets and GV Orbit Client Behaviours and Bindings in a similar way to designing a custom user/operator panel in a C&M project.

See:

•

Creating a Custom XY Panel from Scratch , on page 622; and see

•

Creating a Custom BPX Panel , on page 630.

To enhance the appearance of a control panel, lines, labels etc may be added.

See

Enhancing the Appearance of a Panel , on page 636.

Further Editing an XY Panel

Editing an XY panel is done in a similar way to editing a GV Orbit Client C&M Project custom user/operator screen and an XY Panel can be customized as required. For example:

• buttons may be re-positioned, re-sized;

• other widgets can be added (Labels, Tally Lamps, etc.);

• colors can be changed (background colors); and

• widget style themes can be selected.

Figure 12-36 shows an example XY Panel that has been edited after being started with the

XY Wizard. See

Enhancing the Appearance of a Panel , on page 636, for further examples of

enhancing the appearance of an XY Panel.

Fig. 12-36: Edited XY Panel Example

621

Routing Control - XY Routing Panel

Creating a Custom XY Panel from Scratch

GV Orbit Client Version 2.0.0

User Guide

Creating a Custom XY Panel from Scratch

A custom XY Panel can be created from scratch in a GV Orbit Client C&M project.

A custom panel can be made to be smaller and more suited to be embedded into a C&M project screen. An example small panel with two destinations and a handful of possible

sources is given in Figure 12-37 and the steps to generate it are below.

622

Fig. 12-37: Custom XY Panel Example

Step1: New Empty Basic XY Panel

Firstly, create a new empty XY Panel :

1 Open an GV Orbit C&M project in the GV Orbit Client application.

2 Right-click on the ‘panels’ folder item in the Project window and select ‘New Panel’.

3 Enter a name into the New XY Panel dialog and click OK

. See Figure 12-38.

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Creating a Custom XY Panel from Scratch

Fig. 12-38: Create New XY Panel

A new XY Panel is created in the ‘panels’ folder and is shown in the Project window and is open in a tab.

4 In the new XY Panel tab, delete all widgets.

(Type CTRL-A in the tab to select all widgets and then press the Delete key.)

An empty XY Panel results.

5 Click Save File .

This has created an empty XY Panel in the C&M project. See Figure 12-39.

Fig. 12-39: Empty XY Panel

When editing the XY Panel, it is useful to adjust the position of the routing control widgets tool bar in the GV Orbit Client Client, to make it more accessible. To do this:

623

Routing Control - XY Routing Panel

Creating a Custom XY Panel from Scratch

GV Orbit Client Version 2.0.0

User Guide

6 Drag the routing control widgets tool bar by its handle to a convenient position. See

Figure 12-40.

Drag handle and release to re-position Routing Control widget tool bar

624

Fig. 12-40: Re-positioning the Routing Control Widgets Tool Bar

Step 2: Add Routing Control Widgets to (empty) XY Panel

With the empty XY Panel open in GV Orbit Client:

1 Add 8 Source Button

widgets from the Routing widget tool bar (see Figure 12-41).

(Click on ‘Source Button’ button on the tool bar and drag on button widgets.)

The button annotation names increment automatically for each added button.

2 Similarly add 2 Destination Button widgets.

GV Orbit Client Version 2.0.0

User Guide

Source Button widgets

Destination Button widgets

Routing Control - XY Routing Panel

Creating a Custom XY Panel from Scratch

Routing control widgets tool bar

Fig. 12-41: Adding Source and Destination Buttons

Finally, add a Take button:

3 Select ‘Control Buttons’ in the tool bar.

A small dialog appears.

Fig. 12-42: Adding a Take Button

4 Select ‘Take’ and click OK .

A Take button widget appears at your cursor, drop this onto the XY Panel.

5 Arrange the buttons as required.

6 Click Save File and Save Project .

625

Routing Control - XY Routing Panel

Creating a Custom XY Panel from Scratch

GV Orbit Client Version 2.0.0

User Guide

Fig. 12-43: Added Buttons

Step 3: Exercise Panel

This XY Panel, when run, will allow the user to select a source from sources 1 to 8 and route it independently to destinations 1 or 2.

Destination selection buttons

Source selection buttons

626

Fig. 12-44: Running the New XY Panel

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Creating a Custom XY Panel from Scratch

Step 4: Assigning a Port-per-Button

With the XY Panel in ‘Design’ mode in GV Orbit Client Client, the Source buttons and

Destination buttons can be configured for other source or destination ports in the same way as in a ‘Port-per-Button’ panel (See

Assigning Ports to a Port-per-Button XY Panel , on page 613, for more information.)

To assign ports:

1 Right-click in the XY Panel’s background and select ‘Edit Behaviours’.

The ‘Behaviours and Bindings’ graphical editor is shown.

Fig. 12-45: Double-click on ‘Source Button’ Behaviour

2 Select a Source button in the XY Panel and double-click on the ‘Source Button’

Behaviour in the editor. See Figure 12-45.

The Behaviour’s properties are shown.

3 Set the ‘Mode’ property to ‘Fixed’.

4 Set the ‘Source’ property to a chosen Source name.

5 Click Close .

A Source button now has a port assigned.

6 Repeat for the other Source buttons.

And then:

7 Perform similar steps for each Destination button.

The buttons now all have assigned ports.

627

Routing Control - XY Routing Panel

Creating a Custom XY Panel from Scratch

GV Orbit Client Version 2.0.0

User Guide

Step 5: Styling

1 Arrange the buttons and resize as required.

2 Add any further labels/shapes/colors to enhance the panel’s appearance, as required.

Finally:

3 Right-click on the XY Panel background and select ‘Resize to Widgets’.

628

Fig. 12-46: Custom XY Panel

4 Click Save File .

Click Save Project .

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Creating a Custom XY Panel from Scratch

Step 6: Exercise Panel

1 Click the ‘Run Mode’ icon in the main tool bar and exercise the panel.

• Select Destination.

• Select source to route

• Click Take.

Fig. 12-47: Exercising the XY Panel

The small custom panel operates like a fixed, reduced-size XY Panel and may be dragged

onto a C&M project custom user panel screen and embedded into it, if required. See How to

Embed an XY Panel into a Custom User Panel , on page 643.

629

Routing Control - XY Routing Panel

Creating a Custom BPX Panel

GV Orbit Client Version 2.0.0

User Guide

Creating a Custom BPX Panel

What is a BPX Panel Type?

A BPX (BPX, button per crosspoint) panel enables a button-click to specify and make a route between a source and destination. A simple custom panel can be designed as part of a C&M project, for example, to route one of several sources to a single destination.

A BPX Behaviour is available in GV Orbit which can be associated with a button widget. This enables a button-click to make a route between a specific source and destination. BPX

Panel Example

An example BPX panel is a simple panel where each button is configured to set a route to the same destination, but from a different source. This simple BPX panel is shown in

Figure 12-48 and the steps to generate it in GV Orbit are given below.

Each button configured to make a different route

(usually) to the same destination.

Fig. 12-48: Custom BPX Example

630

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Creating a Custom BPX Panel

Basic BPX Panel

To create this panel:

1 Create a new empty XY Panel .

(This is described in

Step1: New Empty Basic XY Panel , on page 622 for the Creating a

Custom XY Panel from Scratch , on page 622.)

2 Add a graphical Button

widget to the panel. (See Figure 12-49.)

Drag on a Button widget

Fig. 12-49: Add a Button Widget

3 Right-click in the XY Panel’s background and select ‘Edit Behaviours’.

The ‘Behaviours and Bindings’ graphical editor is shown.

4 Select the Button widget.

The ‘Behaviours and Bindings’ graphical editor for the selected button is shown.

631

Routing Control - XY Routing Panel

Creating a Custom BPX Panel

GV Orbit Client Version 2.0.0

User Guide

Fig. 12-50: Behaviours and Bindings of Selected Button Widget

632

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Creating a Custom BPX Panel

In the editor:

5 Filter the Behaviours on ‘Routing’. See Figure 12-51a.

6 Select a BPX Behaviour. See Figure 12-51b.

A BPX Behaviour is added to the ‘Behaviour and Bindings’ editor and a Binding too. See

Figure 12-51b.

Filtered list of

Routing

Behaviours a) Filter Behaviours on ‘Routing’ b) Select a BPX Behaviour

Fig. 12-51: Adding a BPX Behaviour

BPX Behaviour is added and a Binding

633

Routing Control - XY Routing Panel

Creating a Custom BPX Panel

GV Orbit Client Version 2.0.0

User Guide

A BPX button’s function is to specify a Source and a Destination and a route between the two:

7 Double-click on the BPX Behaviour.

The Behaviour’s properties are shown. See Figure 12-52.

8 Set the ‘Source’ property to a required Source.

9 Set the ‘Destination’ property to the required Destination.

Fig. 12-52: Setting ‘Source’ and ‘Destination’ Property Values

10 Click Close .

This has defined one BPX button. For example, a route between the Source and

Destination.

Now we will copy this button (with its Behaviour/Binding settings) twice:

11 In the BPX panel, select the one Button widget, right-click on it and select ‘Copy’.

12 Select the panel’s background, right-click and select ‘Paste’.

13 And again, select the panel’s background, right-click and select ‘Paste’.

This copies the button twice more on the panel.

14 Select the panel’s background, right-click and select ‘Edit Behaviours’.

For each button that was copied:

15 Select the button, and edit the button’s BPX Behaviour.

16 Change the ‘Source’ property to select a different Source each time.

Then:

17 Click Close .

18 Click Save File .

19 Click Save Project .

634

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Creating a Custom BPX Panel

Fig. 12-53: BPX Panel, Designed

This has created a basic BPX panel with three buttons. Each button is configured to set a route to the same destination, but from a different source.

Exercise the BPX Panel

1 Enter ‘Run’ mode in GV Orbit Client Client.

2 Operate the panel. See Figure 12-54.

Click the second button to make a route from its source, S10-2.

See the result

Click the third button to make a route from its source, S10-3.

See the result

Currently routed Source to the Destination

Source which the button will route to the Destination, if selected.

Destination

Fig. 12-54: BPX Panel Running

635

Routing Control - XY Routing Panel

Enhancing the Appearance of a Panel

GV Orbit Client Version 2.0.0

User Guide

Enhancing the Appearance of a Panel

•

Panel Enhancement - Add Labels , on page 636.

•

Enhancement - Add Lines , on page 639.

Note: Carry out edits to the panel design in GV Orbit Client Client in

‘Design’ mode.

Panel Enhancement - Add Labels

Label widgets can be added for the display of information. In this example, some text is added to the BPX panel to display the destination name and the source routed to it.

1 Add four Label

widgets to the BPX panel. See Figure 12-55.

2 Set two labels to have fixed ‘Caption’ properties. See Figure 12-55.

Label widgets with fixed ‘Caption’ property Label widgets using a Destination Behaviour

Selected Label

636

Add a Destination Behaviour

Fig. 12-55: Adding Labels

For each of the other two Label s:

3 Open the ‘Behaviour and Bindings’ graphical editor.

(Right-click and select ‘Edit Behaviours’ in the panel background.)

4 Select one of the Label

s. See Figure 12-55.

5 Add a Destination

Behaviour. See Figure 12-55.

A Destination Behaviour and a Binding are added to the ‘Behaviour and Bindings’ editor.

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Enhancing the Appearance of a Panel

6 Double-click on the Destination Behaviour and set its ‘Destination’ property to the same destination that each of the Buttons

control. See Figure 12-56.

7 Click Close .

Destination Behaviour pointed at the same destination monitored as the BPX buttons.

Fig. 12-56: Setting Destination for a Label’s Destination Behaviour

This has set up both of the Label captions to show the Source name of the pointed-to

Destination. To modify one of the Label captions to show the Destination name instead:

8 Select the Label to see its Behaviours and Bindings. See Figure 12-57.

Fig. 12-57: Select a Label

637

Routing Control - XY Routing Panel

Enhancing the Appearance of a Panel

9 Double-click on the Binding to see the Binding’s properties.

See Figure 12-58.

GV Orbit Client Version 2.0.0

User Guide

Fig. 12-58: Edit Binding Properties

10 Change the following properties of the Binding:

• ‘Behaviour Value’ property from ‘Source Name’ to ‘Dest Name’.

• ‘Name’ property from ‘Routed source onto caption’ to ‘Dest name onto caption’.

11 Click Close .

12 Click Save File . Click Save Project .

This has modified our BPX Panel design. See Figure 12-59a.

13 Exercise the BPX panel with the Labels .

When a button is clicked, the resulting route is shown by the labels. See Figure 12-59b.

a) Designed BPX Panel with Labels b) Running BPX Panel with Labels

Fig. 12-59: BPX Panel with Labels: a) Designed; b) Running

638

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Enhancing the Appearance of a Panel

Enhancement - Add Lines

Lines ( Line widgets) or any shapes may be added to a panel.

Fig. 12-60: Added Lines

Additionally, Line widgets can have their visibility controlled from the state of the routing.

This is shown by using the example panel from

Panel Enhancement - Add Labels , on page 636. To do this:

1 Open the panel and show the ‘Behaviour and Bindings’ graphical editor.

2 Add the required lines, in this example, three lines are added.

For each button:

3 Select the button and then view the properties of the associated BPX Behaviour; change the ‘Name’ property to a unique name. (for example, to ‘BPX-1’, ‘BPX-2’, and

‘BPX-3’.)

This gives each BPX Behaviour a unique name.

For each line:

4 Select the line and add a Property

Binding. See Figure 12-61.

639

Routing Control - XY Routing Panel

Enhancing the Appearance of a Panel

GV Orbit Client Version 2.0.0

User Guide

Fig. 12-61: Add Property Binding

5 Double-click on the added Property Binding to edit its properties.

6 Change the following Property

Binding property values: (See Figure 12-62.)

• ‘Source Behaviour’, select a unique BPX Behaviour. For example, ‘BPX-1’,or ‘BPX-2’, or ‘BPX-3’.

• ‘Behaviour value’ to ‘Is Routed’.

• ‘Property to Bind’ to ‘Visibility’.

Fig. 12-62: Added Property Binding

7 Click Close .

This has set the visibility of a line to be controlled by the routing status of the BPX

Behaviour associated to a Button .

Do this for each line and select a unique BPX Behaviour name each time.

640

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

Enhancing the Appearance of a Panel

Fig. 12-63: BPX Panel Example

When the visibilities of all three lines are changed:

8 Click Save File . Click Save Project .

9 Exercise the panel. See Figure 12-64.

The lines simply indicate the route that is made when clicking buttons.

641

Routing Control - XY Routing Panel

Enhancing the Appearance of a Panel

Fig. 12-64: Exercising BPX Panel with Lines

GV Orbit Client Version 2.0.0

User Guide

Click button:

Route is made and a line indicates the routing made.

Click Button:

Route is made and a line indicates the routing made.

Click Button:

Route is made and a line indicates the routing made.

642

GV Orbit Client Version 2.0.0

User Guide

Routing Control - XY Routing Panel

How to Embed an XY Panel into a Custom User Panel

An XY Panel may be embedded into an XY Routing Panel C&M project screen as an GV Orbit

‘Component’.

To embed:

1 Open the GV Orbit project containing the XY Panel and a C&M project screen.

Firstly, check that the overall XY Panel size is just bigger than the widgets it contains. To do this:

2 Open the XY Panel and check the size values in the Properties box.

( Properties box: Screen > Dimensions > Page Size > ‘Width’ and ‘Height’.)

3 If the panel size needs adjusting:

• right-click in the panel background and select ‘Resize to Widgets’, and/or

• adjust the background’s screen ‘Width’ and ‘Height’ properties directly.

4 Close the XY Panel.

Now embed the XY Panel into a C&M project screen:

5 Open a C&M screen.

6 Drag an XY panel from the Project window onto the C&M project screen.

and release. See Figure 12-65.

Drag panel onto screen

Fig. 12-65: Drag on an XY Panel

The panel object is like a GV Orbit component object on a C&M project screen.

7 Resize the panel object as required.

8 Click Save File . Click Save Project .

9 Run the C&M screen and exercise the XY Panel on the screen.

One or more instances of an XY panel on a screen can be used.

643

Routing Control - XY Routing Panel

How to Embed an XY Panel into a Custom User Panel

GV Orbit Client Version 2.0.0

User Guide

644

Introduction

Lite Professional



Enterprise



A multiviewer cluster ( MV Cluster ) is a group of multiple MV-8 Series multiviewer devices in a GV Orbit system which are all acting together to serve one or more video walls. The cluster is treated as one multiviewer resource, rather than as a set of single, individual multiviewer devices.

All of the video walls served by the multiviewer cluster are designed in a single ‘Clustered

Multiviewer’ project in GV Orbit Client. This is done using the ‘ Room Editor ’ tool and an MV

Cluster Manager service is required to be running on a GV Orbit server. The resulting video wall(s) are managed at a higher level (at a ‘cluster-level’) and router destinations are referred to in operation rather than video wall tiles or multiviewer inputs.

645

Multiviewer Cluster

MV Cluster Information

GV Orbit Client Version 2.0.0

User Guide

MV Cluster Information

What is an MV Cluster?

An MV Cluster is a cluster of multiviewer devices configured together and all acting together to serve one or more video walls. An MV cluster contains one or more multiviewer devices.

Number of

Multiviewer

Devices

Table 13-1: MV Cluster Numbers for MV-8 Series Multiviewers

Number of head display outputs: Number of video wall tiles: per device maximum available per device per video wall

2 up to 12 up to 12

48 up to 48 up to 48 * 2 (=96)

...

Cluster a up to 12

...

up to 12

...

12 * N

Cluster

...

48 up to 48 * 3 (=144)

...

up to 48 * N

Cluster a.The number of devices in an MV Cluster has no fixed limit. Please see

MV Cluster Size for more

information.

MV Cluster Size

The number of devices in an MV Cluster ( N

Cluster

) has no fixed limit: The number of multiviewers that GV

Orbit Client and the MV Cluster Manager service can handle has no real limit.

However, in practice, limiting factors are anticipated. The maximum number of MV-8 Series multiviewers in an MV Cluster ( N

ClusterMax

) is determined by performance and various system factors, including:

• GV Orbit system size; and

• network speed.

Please contact

Grass Valley Technical Support for further information on

ClusterMax for specific use cases.

Defining Video Walls for an MV Cluster

A user can define a set of video walls for a broadcast production studio or OB truck using the Grass Valley GV Orbit Client tool with a ‘Clustered MV’ project. The video walls are all served by a cluster of MV-8 Series multiviewers.

GV Orbit Client is used along with GV Orbit system services. Video walls are defined and managed independently from the individual multiviewer devices used. Video wall tiles are referred to by their router destination name.

Additionally, for a ‘Clustered MV’ GV Orbit project, TSL tally settings and audio bars configuration can be done for each whole video wall.

646

GV Orbit Client Version 2.0.0

User Guide

Multiviewer Cluster

What is a Clustered Multiviewer Project?

MV-8XX Multiviewer Cluster Example

Fig. 13-1: Video Walls Served by Multiviewer Cluster (Example shown has an MV Cluster of 6 Devices)

What is a Clustered Multiviewer Project?

A GV Orbit Clustered MV project (Clustered MV project) enables a user to define a set of video walls for a broadcast production studio or OB truck served by an MV Cluster.

The video walls can each comprise one or more display monitors. One or more video walls may be defined, all served by a cluster of multiviewer devices.

All of the video walls are designed in one ‘Clustered MV’ project, which then holds the designs of one or more video walls for a studio or an OB truck.

Overall TSL tally set up and Audio Bars audio channel configuration of audio bars is also integrated and handled within such a project.

The project is stored centrally on the GV Orbit server and the entire video wall design is then automatically parsed and administered across the individual multiviewers in the cluster.

647

Multiviewer Cluster

What is a Clustered Multiviewer Project?

GV Orbit Client Version 2.0.0

User Guide

Multiviewer Discovery

Is the Multiviewer device on the network?

Yes

Is Multicast data enabled on network?

Yes No

Multiviewer is automatically discovered by GV Orbit Client for the

Clustered MV project.

Require manual entry of multiviewer devices into the Clustered MV project.

Add the device to the network.

Video Wall Design

Video walls are formed from a physical arrangement of one or more display monitors and each display monitor is driven from any one of the multiviewer head display outputs available from the multiviewer cluster. Video wall tile layouts can be applied and layouts for the whole video wall and also for individual monitors can be saved and switched between.

Assignment of router destinations to video tile layouts completes the video wall design.

Finally, the assignment of video sources to video tiles (PiPs) is integrated into the GV Orbit routing control system and the routing of video to wall tile positions can be interactively achieved.

Deployment

Deployment is a one-step process, requiring the finished project to be simply pushed to the

GV Orbit server. Behind the scenes, the video wall designs are then automatically translated into constituent, individual ‘multiviewer projects’ which are targeted at each individual multiviewer of the cluster. The constituent projects are automatically pushed out to the individual multiviewer devices.

IMPORTANT

Multiviewers should be operated either in a clustered mode or as individual, non -clustered single-multiviewers.

Changing readily between these operational modes is not supported.

Recommendation:

All multiviewer set-up and configuration is carried out fully for the intended mode of operation.

648

GV Orbit Client Version 2.0.0

User Guide

Multiviewer Cluster

What is a Clustered Multiviewer Project?

Clustered MV project vs. Multiviewer Project

A Clustered MV project is opened, saved, pushed etc. in a similar way to other GV Orbit

multiviewer projects; the main exceptions/differences are listed in Table 13-2.

Table 13-2: Clustered MV Project Differences

Item

Video wall design tool Room Editor in GV Orbit Client

GV Orbit Project Type

Clustered Multiviewer Multiviewer, or

Connected Multiviewer

Wall Editor a in GV Orbit Client

Multiviewer resource(s) A single multiviewer device.

GV Orbit System

Deployment

Max number Video Walls

(

One or more multiviewer devices.

Cluster

devices in an MV Cluster)

Required, running a MV Cluster

Manager Service

Push project to a

GV Orbit server repository.

up to 12x N

Cluster

Can operate with or without a GV

Orbit system

Push project to a single multiviewer device.

Max number Video Tiles up to 48x N

Cluster

Video Wall Arrangement Flexible Constrained

Video Wall Layouts

Monitor-level Layouts

Yes, Room Layout

Yes, Monitor Layout

No.

Yes, Wall Layout a.For information on the Wall Editor, please refer to Orbit documentation.

Use a Clustered MV project when defining and managing video walls from a cluster of MV-

8xx multiviewers.

649

Multiviewer Cluster

What is an MV Cluster Manager?

GV Orbit Client Version 2.0.0

User Guide

Room Editor vs Wall Editor

Wall Editor - Both the original Orbit Client tool and the current GV Orbit Client tool allow configuration of video walls from single multiviewers using the original GV Orbit

‘Multiviewer’ type projects and the Wall Editor tool (refer to Orbit documentation).

Room Editor GV Orbit additionally allows configuration of video walls from a multiviewer cluster with a ‘Clustered MV’ project. This is done via the new Room Editor tool in GV Orbit

Client with the MV Cluster Manager service running on a GV Orbit server.

Note: Room Editor vs Wall Editor :

MV-8 Series multiviewer(s)

Cluster of one or more

Single, individual

Client tool?

GV Orbit project type?

Minimum system configuration

Uses MV Cluster

Manager service?

Room Editor

Clustered

Multiviewer

GV Orbit system with server

Yes, an MV Cluster

Manager service is required.

a.For information about the Wall Editor, refer to Orbit documentation.

Wall Editor a

Multiviewer

None

Single Multiviewer as an MV Cluster

A single multiviewer may be considered as an ‘ MV Cluster of one’ and a video wall design can be generated for a single multiviewer with the Room Editor in a ‘Clustered MV’ project.

Note: For an MV Cluster of any size, an MV Cluster Manager service is required to be running on a GV Orbit server.

What is an MV Cluster Manager?

The MV Cluster Manager is a service running on the GV Orbit server which automatically translates a GV Orbit ‘Clustered MV’ project into its constituent, single-multiviewer projects.

The service automatically manages each individual multiviewer device of an MV Cluster . A

GV Orbit system may have zero or one such service.

Once it is configured, the service will:

• check for the availability of multiviewers in the room; and

• put a watch on the relevant GV Orbit server repositories for any project changes.

The service processes any detected repository project changes and rebuilds any constituent single-multiviewer projects where necessary, automatically pushing the projects to the appropriate multiviewer device(s).

650

GV Orbit Client Version 2.0.0

User Guide

Multiviewer Cluster

Video Wall Configuration Workflow (Clustered Multiviewers)

The service will alert the GV Orbit system to any off-line multiviewers and missing repositories.

The service is automatically discovered by a GV Orbit Client in a GV Orbit system and a user can then create a ‘Clustered MV’ project.

Configuring an MV Cluster Manager Service

The MV Cluster Manager service configuration is carried out on the GV Orbit server.

Refer to: Please refer to the GV Orbit Admin Guide for information about GV

Orbit services, including configuring the MV Cluster Manager service.

The following settings can be configured from the MV Cluster Manager service’s configuration page on the GV Orbit server:

• Service Settings:

• GVOP Client Domain ID number for the service to use.

• Network interface(s) on the GV Orbit server for the service to use.

• RollCall address of the service in the GV Orbit system.

• A friendly name for the service, to be used in a GV Orbit Client’s Network window.

• Project Settings:

• GV Orbit server repository name of the Clustered MV project for the service to use.

Note: The ‘Project Settings’ may be set up separately later, when a

‘Clustered MV’ project has been created along with its repository.

Video Wall Configuration Workflow (Clustered Multiviewers)

This user guide describes the configuration and operation of clustered MV-8XX multiviewers in a GV Orbit control and monitoring system for multiple video walls, for example in an OB truck environment.

This chapter has provided some MV Cluster definitions. It proceeds to provide some MV

Cluster information:

Configuring an MV Cluster Manager Service , on page 651.

Creating a New Clustered Multiviewer Project for an MV Cluster , on page 653.

Clustered MV Project Screens , on page 664.

Managing Multiviewer Cluster Information in a Project , on page 667.

Additionally, the workflow description is continued in further user guide chapters:

5 Chapter 14, MV Cluster - Room Editor

: a

Room Editor Introduction , on page 671.

Room Editor Workflow , on page 684.

Step 1: Create a Room , on page 687.

Step 2: Arrange Monitors and Assign Multiviewer Outputs , on page 689.

Step 3a: Design Layout - Assign Tile Grid Layouts to a Video Wall , on page 701.

651

Multiviewer Cluster

Video Wall Configuration Workflow (Clustered Multiviewers)

GV Orbit Client Version 2.0.0

User Guide f

Step 3b: Create Optional Alternative Layouts for a Video Wall , on page 710.

Step 4a: Assign Destinations to Tile Positions , on page 719

Step 5a: X/Y Routing Video Sources to Tiles , on page 741.

Also see Chapter 15 MV Cluster - TSL Tally Configuration

, on page 757, and Chapter 16

Audio Bars Configuration , on page 785.

652

GV Orbit Client Version 2.0.0

User Guide

Multiviewer Cluster

Creating a New Clustered Multiviewer Project for an MV Cluster

The video walls served by an MV Cluster are defined with a ‘Clustered Multiviewer’ Project in GV Orbit Client.

Procedure

To create a new ‘Clustered Multiviewer’ project (Clustered MV project) in GV Orbit Client:

Step 1: Create and Connect a Project to a GV Orbit Server

1 Open GV Orbit Client.

The initial screen is shown.

Fig. 13-2: Initial Screen of GV Orbit Client

2 Select New Project on the initial screen.

The New Project dialog is shown.

653

Multiviewer Cluster

Procedure

GV Orbit Client Version 2.0.0

User Guide

Select Clustered Multiviewer project type.

Enter a Name for the new project.

Browse to a folder location.

Fig. 13-3: New Project Dialog

3 Select the Clustered Multiviewer

project type. (See Figure 13-3.)

4 Enter a Name for the new project in the ‘Details’ section.

This is a name for the local storage of project information.

5 Browse to a folder location (local or network) for the project to be stored in while the multiviewer video walls are being designed.

Note: Folder Location:

The folder location must be accessible from the client computer running the GV Orbit Client tool. This location is used while the project is being edited.

When the editing is complete and the project is ready to be deployed, it is pushed from the GV Orbit Client to a central repository location on the GV Orbit server of the GV Orbit system.

6 Click Choose to select the folder.

654

Fig. 13-4: Filled Out New Project Dialog

7 Click OK in the dialog.

GV Orbit Client Version 2.0.0

User Guide

A Setup

dialog for the project is then shown. See Figure 13-7.

Project Setup Dialog:

Multiviewer Cluster

Procedure

Server 1 IP

Basic system test results

Fig. 13-5: Setup Dialog

In the clustered multiviewer project’s Setup dialog:

8 Set Server 1 IP to the IP address of the GV Orbit server and press Enter.

(For a GV Orbit Server Cluster system, still just enter the IP address of one server. The second server will be discovered automatically in the steps below.)

After the IP address is entered, some basic system tests are carried out using the current, original settings of the Setup dialog.

(This basic system testing includes testing system connectivity and gathering some basic system information from the GV Orbit server.)

The results of these basic system tests are then shown in the Setup dialog’s console window.

Note: The current, original dialog settings will most likely differ from those of the GV Orbit system being connected to. Discrepancies are shown in red-highlighted text in the dialog’s console window. This is normal.

9 After these basic system tests are done, any differences in the settings are adopted by the Setup dialog.

Step 2: Repository for Clustered MV Project

When creating a new ‘Clustered Multiviewer’ project, a new repository needs to be created.

(Compare to when opening an existing ‘Clustered Multiviewer ‘project; in this case, an existing repository must be specified, see

Open an Existing Clustered Multiviewer Project , on page 659.)

655

Multiviewer Cluster

Procedure

To Create a New Repository for the Project:

In the Setup dialog, to create a new Repository to be used:

1 At the Repository setting, click New .

GV Orbit Client Version 2.0.0

User Guide

Click New

656

Fig. 13-6: Click New in Setup Dialog

The Create Repository dialog is shown.

2 Enter a Name for the new repository on the

GV Orbit server for the ‘Clustered MV’ project to use and press Enter, or click OK .

Note: Characters to use in a Repository Name:

Use only:

• alpha-numeric characters (0 1 2 A B C x y z etc.); and/or

• underscore characters (_); and/or

• tilde characters (~).

Note: Repository Name:

Use a unique and identifiable repository name for the ‘Clustered MV’ project to use. In this way, it is easily identified and found in a list of all repositories on a server.

The new repository name is shown in the Setup dialog.

GV Orbit Client Version 2.0.0

User Guide

Multiviewer Cluster

Procedure

IMPORTANT

If a new Repository has been created during the ‘Clustered MV’ project creation, then the MV Cluster Manage r service repository needs to be configured with the new Repository .

(See the ‘Project Settings‘part of Configuring an MV Cluster Manager

Service , on page 651.)

Step 3: System Re-Test (optional) During Project Setup

With a new or an existing Repository name shown in the Setup dialog, a system re-test can be carried out.

Note: At this point, a system re-test is optional and will now remove any red items in the console pane. Optionally, in the Setup dialog:

1 Click System Test .

This re-does the basic system tests. The results are shown in the console. Any ‘red’ items

from before should now be cleared. See Figure 13-7.

Fig. 13-7: System Re-Test

Step 4: Finally, Create Project

1 Click Apply in the Setup dialog.

The settings are applied to the project and a progress bar appears in the dialog.

657

Multiviewer Cluster

Procedure

GV Orbit Client Version 2.0.0

User Guide

2 While settings are applied, a pop-up dialog may appear, asking if the local project should be updated from the chosen repository:

For a new project where no changes have been made locally, answer Yes .

Fig. 13-8: Update Local Project?

• Click Yes to update the local project from the repository on the server (this will lose any local changes made); or

• Click No to keep any local project changes made (and not pull the project from the repository on the server).

3 While the applying of the settings continues, progress is shown in the progress bar.

4 When the settings changes are all applied, an All Done message pops up.

Fig. 13-9: Applying of Project Settings is All Done

5 Click OK .

6 Close the Setup dialog.

The new Clustered Multiviewer project is created and its Home screen is then shown.

See

Clustered MV Project Home Screen .

Note: The Setup dialog can also be viewed when a GV Orbit project is open by clicking Connections > GV Server in the main menu.

7 Click OK .

The Clustered Multiviewer project information is contained in the local folder, ready for editing. For a newly-created project it is an empty project.

658

GV Orbit Client Version 2.0.0

User Guide

Multiviewer Cluster

Open an Existing Clustered Multiviewer Project

To open an existing ‘Clustered Multiviewer’ project from a repository on the GV Orbit server, the procedure is similar to the procedure for creating a new ‘Clustered Multiviewer’ project

(refer to Creating a New Clustered Multiviewer Project for an MV Cluster , on page 653).

The steps below open an existing project from an existing repository.

Procedure

Step 1: Create and Connect

1 Carry out the steps in

Step 1: Create and Connect a Project to a GV Orbit Server , on page 653.

This creates an empty, locally-stored project.

Step 2: Repository for Clustered MV Project

When opening a Clustered MV project from a repository, an existing repository must be specified:

To specify an existing Repository for the project, in the Setup dialog:

1 At the Repository drop-down box, select a Repository from the drop-down list. (See

Figure 13-10.)

The repository must be a ‘Clustered Multiviewer’ repository.

Click on drop-down arrow Select an existing Repository

Fig. 13-10: Select Existing Repository

The selected Repository name is shown in the Setup dialog.

Step 3: System Re-Test (optional)

With a Repository name shown in the Setup dialog, a system re-test can be carried out.

1 Carry out the steps in

Step 3: System Re-Test (optional) During Project Setup , on page 657.

659

Multiviewer Cluster

Procedure

GV Orbit Client Version 2.0.0

User Guide

Step 4: Finally, Open the Project from the Repository

1 Click Apply in the Setup dialog.

The settings are applied to the project and a progress bar appears in the dialog.

2 While settings are applied, a pop-up dialog may appear, asking if the local project should be updated from the chosen repository:

For a new project where no changes have been made locally, answer Yes .

Fig. 13-11: Update Local Project?

• Click Yes to update the local project from the repository on the server (this will lose any local changes made); or

• Click No to keep any local project changes made (and not pull the project from the repository on the server).

Note: To edit an existing repository project information on a new PC, then click Yes to pull the existing project information from the repository into the newly created ‘Clustered MV’ project.

If the user clicks No here, then subsequent pushing back to the repository will overwrite the existing project information in the repository.

3 While the applying of the settings continues, progress is shown in the progress bar.

4 When the settings changes are all applied, an All Done message pops up.

Fig. 13-12: Applying of Project Settings is All Done

5 Click OK .

6 Close the Setup dialog.

The exiting Clustered Multiviewer project is opened and its Home screen is then

shown. See Clustered MV Project Home Screen

Note: The Setup dialog can also be viewed when a GV Orbit project is open by clicking Connections > GV Server in the main menu.

7 Click OK .

The Clustered Multiviewer project information is contained in the local folder, ready for editing. For a newly-created project it is an empty project.

660

GV Orbit Client Version 2.0.0

User Guide

Multiviewer Cluster

Note: The Home Page is not automatically refreshed, and new Room files will not be shown.

Close and re-open the project to refresh and then see files pulled from the repository.

Procedure

661

Multiviewer Cluster

Deploying a Clustered Multiviewer Project (Push/Pull)

GV Orbit Client Version 2.0.0

User Guide

Deploying a Clustered Multiviewer Project (Push/Pull)

For deployment, a Clustered MV project is pushed to a central store on the GV Orbit server, for example, to the Repository . There is one project per Repository .

Compare this to a single-multiviewer project: that is for a non -clustered multiviewer device, in which case the project is pushed to the multiviewer itself.

Push Project to Repository

To send a locally-saved and edited project to the Repository for automatic deployment on the multiviewer cluster by the MV Cluster Manager Service on the GV Orbit server:

1 Click Push in the main tool bar.

Fig. 13-13: Push in Tool Bar

A Choose Projects dialog is shown.

662

Fig. 13-14: Choose Push

2 Ensure that the project Repository to be pushed is selected (highlighted in blue) in the

dialog. See Figure 13-14.

3 Click OK .

The project information is pushed to the Repository.

4 When the Push is done, a Push dialog is shown.

Fig. 13-15: Push Done

5 Click OK to close the Push dialog.

GV Orbit Client Version 2.0.0

User Guide

Multiviewer Cluster

Pull Project from Repository

To get a project from a Repository into an opened project for editing and/or locally saving:

1 Click Pull in the main tool bar.

Fig. 13-16: Pull in Tool Bar

A Choose Projects dialog is shown.

Fig. 13-17: Choose Pull

2 Ensure that the project Repository to be pulled is selected (highlighted in blue) in the

dialog. See Figure 13-17.

3 Click OK .

The project information is pulled from the Repository.

4 When the Pull is done, a Pull dialog is shown.

Fig. 13-18: Pull Done

5 Click OK to close the Pull dialog.

Note: For best practice, Pull a project before starting to edit it.

This ensure that the most up to date project information is used.

If there are any conflicts between locally-stored project information and the repository, then the user is prompted. The user may then either discard their changes, or keep their changes and discard any server-side changes.

663

Multiviewer Cluster

Clustered MV Project Screens

GV Orbit Client Version 2.0.0

User Guide

Clustered MV Project Screens

Clustered MV Project Home Screen

The Home screen of a Clustered Multiviewer

project is shown in Figure 13-19.

Main menu bar

Main tool bar

Project name

Click Edit to edit Project name

Local path to project folder

Click ‘Multiviewer > Multiviewer Cluster’ in the main menu for information on the multiviewers in the MV Cluster .

Click Rooms icon to create a and open it in the

Fig. 13-19: Clustered Multiviewer Project Home Screen

.room

Room Editor .

file in the project

The Home screen of the Clustered MV project is similar to that for a GV Orbit Multiviewer project; differences include:

• Multiviewer Cluster dialog which lists the multiviewers of the cluster.

(Main menu item ‘Multiviewer -> Multiviewer Cluster’.)

• Rooms icon on the Home screen which allows the user to create .room

files and edit them in the Room Editor

. (See Chapter 14, MV Cluster - Room Editor , on page 671.)

• Project window has a ‘rooms’ sub-folder for .room

files.

The large icons are similar to (non-clustered) multiviewer projects:

• Manage Users

- Set up project users and their roles. (See Chapter 4, Manage Users , on page 159.)

664

GV Orbit Client Version 2.0.0

User Guide

Multiviewer Cluster

Clustered MV Room Editor Screen

• Themes - Edit or create new on-screen appearance styles for graphical widgets for use on the video wall.

• Rooms - Edit or create .room

file(s) with the Room Editor tool for the ‘Clustered

Multiviewer’ project. (See Chapter 14, MV Cluster - Room Editor , on page 671.)

• Tiles - Edit or create new Custom Tiles for use on the video wall.

Main Menu Items

Please see Main Menu Items , on page 145.

Main Tool Bar Items

Please see Main Tool Bar Items , on page 151.

Further Tool Bar items are shown when a multiviewer video wall is open. See

Main Tool Bar with Room Editor Open .

Clustered MV Room Editor Screen

The Home screen of the Room Editor

is shown in Figure 13-20.

Main menu bar

Main tool bar

Project window

.room

file open in Room Editor tab window

Room Editor tool bar Properties Box

Network window

Fig. 13-20: Clustered Multiviewer Room Editor Screen

665

Multiviewer Cluster

Clustered MV Room Editor Screen

GV Orbit Client Version 2.0.0

User Guide

For further description of the Room Editor

, please see Chapter 14, MV Cluster - Room

Editor , on page 671.

Main Tool Bar with Room Editor Open

Additional tool bat icons are shown here. See

Main Tool Bar Items

for the other icons.

Dock/Undock the active window

Set the active window to full-screen mode

Display drawing grid

Properties window

Run/Design Mode shown in Design mode)

Graphic object alignment controls,

see Graphic Object Alignment Controls , on page 153

Graphic object layer

Options

(Tools > Options in main menu)

Zoom stage screen in/out

Fig. 13-21: Clustered Multiviewer Main Tools Bar with Room Editor Screen Open

666

GV Orbit Client Version 2.0.0

User Guide

Multiviewer Cluster

Managing Multiviewer Cluster Information in a Project

The multiviewers in a multiviewer cluster are automatically discovered by GV Orbit where a network allows multicast discovery data packets.

In addition, a user can manually add one or more networked multiviewers to the cluster.

Note: Manual entry of multiviewer devices is required where a network does not have multicast data enabled.

View/Edit Multiviewer Information about Multiviewers in the Cluster

Procedure

To view information about each multiviewer in the multiviewer cluster:

1 Click ‘Multiviewer > Multiviewer Cluster’ in the GV Orbit Client main menu.

The Multiviewer Cluster

dialog is shown. See Figure 13-22.

The dialog shows the auto-discovered multiviewers of the cluster.

IP address

RollCall address Number of supported, licensed multiviewer head display outputs

Multiviewer output resolution

Fig. 13-22: Multiviewer Cluster Dialog

In the Multiviewer Cluster dialog, the following should be manually set up:

2 Select the number of ‘Heads’ that are licensed for each multiviewer in the list.

3 Select the output ‘Resolution’ for the multiviewers.

4 Click OK .

If required, multiviewers can be explicitly added, see

Adding Multiviewers Explicitly .

Note: The head display outputs of an MV-8 Series multiviewer all share the same resolution. Select either 1920x1080 or 720x1280.

UHD (4K) is achieved with four outputs and 1080p quad-link.

667

Multiviewer Cluster

Adding Multiviewers Explicitly

GV Orbit Client Version 2.0.0

User Guide

Adding Multiviewers Explicitly

It is possible to add multiviewers to the list in the Multiviewer Cluster dialog. This may be required if, for example, multicast discovery data packets are not allowed on a network.

Procedure

To add multiviewers manually:

1 Click New

to add the information about each multiviewer of the cluster. See Figure 13-

23.

2 Click OK to close the dialog.

3 Click Project -> Save Project in the main menu to save the project locally.

MV-8 Series multiviewer head display outputs all share the same resolution.

Select either 1920x1080 or 720x1280.

Fig. 13-23: Multiviewer Cluster Dialog- Adding New Multiviewer Device

668

GV Orbit Client Version 2.0.0

User Guide

Multiviewer Cluster

Video Walls Etc. Design Workflow for an MV Cluster

For instructions on designing video walls in a ‘Clustered MV’ project see the workflow described in:

• Chapter 14, MV Cluster - Room Editor , on page 671.

Also see these additional design steps:

• Chapter 15 MV Cluster - TSL Tally Configuration , on page 757.

• Chapter 16 Audio Bars Configuration , on page 785.

669

Multiviewer Cluster

Video Walls Etc. Design Workflow for an MV Cluster

GV Orbit Client Version 2.0.0

User Guide

670

Room Editor Introduction

Lite Professional



Enterprise



Room Editor is a facility offered in a ‘Clustered MV’ project in GV Orbit Client. It enables a user to design one or more video walls that are served by a cluster of multiviewers. This allows a user to design and manage all the video walls in a production-facility (for example, studio, or OB truck). The multiviewer devices are automatically discovered by GV Orbit

Client.

Video walls, Rooms

Cluster of multiviewers

Fig. 14-1: Example Facility Schematic - Cluster of Multiviewer Devices Serving a Production Facility

In the

This section defines and describes some terms etc. used when using the Room Editor in GV Orbit Client.

, a user can define and position all of the physical monitor displays for all

their video walls. Assignment of multiviewer devices and outputs to video wall monitors is performed once. Video walls can be fed by any multiviewer output available in the multiviewer cluster and are assigned to router destinations. Assignment of video signals to the video wall for monitoring is integrated into the GV Orbit routing system and carried out with a graphical interface in GV Orbit Client.

671

MV Cluster - Room Editor

What is a Room?

GV Orbit Client Version 2.0.0

User Guide

Subsequent design and management of all the various video walls is then independent of the individual multiviewers in the cluster and video tile positions on the video wall are referred to with router destination names.

The Room Editor also enables a user to set up TSL tally settings and audio bars configuration for a video wall.

This section defines and describes some terms etc. used when using the Room Editor in GV

Orbit Client.

What is a Room?

A Room (also known as a Room file, or, simply, a Room ) is part of a Clustered MV project. A file holds information for a video wall ( Room Design ). There can be more than one Room in a Clustered MV project.

The files are stored in the ‘Clustered MV’ project’s folder structure, in the ‘rooms’ sub-folder, and are accessible from the Project window in GV Orbit Client or from the opening project

Home Page .

672

Cluster of multiviewers

Fig. 14-2: Room Files in a Clustered Multiviewer Project Describe Video Walls

GV Orbit Client Version 2.0.0

User Guide

MV Cluster - Room Editor

What is a Room Design?

A video wall is formed in a ‘Clustered MV’ project from ‘physical’ video monitor displays.

Each video wall design is a Room Design . A user can form a large video wall from multiple

‘physical’ displays arranged and configured. They can be driven from one or more multiviewer devices from an MV cluster. Video wall tile layouts can be applied and video tiles can be assigned router destinations.

A Room Design is stored in a Room file.

See

Step 1: Create a Room , on page 687, for the workflow steps.

What is Monitor Arrangement and Multiviewer Output Assignment?

As part of a Room Design , a user can configure a large video wall from multiple ‘physical’ displays and driven from one or more multiviewer devices from an MV cluster. a) Arrange Monitors for each video wall a Room Design

Monitors

Cluster of multiviewers b) Assign a Multiviewer Output to Each Monitor

Fig. 14-3: Room Designs: a) Arranging Monitors; b) Assigning and Configuring Multiviewer

Outputs.

673

MV Cluster - Room Editor

What is Room Design Layout?

GV Orbit Client Version 2.0.0

User Guide

Monitor Arrangement includes:

1 Creating a representation of a large video monitor wall by positioning ‘physical’ displays on a ‘stage’.

2 Defining each display, including:

• Display size, geometry.

• Type: single HD, or quad-split for UHD.

• Orientation: Vertical or Horizontal.

Note: A UHD monitor is fed from four MV-8 Series multiviewer “HD” multiviewer outputs. These must be multiviewer outputs from the same multiviewer device.

Note: Monitor aspect ratio is assumed to be 16:9.

Assign Outputs includes:

3 Assigning a multiviewer output to each physical monitor display.

A monitor arrangement and assigned outputs in a Room file can be saved locally and, when complete, the Room Design can be saved centrally on a GV Orbit server in a

‘Clustered Multiviewer’ project.

See

Step 2: Arrange Monitors and Assign Multiviewer Outputs , on page 689, for the

workflow steps.

What is Room Design Layout?

This defines the arrangement of tiles used in a project for each video wall monitor.

The arrangement of tiles plus their connection to multiviewer inputs on a monitor is termed its Layout.

674

GV Orbit Client Version 2.0.0

User Guide

Tiles

MV Cluster - Room Editor

What is a Tile-Grid?

Tile layouts added to video wall monitors

Fig. 14-4: Video Wall Design Layout

Layout Workflow

For a created Room Design , for each monitor:

• A tile-grid is applied from a selection of templates (for example, 2x2, 3x3 etc.) to position tiles and fine-positioning can be done.

• Each tile type is then defined (for example, video tile, audio tile, or custom tile).

This has prepared a basic Design Layout in a Room Design .

(See What is a Monitor Layout?

, and What is a Room Layout?

)

See

Step 3a: Design Layout - Assign Tile Grid Layouts to a Video Wall , on page 701, for the

workflow steps.

What is a Tile-Grid?

A tile-grid determines the position and size of tiles on a monitor, irrespective of tile type.

For example, a tile-grid may comprise:

• 3x3 tiles; or of

• one larger, central tile surrounded by twelve smaller tiles .

A tile-grid includes the assignment of multiviewer inputs and router destinations to each tile position in the grid.

Tile-Grid Excludes Tile Types

A tile-grid excludes the tile types that populate the tile-grid.

675

MV Cluster - Room Editor

What is a Monitor Layout?

GV Orbit Client Version 2.0.0

User Guide

Note: Tile-grid + Tile types = Monitor Layout .

(See

What is a Monitor Layout?

In a project, monitors on the video wall are each configured to show a tile-grid layout, either from pre-configured grids (2x2 or 3x3 etc.), or from user-defined grids. These

‘monitor layouts‘ then make up the layout of the entire video wall.

Further, an individual monitor may be set up with a set of two or more alternative tile-grid layouts which can be available to the monitor at run time. (For example, there may be a 2x2,

3x3, a 4x4 tile grid and a user-defined tile grid layout in the set of alternative layouts to select from at run time on the monitor.)

These alternative layouts are saved for an individual monitor for selecting at run time on the video wall. These are called Monitor Layouts and they apply to individual monitors on the video wall.

These ‘monitor-level’ layouts form part of the overall Layout Configuration .

Note: Live-Selecting of Monitor Layouts:

Monitor Layouts are live-selectable.

( Monitor Layout in the Room Editor tool is equivalent to

Wall Layout in the Wall Editor tool in GV Orbit Client.)

Monitor Layouts can be created (see

Create a New Monitor Layout , on page 710).

Monitor Layouts

can be selected live for a video wall in X/Y Routing mode (see Step 5b:

Change Layouts in X/Y Routing Mode , on page 750).

What is a Room Layout?

A Room Layout is a snapshot of Monitor Layouts across the monitors on a video wall. A

Room Design can have one or more Room Layouts to select from. This ‘room-level’ layout applies across a whole video wall in a Room .

(See Step 3b: Create Optional Alternative Layouts for a Video Wall , on page 710, for the

workflow steps.)

Room Layouts enable a video wall to have various optional, alternative, similar layouts to

use for different scenarios. Table 14-1 shows some possible example combinations.

676

GV Orbit Client Version 2.0.0

User Guide

MV Cluster - Room Editor

What is Destination Assignment for a Room?

Table 14-1: Example Room Layouts with different Monitor Layouts Combinations

Monitor Layouts

Monitor 1

Monitor Layouts

Monitor 2

Monitor Layouts

Mon

Mon 5

Monitor

Layouts

Mon

Room Layouts

Soccer Layout 1

Soccer Layout 2

Soccer Layout 3

Hockey Layout 1

Hockey Layout 1b

Hockey Layout 2

Hockey Layout 3



 



  

 

  

   

 

  

 

Room Layouts can be created (see

Create a Room Layout for a Video Wall , on page 715).

Room Layouts can be selected live for a video wall in X/Y Routing mode (see

Step 5b:

Change Layouts in X/Y Routing Mode , on page 750) and, in this mode, they may also be

created live and saved.

What is Destination Assignment for a Room?

Assignment of router destinations to tile positions on the video wall tile-grid allows the user to manage video walls, and their specifically tile positions, in terms of router destinations.

Assignment of destinations is done for all video walls in a Clustered MV project (for example, for all Rooms in the project). There are two destination assignment mechanisms that can be used:

• Static Destination Assignment

- see What is Static Destination Assignment?

, on page 678.

• Dynamic Destination Assignment - see

What is Dynamic Destination Assignment?

, on page 679.

677

MV Cluster - Room Editor

What is Static Destination Assignment?

GV Orbit Client Version 2.0.0

User Guide

Router destinations assigned to each tile position.

Fig. 14-5: Video Wall - Assigned Destinations

TSL Configuration and Audio Bars Configuration

Additionally, this Room Editor mode allows:

• TSL settings to be configured globally for the Room .

(See Chapter 15, MV Cluster - TSL Tally Configuration , on page 757.)

• Audio bar configuration for Audio Bars in on-screen graphical widgets to be configured globally for the Room .

(See Chapter 16, Audio Bars Configuration , on page 785.)

What is Static Destination Assignment?

Static Destination Assignment is where one, or more, or all video tiles on video walls are manually assigned specific router destinations. It may be implemented partly or fully in a system. Full static assignment is suitable in routing systems where each video tile on each video wall from each multiviewer is assigned a fixed, specific router destination, which needs to remain static throughout routing operation. (For example, this may be suitable for systems with third-party router controllers.)

For a created Room Design , for each monitor in a video wall, the workflow for static destination assignment is:

1 Router destinations are manually mapped to multiviewer inputs for all devices in the

MV cluster.

2 Destinations are then manually assigned to tile positions on the video walls.

This has prepared the Destination Assignments for monitors in a Room . The multiviewers are ready have signals routed to them.

678

GV Orbit Client Version 2.0.0

User Guide

MV Cluster - Room Editor

What is Dynamic Destination Assignment?

Dynamic Destination Assignment implements routing based on video wall tiles rather than on router destinations. This is made possible with the integrated nature of multiviewing and routing in a GV Orbit system.

The assignment of router destinations to video tiles is done at run time by a GV Orbit service. This keeps track of the current video wall active layouts for each multiviewer. The service then knows which multiviewer inputs are actively feeding video tiles and which are free. This information is shared with the GV Orbit system.

Note: The GV Orbit Multiviewer Cluster Manager Service (MVCMS) is required for the dynamic destinations assignment to function.

Upon a video wall layout change, the service re-assigns destinations on the fly to meet the needs of the newly switched-to layout.

In this way:

• A user does not have to keep track of multiviewer input usage across different video wall layouts.

• Multiviewer inputs (up to 48 per multiviewer) can flexibly accommodate the needs of different video wall layouts.

• It is easier for a user to design video walls, because dynamic destination assignment is the default on video tiles from the outset.

( Note: A video tile can still be set to a static destination, preventing the destination to be assigned dynamically if required.)

Note: TSL assignments made will automatically follow any destination reassignments done in dynamic destination assignment mode.

679

MV Cluster - Room Editor

What is X/Y Routing Source Assignment for a Room?

GV Orbit Client Version 2.0.0

User Guide

What is X/Y Routing Source Assignment for a Room?

The final step in designing the video wall ( Room ) involves routing sources to all of the tile positions in each monitor tile-grid. This is done with an integrated, easy-to-use, graphical routing panel enabling the user to route by selecting sources and destination tiles.

Router sources assigned to each tile position.

Fig. 14-6: Video Wall - Routed Sources

The ‘X/Y Routing’ tool mixes a graphical representation of the monitor wall with a (router) source selection panel. The monitor wall representation is the (router) destination selection panel.

A source can easily be assigned (routed) to a tile position on a monitor of a video wall.

See

Step 5a: X/Y Routing Video Sources to Tiles , on page 741, for the workflow steps.

Routing Sources Workflow

The workflow for each video tile position on a monitor is:

1 select the tile position in the monitor’s tile-grid (this is the destination to route to); and

2 select the source.

When a route is made, all levels are routed. and tile positions on the tile-grid show their logical names.

680

GV Orbit Client Version 2.0.0

User Guide

Room Editor Home Screen

Video wall design open in Room Editor tab window

Room Editor Tool Bar

MV Cluster - Room Editor

Room Editor Home Screen

Fig. 14-7: Room Editor Screen Example

The Room Editor stores video wall design information for one or more video walls in a single ‘Clustered MV’ GV Orbit project (see

What is a Clustered Multiviewer Project?

). Each video wall design is stored in a Room

file (see What is a Room?

) in the project.

Room Editor Workflow Overview

Room Editor allows a user to easily create video walls. This is an overview of the workflow:

1 Create monitor wall arrangements from one or more monitors and assign multiviewer outputs.

2 Create the layout - Assign tile-grids to each monitor in the video wall and populate with tile types, and create all room layouts and monitor layouts.

3 Assign router video destinations to video wall tile positions in the grid.

4 Assign video sources to video wall tile positions in the tile-grid.

The Room Editor workflow steps are outlined in

Room Editor Workflow , on page 684. The

steps are then fully described in the subsequent sections of this chapter, that is in sections:

Step 1: Create a Room

through to

Step 5a: X/Y Routing Video Sources to Tiles .

681

MV Cluster - Room Editor

Room Editor Tool Bar

GV Orbit Client Version 2.0.0

User Guide

Room Editor Tool Bar

The first few icons in the Room Editor

tool bar (see Figure 14-8) follow the MV Cluster video

wall design’s Room Editor workflow and take the user through the various modes of operation of the Room Editor .

Tool bar icons shown depends on workflow step that is active

Room Editor workflow:

• Select for

Arrange Monitors and Assign MV Outputs Mode

• Select for

Design Layout Mode .

• Select for

Assign Router Destinations Mode

• Select for

X/Y Routing Mode

Fig. 14-8: Room Editor Tool Bar - Main Icons

Arrange Monitors and Assign MV Outputs Mode

Icons in the Room Editor tool bar in this mode:

Click to delete the selected monitor

Fig. 14-9: Room Editor Tool Bar - Arrange Monitors and Assign MV Outputs Mode

Design Layout Mode

Icons in the Room Editor tool bar in this mode:

• Room Layout actions.

• Monitor Layout actions.

• Fine, free-hand positioning of tiles on tile-grid.

• Delete currently-selected item.

• Select all tiles on selected monitor.

Fig. 14-10: Room Editor Tool Bar - Design Layout Mode

682

GV Orbit Client Version 2.0.0

User Guide

Assign Router Destinations Mode

Icons in the Room Editor tool bar in this mode:

MV Cluster - Room Editor

Room Editor Tool Bar

• Room Layout actions.

• Monitor Layout actions.

• Map multiviewer inputs to router destinations.

• Select all tiles on selected monitor.

Fig. 14-11: Room Editor Tool Bar - Assign Router Destinations Mode

X/Y Routing Mode

Icons in the Room Editor tool bar in this mode:

• Room Layout actions.

• Monitor Layout actions.

Fig. 14-12: Room Editor Tool Bar - X/Y Routing Mode

683

MV Cluster - Room Editor

Room Editor Workflow

GV Orbit Client Version 2.0.0

User Guide

Room Editor Workflow

The workflow for creating Room designs in the Room Editor is listed here and described in the following sections of this chapter. A prerequisite is a GV Orbit ‘Clustered MV’ project

open in GV Orbit Client. (See Creating a New Clustered Multiviewer Project for an MV

Cluster , on page 653.)

Workflow steps overview:

•

Create a Room (Room File)

•

Arrange Monitors and Assign Multiviewer Outputs

•

Design Room Layout - Assign Tile Grid Layouts

•

Create Optional Alternative Layouts for a Video Wall

•

Assign Router Destinations to Tile Positions

•

Tally Configuration

•

Routing Video Sources to Tile Positions

These steps are outlined in subsequent sections of this chapter, listed as

Workflow

Procedure Steps , on page 686.

Create a Room (Room File)

Firstly, for each video wall, create a Room for each video wall.

See

Step 1: Create a Room , on page 687.

Then, for each Room , create a Room Design to form the video wall design, as described in subsequent sections:

Arrange Monitors and Assign Multiviewer Outputs

See

Step 2: Arrange Monitors and Assign Multiviewer Outputs , on page 689.

Position monitors on a ‘stage’; define monitor types (includes size, orientation, single HD or quad-split for UHD); and assign one or more MV outputs to each monitor.

Note: The Assign Multiviewer Outputs mode of the Room Editor does not use ‘Run mode’ ; the ‘Design/Run Mode’ tool bar icon is hidden

Step 3a: Design Layout - Assign Tile Grid Layouts to a Video Wall , on page 701.

Design Room Layout - Assign Tile Grid Layouts

See

684

GV Orbit Client Version 2.0.0

User Guide

MV Cluster - Room Editor

Create Optional Alternative Layouts for a Video Wall

Assign tile-grid templates to the monitors of the video wall; populate with tiles; and customize if required to form the video wall layout. Additionally, manage destinations assigned to the video wall tiles.

Note: Design Room Layout mode of the Room Editor may operate in GV

Orbit Client’s Design or Run Mode .

Step 3b: Create Optional Alternative Layouts for a Video Wall , on page 710.

Create Optional Alternative Layouts for a Video Wall

See

This mode enables creates different layouts for the video monitor wall.

Assign Router Destinations to Tile Positions

See

Step 4a: Assign Destinations to Tile Positions , on page 719.

This mode: maps destinations to multiviewer inputs; assigns destinations to video wall tile positions on each tile-grid; and can also be used to assign TSL settings for the Room .

The mapping made between router destinations and multiviewer inputs needs to be made whether operating in the Dynamic Destination Assignment mode or in the Static

Destination Assignment mode, or in a mixture of both. All the destinations that are mapped to tiles configured for dynamic assignment will be assigned dynamically.

Note: The Assign Router Destinations mode of the Room Editor does not use ‘Run mode’ ; the ‘Design/Run Mode’ tool bar icon is hidden.

Step 4b: Configure TSL Tally Settings for a Room , on page 740.

Tally Configuration

See

Optional at this stage and may be done separately later.

Routing Video Sources to Tile Positions

See

Step 5a: X/Y Routing Video Sources to Tiles , on page 741.

685

MV Cluster - Room Editor

Workflow Procedure Steps

GV Orbit Client Version 2.0.0

User Guide

This mode routes required sources to video tiles for the required video monitoring.

Different video monitor wall layouts can be selected from this Room Editor mode and seen live on the video monitor wall. Additionally, new layouts can be tried and saved.

Note: Routing Video Sources mode of the Room Editor operates in ‘Run

Mode’, allowing live changes on a video wall to be made.