beautypg.com

The external subtitler configuration panel – Grass Valley iTX System v.2.6 User Manual

Page 178

background image

Configuring channel plug-ins

The External Subtitler Configuration panel

You set up iTX to work with an external subtitler in the External Subtitler Configuration panel:

You select the communications protocol for the external subtitler in the Available Protocols

box; the protocol name appears in the text box at the top of the panel.

You enter the i.p. address of the subtitler in the Location box. For a Polistream system, the

entry should be the short name of the Polistream Channel Server (which you can check in the

Polistream Config Client tool).

In the Port box, you enter the number of the port used for communications between iTX and

the subtitling system. For a Polistream system, the required number is the one that the

Polistream Name Exporter uses when communicating with the Name Maintainer on the Output

Server; Screen Subtitling Systems Ltd provide this number. For Cavena, the port number is

4703.

If the Cavena protocol has been selected, a Service ID number must be configured. This is a

number that identifies the STC output to which the STU for the particular iTX channel is

connected.

For a system that has main and back-up Output Server machines, two hardware configurations

are possible:

The master-slave pair of channels may share an external subtitler. For this

configuration, you select Shared Device; only the main Output Server then controls

the subtitler.

The master and slave channels may have separate subtitlers. You then need to ensure

Shared Device is not selected; each Output Server controls its own subtitler, with the

main output being routed into the transmission path.

Note:

An external subtitler requires timecode to be present in the video signal it receives

from the Output Server. If any video clips that iTX is to play out do not contain

timecode, you need to set up iTX to generate it.

More details

, page 184.

For a Polistream system, the network should allow bi-directional UDP

communications.

March 2015

System Administrator Guide

Page 178 of 404

This manual is related to the following products: