Grass Valley Vertigo XG Integration v.2.3 - Manual (Page 7)

Vertigo XG & iTX Integration User Guide 1-3
Integration of Vertigo XG & iTX
scene’s objects are to be data driven or controlled during playout, the scene should be
associated with a template. See the Xstudio User Manual for more information about using
Xstudio to create standalone scene assets.
Processing and playout of video & graphics
Using the Vertigo XG plugin in the iTX Desktop, the graphics page and scenes can then be
added to the channel’s schedule or timeline as a secondary event.
TXPlay controls schedule playout. It sends commands through the Output Server to the
iTX Player (Pandora) to play out events at specified times. An event can feature one or two
video sources, from which iTX produces an SDI or HD SDI output signal.
When an event includes a Vertigo page or scene, the iTX Player feeds the video streams
to the XG Renderer. It always supplies two streams; if there is only one video source, one
of the streams has blank frames.
Using the Oxtel protocol, TXPlay instructs Vertigo Xplay to cue and take the page or scene.
Xplay processes the page/scene requirements and sends playout commands to the
XG Renderer.
The XG Renderer loads the page or scene and its associated graphics. The XG Renderer
and the GPU renders the graphics with the video streams and passes a single rendered
video stream back to the iTX Player, which combines this with the audio stream(s) for
playout through the AJA video card.
The iTX Player does not pass any audio content to the XG Renderer. It de-embeds the audio
content from the video streams, diverts it around the XG Renderer and then re-embeds it into
the rendered video stream (after a delay to compensate for the render process).
For events that do not feature a Vertigo page or scene (XG Event), the video streams simply
pass through the XG Renderer (figure
1-2 ).
Figure 1-2. For all other event types, the video streams pass through the XG Renderer