Belden, Belden Sending All The Right Signals, and the Belden logo are trademarks or
egistered trademarks of Belden Inc. or its affiliated companies in the United States and
r
other jurisdictions. Grass Valley USA, LLC, Miranda, iTX, Output Server 2, Output Server 1,
TXPlay, TXPlay 2, MediaCache, MediaCache 2, Vertigo XG, XG Inside and iTX Desktop Client
are trademarks or registered trademarks of Grass Valley USA, LLC. Belden Inc., Grass Valley
USA, LLC, and other parties may also have trademark rights in other terms used herein.
Terms and Conditions
Please read the following terms and conditions carefully. By using iTX documentation, you
agree to the following terms and conditions.
Grass Valley hereby grants permission and license
manuals for their own internal business use. Manuals for Grass Valley products may not be
reproduced or transmitted in any form or by any means, electronic or mechanical, including
photocopying and recording, for any purpose unless specifically authorized in writing by
Grass Valley.
A Grass Valley manual may have been revised to reflect changes made to the product
during its manufac
product. Care should be taken to ensure that one obtains the proper manual version for a
specific product serial number.
Information in this document is subject to change without
commitment on the part of Grass Valley.
Warranty information is available in the Support section of the Grass Valley Web site
ww.grassvalley.com).
(w
turing life. Thus, different versions of a manual may exist for any given
Downgrading from Output Server 2 to Output Server 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
iTX Output Server 2
Channel Configuration Guide
iii
Table of Contents
iv
This guide describes the features and functionality of Output Server 2 (OS2), the differences
between Output Server 2 and its predecessor, Output Server 1 (OS1) and the features and
underlying principles of Output Server 2. It also explains how to install or upgrade to
Output Server 2, how to create and configure channels using Output Server 2 and day-today operational and maintenance information for Output Server 2 systems.
Output Server 2 integrates with the current iTX framework, allowing customers to easily
upgrade their existing channels. Working alongside our next generation video engine is
our new automation controller, TXPlay 2, which supports the new features and
functionality that Output Server 2 provides, and our new caching mechanism, Media Cache
2.
Introducing Output Server 2
Output Server 2 has improved standards compliance, more flexibility and greater stability,
and forms the basis for future iTX development. Among the new features and functionality
offered by Output Server 2 are improved image quality, the ability to perform on-air
updates for AFD and duration changes, per stream configuration for Dolby D and E, full
audio processing for XG inside and the ability to perform dual channel or simulcast
broadcast from a single playout server.
Whilst Output Server 2 supersedes the previous video engine, Output Server 1 is still
supported and it is even possible to run both video engines in the same iTX system.
Transitioning to Output Server 2 on page 15.
See
1
Introducing Output Server 2
Comparison Chart - Output Server 1 and Output Server 2
Comparison Chart - Output Server 1 and Output Server 2
The table below details the differences between the Output Server 1 and Output Server 2
service.
FeatureOutput Server 1Output Server 2
AJA Kona 3G SDI I/O cardSupportedSupported from iTX v2.6
AJA Corvid 1 SDI I/O cardSupportedSupported
AJA Corvid 44 SDI I/O cardNot supportedSupported from iTX v2.6
AJA Corvid 88 SDI I/O cardNot supportedSupported from iTX v2.6
Dedicated SDI I/O video card
service
(I/O Device Controller)
Simulcast Not supportedSupported from iTX v2.6
Not availableAvailable from iTX v2.6
Single server dual channel Supported with dual Corvid
L/P SDI I/O Cards only *
On-air update: Active Format
Description (AFD) change
On-air update: Duration
change
Dolby E and D per stream
configuration
XG Inside: Full audio
processing (audio flows from
OS2 to XG and back to OS2)
Output Server audio
configuration: Output group
definitions
Cross conversion: 50hz to
59hz standards
Cross conversion: Same family
of standards. For example:
• 1080i50 <-> 750p50 <-> 625
• 1080i59 <-> 720p59 <-> 525
SCTE104: VANC splice
commands
SCTE104: Multiple operations
within Multiple Operation
Messages
SCTE104: Segmentation
commands to identify local
and national avail inserts)
Not supportedSupported
Not supportedSupported
Not supportedSupported
Not supportedSupported
OptionalMandatory
PermittedNot permitted
SupportedSupported
SupportedSupported
SupportedSupported
SupportedSupported
Supported from iTX v2.6
2
iTX Output Server 2
Channel Configuration Guide
FeatureOutput Server 1Output Server 2
SCTE104: DTMF descriptor
data request operations
Cue to first frameOptionalDefault
Interlaced NTSC SD media -
nterpretation
field i
System message logsAll messages in a single CSV
SupportedSupported
User controlledUser controlled or
automatically detected
(global setting)
iewing the Output
See V
file
Server 2 Engineering Panel on
page 63
Output Server Engineering
onfiguration
C
Located within Engineering
layout of iTX Desktop
Note:
• * Output Server 2 does not support playout servers with dual SDI I/O cards (i.e. two
Corvid L/P cards). If your playout server is equipped with dual SDI I/O cards, only
the card that Windows identifies as device 0 will be used and only in single channel
mode.
• Although iTX 2.x supports the Kona 3G SDI I/O cards, it does not support Kona 3
rd.
ca
About Playout Types for Output Server 2
iTX Output Server 2 supports three different types of playout.
Single Channel Playout
Single channel playout means the channel has a single input and a single output. This
playout type can be used for main channels in any iTX system, including backup channels
running on their own playout servers.
Dual Channel Playout
Located within Output Server
2 user interface
Dual channel playout means there are two independent channels running on a single
playout server, each with a single input and output. This can be used to run a main channel
and the backup of another channel on a single playout server (providing it is equipped with
a Corvid 44 or Corvid 88 SDI I/O card, such as the Grass Valley Playout Appliance 2 server).
Simulcast Playout
In a simulcast system, two channels share two inputs, but have independent outputs. A
typical use case for a simulcast system is to generate HD and SD transmissions from a single
schedule that is loaded on to the main channel. Because the main and simulcast channels
have different requirements for the resolution, aspect ratio control (ARC) and audio output,
the two channels are configured independently.
3
Introducing Output Server 2
Playout Type Support
In order to transmit appropriate branding for a simulcast channel, iTX allows users to
configure event substitution rules, which can be used to swap assets such as logos and CGs
based on their names in the main channel’s schedule.
iTX manages the broadcasting of main and s
networked instances of TXPlay 2, known as a leader/follower network. The main channel in
any iTX system is identified as a leader channel. When a simulcast channel and its
corresponding backup channels are added to the iTX system, they are designated as
followers. See About L
information about the leader/follower model.
Playout Type Support
The table below shows which playout types are available to the supported models of AJA
SDI I/O card:
Playout TypeK3G C1C44 C88 Comment
Single channel
Dual Channel
Simulcast
SimulatorN/ASelect for test channels only.
imulcast channels using a system of
eader/Follower Channel Communication on page 4 for more
Default for all models of SDI I/O card. Use for stand
alone main or backup channels.
Select to configure two channels running on the
same playout server (i.e. channel A main and channel
B backup).
Select if you are configuring a simulcast channel on a
separate playout server or you are configuring main
and simulcast channels on the same playout server.
About Leader/Follower Channel Communication
When configuring a main channel and its backup in Output Server 1, it communicates
between the two channels using a master/slave model. The two channels share the same
configuration, schedule, assets and iTX Desktop controls, and changes to any of these on
the main channel (the master) are also sent to the backup channel (the slave). The backup
also checks the database every 30 seconds and changes to the schedule on the main
channel cause a schedule restore on the backup channel. This results in a delay of up to 30
seconds between schedule changes on the main and backup.
Master/slave operation relies on the status of a
determine which channel should act as the master. In the event of a failover, the backup
channel takes over the transmission of the scheduled programming.
Output Server 2 uses a leader/follower model f
main channel is the leader and its backup channel is the follower; in a simulcast system, the
simulcast channel and its backup channel are also followers. This is known as a
leader/follower network. When the iTX Desktop operator performs a manual control,
schedule change or changes an asset, the leader channel passes these changes on to its
followers and they respond instantaneously. This ensures the channels in the
leader/follower network are always in sync with each other, regardless of the number of
followers.
single router crosspoint (destination) to
or channel communication. This means the
4
Failovers are controlled in the same way as the master/slave model, however, iTX can only
promote main and backup channels to be leader channels; simulcast and simulcast backup
channels can only be followers.
Known limitations of Output Server 2
Output Server 2 has the following known limitations:
• Automatic Loudness Control (ALC) is currently not supported and set to Off by default
in the Output Server 2 Configuration panel.
• Raw audio mode is not supported for MPEG audio codecs.
• When using Dolby E (Auto) output, Dolby Metadata is not supported.
• Squeeze effects are not supported for CGs or logos in either Output Server 2 or Output
Server 1.
• Output Server 2 does not currently support regional sub-channels.
iTX Output Server 2
Channel Configuration Guide
5
Introducing Output Server 2
Known limitations of Output Server 2
6
Preparing for Output Server 2
This chapter discusses the hardware and software prerequisites for operating an Output
Server 2 iTX system, including the additional licenses that may be required. It also provides
an overview of the installation process for new iTX systems and upgrades from Output
Server 1.
Dual channel playoutTo transmit dual channel or simulcast broadcasts, your playout server
l need the following:
Simulcast playout
Vertigo XG InsideWhen XG Inside is enabled, Remote Deskt
wil
• An AJA Corvid 44 or Corvid 88 SDI video card.
• AJA SDI I/O video card driver version 12.1.0.107.
• The I/O Device Controller service (available from iTX v2.6 onwards).
playout server.
License Requirements
The modules that make up the iTX system are individually licensed and add-on
components (such as XG Inside) require their own license to function.
Depending on your system architecture, the following licenses may be required to operate
Output S
• XG Inside graphics on Output Server 2 requires the iT
erver 2:
op must be disabled on the
X IntegratedXG license.
For more information about licensing and the Grass Valley license dongle, please contact:
ensing@grassvalley.com.
itxlic
Installing iTX licenses
The modules that make up the iTX system are individually licensed and add-on
components (such as XG Inside) require their own license to function.
Licenses are stored in
a USB port on the playout server.
To install the iTX license file
1Open the iT
2 Place a copy of the .lic file in the Inbox shared folder of the iTX Framework Server
where the Media Watcher resides.
The license file is automatically ingested by the M
the file disappears from the Inbox folder.
When TXPlay 2 starts it will check that the requir
of the licenses can be checked by running diagnostics on TXPlay 2
.lic files and require a Grass Valley license dongle to be inserted into
X License folder shortcut located on the Windows desktop.
edia Watcher service, at which point
ed licenses have been installed. The status
8
iTX Output Server 2
Channel Configuration Guide
Process Overview - Output Server 2 Installation and Channel
Configuration
The process of installing Output Server 2 and configuring a channel consists of the
following actions:
Step DescriptionSee section(s)
1Install the required licenses and driversPrerequisites and Compatibility
Requirements, on page 7.
2Install the Output Server 2 module on your
yout server.
pla
NOTE: If you have purchased a Grass Valley
P
layout Appliance 2 it will come pre-
installed with Output Server 2.
3Add your first channel, followed by any
subsequent ch
4Start Server Controller on each playout
ver.
ser
5Channel configuration - Output Server 2:
• Confirm your reference input
• Set resolution and frame rate
•Configure ancillary data
• Select XG Inside (if applicable)
• Configure channel delay
• Configure Nielsen watermark (if applicable)
• Configure Dolby metadata
• Configure audio upmixing (if applicable)
•Configure SCTE104
• Configure subtitles (mi
6Channel configuration - iTX Desktop:
• Configure channel routing
• Configure channel communication setup
• Configure audio output
• Configure event substitution for simulcast
ch
annels (is applicable)
• Configure GPI devices
annels.
nimum required setup)
Installing Output Server 2, on page 11.
Adding Channels to an ITX Playout Server,
on page 21.
Setting a Reference, Frame Rate Family and
Output Timing, o
Output Server 2 Channel Configuration, on
page 29.
Output Server 2 Channel Configuration, on
page 29..
n page 29
Upgrading from Output Server 1 to Output Server 2
iTX allows broadcasters to transition from an Output Server 1 system to an Output Server 2
system by running both video engines in parallel within the same iTX system during the
upgrade. This is known as a “mixed Output Server system” and is only recommended
during the upgrade and testing process, and not for day-to-day operation.
ransitioning to Output Server 2 on page 15.
See T
9
Preparing for Output Server 2
Upgrading from Output Server 1 to Output Server 2
10
Installing Output Server 2 on a New System
This chapter discusses how to install the Output Server 2 components on your playout
server and how to create a shared folder to use as a media cache.
IMPORTANT
If you have a Grass Valley Appliance Server 2 playout server, it will be preinstalled with Output Server 2. Therefore you can skip this chapter move on
See Adding Channels to an ITX Playout Server on page 21.
The Output Server 2 module includes other critical components, such as TXPlay 2, Media
Cache 2, File Processing Pipeline, Domain Config Tool and the I/O Device Controller, which
are all installed along with the main Output Server 2 service. Of these components, Media
Cache 2 and TXPlay 2 require user input before the installation is complete.
To perform a new installati
1 Access and open the iTX Installer.
2Right-click the Se
The iTX Se
3Expand the Pla
4Check Ou
5Click OK.
The S
6On the iT
The selected components will install on your playout server.
7 Before the installation completes, the Med
Enter the cache name and location, as described in Creating and Sharing a Media
Cache Folder, below.
8 After creating a media cache folder, the i
At this point you should add any channels that you require on this playout server. See
Adding Channels to an ITX Playout Server on
9 Complete the installation of any other iTX modules you have selected, as described in
the iT
lect Software to Install window appears.
yout section
tput Server 2.
elect Software to Install window closes.
X Installer window, click CONTINUE.
X System Administrator Guide.
on of Output Server 2:
tup.exe file and select Run as administrator.
ia Cache Configuration dialog appears.
TX Channel Config dialog for TXPlay2 appears.
page 21.
11
Installing Output Server 2 on a New System
Creating and Sharing a Media Cache Folder
10 Apply any additional configuration that is required for your channel. See Output Server
2 Channel Configuration on page 29 for more information.
Creating and Sharing a Media Cache Folder
As part of the installation of Output Server 2, you are required to create a folder on your
playout server to use as the caching location for media as it transitions from your media
store to playout.
To configure the Media Cache for your playout server:
1 During the installation of Output Server 2, the M
appears.
edia Cache Configuration dialog
2 By default, the Cache Name field will be populated with the playout server’s Windows
Computer Name followed by the suffix
-CACHE.
You may enter a name of your choice, but you must ensure the name does not match
an
y channel names in your iTX system. The name must also include the
-CACHE suffix.
3Click Create CACHE Share. The Create Share dialog appears.
4Click the Browse button . The Browse For Folder dialog appears.
5 Select a location to create the caching folder (e.g.
6Click M
ake New Folder and enter the name Cache.
Computer > C:).
7Click OK.
The B
rowse For Folder dialog closes and you are returned to the Create Share dialog.
8Click Sh
are This Folder as ‘CACHE’.
9Click the Close button . The Create Share dialog disappears, retaining your
selection and you are returned to the M
10 Click SA
VE to confirm your media cache configuration.
edia Cache Configuration dialog.
The installation continues.
12
iTX Output Server 2
Channel Configuration Guide
11 After creating a media cache folder, the iTX Channel Config dialog for TXPlay2 appears.
At this point you should add any channels that you require on this playout server.
See
Adding Channels to an ITX Playout Server on page 21.
12 Complete the installation of any other iTX modules you have selected, as described in
the iTX System Administrator Guide.
13 Apply any additional configuration that is required for your channel. See Output Server
2 Channel Configuration on page 29 for more information.
14
13
Installing Output Server 2 on a New System
Creating and Sharing a Media Cache Folder
14
Upgrading to Output Server 2
If you are upgrading from an Output Server 1 system to Output Server 2, there are
additional precautions and procedures to take into consideration compared to a new
installation. This includes how best to transition from one system to the other and how to
operate with a mix of video engines during the transition.
During the transition from Output Server 1 to Output Server 2, it will be necessary to
temporarily operate with some channels on Output Server 2 and some still on Output
Server 1. This is known as a mixed Output Server system.
Below are some guidelines for operating a mixed Output Server system during this
transition.
• Output Server 2 does not support playout servers with dual SDI I/O cards (i.e. two
Corvid L/P cards). If your playout server is equipped with dual SDI I/O cards, only the
card that Windows identifies as device 0 will be used and only in single channel mode.
• You cannot run Output Server 1 and Output Server 2 on the same playout server. This
because each service requires different AJA SDI I/O card drivers.
• During the transition, it is recommended that an Output Server 2 playout server is
setup as the backup to an Output Server 1 playout server, rather than the other way
around.
• Main/backup setup for a mixed Output Server system is configured in the same way as
a standard main/backup setup.
See About Channel and Live Event Routing on page 46.
Transitioning to Output Server 2
The steps below provide a high level overview of the process for transitioning from Output
Server 1 to Output Server 2.
To transition to Output Server 2:
1 Make sure main channel (legacy master) is routed to air
2 Decommission the backup channel (legacy slave).
3 As near as possible, there must be parity between the configuration of the Output
Server 1 and Output Server 2 playout servers. Apply any configuration changes to the
15
Upgrading to Output Server 2
Operating a Mixed Output Server System
Output Server 1 master that are required to bring it into line with the Output Server 2
backup (e.g. configuring enhanced SCTE 104).
See Operating a Mixed Output Server System, on page 16.
4 Upgrade the backup channel to Output Server 2 and perform the required
configuration.
See Upgrading to the Output Server 2 Service on page 17.
5Start Server Controller on the Output Server 2 backup and confirm the following
configuration:
• On the instance of I/O Device Controller for the channel, check the Reference input
is correct.
See Setting a Reference, Frame Rate Family and Output Timing on page 29.
• On the instance of Output Server 2 for the channel, check the Resolution is correct.
• Apply any other configuration, as required. Backup channels should mirror the
configuration of their main, although when running a mixed Output Server system
some differences in configuration may be required.
See Operating a Mixed Output Server System, on page 16 for differences in
configuration.
See Output Server 2 Channel Configuration on page 29 for more information on
channel configuration.
6 Run the Output Server 1 and Output Server 2 channels in parallel until you are satisfied
with the stability of the system.
7 When you are ready to upgrade the main channel to Output Server 2, route the Output
Server 2 backup to air.
8 Failover the Output Server 1 main, so the channel plays out from the Output Server 2
backup.
9 Upgrade the main channel to Output Server 2 and perform the required configuration.
10 Route new main channel to air.
11 Failover the backup, so the channel plays out from the new main (Output Server 2)
playout server.
Operating a Mixed Output Server System
When running a mixed Output Server system, consider the following differences in
behavior between the two video engines:
FeatureComment
Internal captions Output Server 2 has improved rendering for internal captions. As
such you may see some differences in captions between the two
video engines. For example, outlines and drop shadows are clearer
on Output Server 2.
Cue and commit timingsThe timing for cueing and committing events was redesigned for
Output Server 2 and it does not mirror Output Server 1.
The differences are visible on the schedule grid when viewing an
Output Server 1 main and Output Server 2 backup side by side.
These differences do not affect when items are played out to air.
16
iTX Output Server 2
Channel Configuration Guide
FeatureComment
Playout timingOutput Server 2’s playout is frame accurate, which means a
scheduled item may playout earlier on the Output Server 2 backup
channel compared to the Output Server 1 main, but the difference
should be marginal.
Live pass-through delayThe live pass-through delay was redesigned for Output Server 2
and is different to Output Server 1. It may be possible to
synchronize the live pass-through for an Output Server 1 main and
an Output Server 2 backup by altering the delay on both channels.
For information on changing the output buffer and time delay on
Output Server 1, see the iTX System Administration Guide.
For information on changing the Channel Delay on Output Server
2, see
Configuring Channel Delay, on page 34.
Audio output typesOn Output Server 2, the PCM (Auto) audio output type will assign
16 channels to the track, even if not all of the channels are
required. Any unused channels will be automatically set to mute.
See About Audio Output for Output Server 2 on page 49 for more
information.
SCTE 104 Output Server 2 only supports enhanced SCTE 104. Therefore, the
Output Server 1 main will also need to be configured to use
enhanced SCTE 104.
For more information on enhanced SCTE 104 configuration for
Output Server 1, see the iTX System Administration Guide.
For more information on SCTE 104 configuration for Output Server
2, see
See Configuring a Channel to Process SCTE104 Messages on
page 38.
NTSC SD field order
Output Server 1 and Output Server 2 handle the field order for
NTSC SD assets in different ways. Output Server 1 often
required user intervention to reverse the field order on a perasset basis, while Output Server 2 is able to interpret this
information from the media itself. This can cause problems
when trying to playout assets that have been altered on a
mixed Output Server system.
See Honoring NTSC SD Field Orders on page 65 for more
information.
Upgrading to the Output Server 2 Service
Before upgrading a playout server to Output Server 2, Output Server 1 must be uninstalled.
This can be done as part of the upgrade process.
The iTX installer will convert the current channel configuration from Output Server 1 to
Output Server 2. However, the channel name is not migrated as that information is stored in
different locations on each service. To support the I/O Device Controller (which was not
present for Output Server 1), you need to select your required playout type. Therefore,
during the upgrade the iTX Channel Config dialog appears so that these details can be
entered. It is also possible make changes to the channel details, as required.
17
Loading...
+ 52 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.