Grass Valley Vertigo XG Integration v.2.6 - Manual (Page 8)

4
Integration of Vertigo XG and iTX
Overview of the downstream Vertigo XG workflow
• Cel animations are only supported if they are in the Grass Valley VAF format.
Uncompressed TGA sequences are likely to have an adverse affect on the performance
of the Output Server.
• The XG Renderer plays out audio clips embedded in a Vertigo XG template; but it does
not perform any audio mixing with content from the iTX Player, since this contains no
audio stream. This means that Vertigo templates cannot modify the audio properties
(e.g. volume levels) of the clips played out by iTX.
• Audio-level reduction (ducking) and sound effects cannot be controlled from the
XG Renderer.
• The XG Renderer does not modify any AFD code in the video streams.
• The XG Renderer does not include caption or subtitle data in the video stream it returns
to the iTX Player.
• The XG Renderer cannot pass SNMP data to the iTX system.
• Where there is only one video stream and the source is a live feed, only transitions that
do not involve overlapping video streams are possible (e.g. cut-cut; fade out, followed
by fade in).
• Since the XG Renderer is responsible for the compositing of PGM A and PGM B video,
traditional iTX functionality for squeeze-backs and picture-in-picture (PIP) effects do
not work.
Overview of the downstream Vertigo XG workflow
Figure 1-3 demonstrates that in a downstream branding model, the iTX Playout Server acts
as an upstream video server, feeding video and audio content to the external Vertigo XG
device. Meanwhile, graphics content is created and managed using the Vertigo Suite’s
Xstudio and the Xmedia Server. iTX is the automation system that drives the playout
schedule, including controlling the playout of graphics events from the Vertigo XG using
Oxtel automation protocol commands.
Fig. 1-3: System diagram of an external Vertigo XG device downstream of an iTX system