Ross Video Ultrix Router Integration Configuration

Ross Video Ultrix Router Integration Configuration

Configuration Overview

A Ross Video Ultrix router connects to hi in one of three routing modes. Each mode needs a matching Ultrix database configuration and a matching Node configuration in hi. Choose the mode first, then configure both sides. The Multiviewer configuration is independent of the routing mode.

Before You Begin

• Use Node admin and open Inventory > Nodes. See Manage Nodes.

• Confirm the license and minimum hi version in Required Configuration.

• Use Ross DashBoard, or the vendor's configuration tool, to edit the Ultrix database.

• Record the SW-P-08 endpoint address and Port.

• Record the matrix settings of the Ultrix database: the levels and the Source and Destination counts.

• Confirm the network access in Network Requirements. The default SW-P-08 port is 8910.

Configure Embedded Routing

Use this configuration when hi needs only video routing.

Device Configuration

1. Assign the Ultrix system a stable management IP address.

2. Enable the SW-P-08 service and record its port. The default is 8910, which is also the hi default and the Ultrix default for outgoing SW-P-08 connections.

3. Verify the Server Options of the SW-P-08 service. The Matrix Mode option swaps the matrix and level fields, and it is off by default. If routes land on the wrong level or matrix, compare this option with the Level and Matrix values entered in hi.

4. In the Ultrix database, create one level for video only.

5. Fill the Sources and Destinations lists with the SDI inputs and outputs of the router.

6. Record the number of Sources and the number of Destinations.

Example Database

The Sources and Destinations lists use one level. Each row names a signal and points it to an SDI connector of the router. The notation [FrameX/SlotY] stands for the frame and slot of your router. The IDs in the examples are illustrations, so use the IDs of your own database.

In this example the router has 128 Sources and 128 Destinations. Enter 128 as the input count and as the output count in hi.

hi Configuration

1. Add a Probel SW-P-08 Compatible Router Node.

2. Set the port to 8910 and turn off the redundant connection.

3. Set Level to 0 and Matrix to 0.

4. Enter the Source and Destination counts that you recorded.

5. Turn off dummy Crosspoints and create the Node.

hi reads the Source and Destination names from the Ultrix.

Configure Flat Matrix

Use this configuration when hi must embed, de-embed, or shuffle audio.

Device Configuration

1. Complete steps 1 to 3 of Configure Embedded Routing to prepare the SW-P-08 service.

2. Create one level for video and one level for audio.

3. In the Sources and Destinations lists, enter the SDI inputs and outputs on the video level.

4. Identify the Sources that need de-embedded audio and the Destinations that need embedded audio. Omit audio for signals that carry none, such as Multiviewer Heads, or that need none, such as monitors.

5. In the Sources list, enter the de-embedder channels and any MADI connections. Start with the ID after the last video signal and use the audio level.

6. In the Destinations list, enter the embedder channels and any MADI connections. Start with the ID after the last video signal and use the audio level.

Example Database

The video signals come first, on the video level. The audio signals follow, starting with the ID after the last video signal, on the audio level. Each Source or Destination appears on one level only, so the video rows have no audio entry and the audio rows have no video entry.

Omit audio rows for signals that carry no audio, such as Multiviewer Heads and chip cameras, and for Destinations that need none, such as vision mixer inputs and monitors. This saves configuration time. In this example the last video ID is 128, so the video Node uses 128 as its input and output count, and the audio Node uses the last audio ID of each list.

hi Configuration

Create two Probel SW-P-08 Compatible Router Nodes. Use port 8910, no redundant connection, and no dummy Crosspoints for both.

1. Create the Video Node and wait until hi reads the names.

2. Create the Audio Node and wait until hi reads the names.

3. Open the Audio Node.

1. Delete only the duplicate video input and output Ports from the Audio Node.

2. Create Port Containers for the related video and audio inputs and outputs. An embedded route requires hi to switch the video signal and its 16 audio channels, and a Port Container switches them together.

Configure 1+16 Level

Use this configuration when the Ultrix provides one video level and 16 audio levels. A route can only be made inside one level. Breakaway Sources make an audio channel available on every level, so that a route such as CCU 1 CH 1 to REC 1 CH 3 is possible. A SW-P-08 Router Node addresses one level at a time, so this configuration uses the dedicated Ross Ultrix Node.

Device Configuration

1. Complete steps 1 to 3 of Configure Embedded Routing to prepare the SW-P-08 service.

2. In the level setup, create one level for video and 16 levels for audio.

3. In the Sources table, enter every video signal on the first level and its 16 de-embedder channels on the audio levels. Leave out AUX channels that carry MADI.

4. After the last video signal, add one disconnect Source. Assign a disconnect channel on all levels.

5. After the disconnect Source, add the audio breakaway Sources. Leave the video level of each breakaway Source empty.

6. After all breakaway Sources, add MADI or other audio Sources. Enter the same channel on every audio level.

7. In the Destinations table, enter every video signal on the first level and its 16 embedder channels on the audio levels.

Follow these rules for the breakaway Sources:

• Keep the breakaway Sources in exactly the same order as the video Sources.

• Create the breakaway Sources in blocks of 16 channels.

• Enter the same audio channel on all 16 audio levels of each Source.

• Add a block of 16 empty slots for a video Source that has no embedded audio.

Source Table

The Sources table has one video level and 16 audio levels. The table has four blocks, in this order: the video Sources, the disconnect Source, the audio breakaway Sources, and any other audio Sources such as MADI.

Read the table in these four steps:

1. Video Sources: each video Source sits on the video level, and its 16 de-embedder channels sit on the 16 audio levels, one channel for each level. Leave out AUX channels that carry MADI.

2. Disconnect Source: add it directly after the last video Source and before any audio Source. Give it a disconnect channel on every level.

3. Breakaway Sources: add one block of 16 for each video Source, in the same order as the video Sources. Leave the video level empty. Each row carries one audio channel on all 16 audio levels. A video Source without embedded audio still gets a block of 16 empty slots.

4. Other audio Sources: add MADI or other audio Sources after the last breakaway block. Enter the same channel on every audio level.

Destination Table

The Destinations table has the same levels. Every video Destination carries its 16 embedder channels on the audio levels. AUX channels that carry MADI are added in blocks of 16 channels: 1 to 16, 17 to 32, 33 to 48, and 49 to 64.

The tables show the first three audio levels and the sixteenth. Levels 4 to 15 follow the same pattern.

How a Route Resolves

A route can only be made inside one level, and a breakaway Source supplies the same audio channel on every level. The route CCU 1 channel 1 to REC 1 channel 3 therefore resolves to one route on one level. The route takes the breakaway Source CCU 1 CH 1, ID 130, on audio level 3 to Destination REC 1, ID 1, on audio level 3. A video route takes the video Source to the video Destination on the video level.

In this example, enter 130 in First audio channel, because it is the ID of the first breakaway Source. Enter 129 in Map source as Disconnect, because it is the disconnect Source. The IDs in these tables are illustrations. Use the IDs of your own database.

hi Configuration

1. Add an Ultrix Router Node (Ross Video) from the Router Node Family.

2. Enter the highest Source ID as the input count.

3. Enter the highest Destination ID as the output count.

4. Enter the ID of the first audio breakaway Source in First audio channel. hi treats Ports from this number onward as audio.

5. Enter the ID of the disconnect Source in Map source as Disconnect.

6. Create the Node.

7. Wait for the Node to initialize. From hi 2.7.9, hi reads Source labels from the Ultrix through SW-P-08, and it also reads Destination names. Check the Port names, and rename any Port that does not read correctly. See Rename Multiple Labels.

For the other Node settings, see Required Configuration.

Configure Multiviewer and UMD

Use this configuration to send Tally and labels from hi to the Multiviewers integrated in the Ultrix. It does not depend on the routing mode.

Device Configuration

1. In the Ultrix System Status configuration, open the Database tab and confirm that Enable Tally is set.

2. In the Destinations list of the database, assign an ID in the Tally column to every Destination that is a Multiviewer PIP. These IDs are the TSL Screen IDs in hi. The TSL Display ID is always 0.

3. In the Multiviewer layouts, turn on the small Tally check box for every label in the PIPs.

4. Note the TSL listener that you use. The Ultrix listens for TSL 3.1 and TSL 5.0 over TCP and UDP. It also offers TSL 4.0, which this procedure does not use. Use TSL 5.0 over TCP.

5. In the Ultrix connection settings, open the Server Options of the TSL UMD v5.0 service and set Wrapping to Yes. This option wraps the commands for TCP mode. It is off by default, which is the UDP setting.

hi Configuration

1. Add a TSL Based Multiviewer Node. Set the number of inputs to the number of PIPs.

2. Select TSL 5 with TCP and enter port 5729.

3. After you create the Node, set Enable Rotation to Yes and keep Rotation Interval at 1000, its default.

4. For an older Ultrix firmware, turn off Multi-Display Packets and set a Message Delay of 50 ms.

5. Configure the UMD entries with the Screen IDs that you assigned. See Configure UMD Labels.

Common Checks

Verify the Configuration

Confirm that the Node shows a connected state and the expected Source and Destination counts. Compare several names with the Ultrix database. In a non-critical path, switch a test route and confirm the Crosspoint in the Ultrix. In Flat Matrix and 1+16 Level, also route one audio channel to a different audio channel. For the Multiviewer configuration, change a Tally in hi and confirm that the label and Tally of the PIP update on the Ultrix Multiviewer.

Related Pages

• View and Edit Topology to confirm the Signal Path of a test route.