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

1-2 Vertigo XG & iTX Integration User Guide
Integration of Vertigo XG & iTX
Overview of the XG Inside workflow
Figure 1-1 shows how iTX and the XG Inside components work together on an Output
Server machine.
Figure 1-1. XG Inside signal path and workflow
Graphics preparation
Vertigo templates are created offline using the Vertigo Suite’s Xstudio application. The
templates provide the layout, formatting and optional logic for controlling the graphics
during playout. An advantage of using graphics templates is that unique instances of the
graphics can be quickly created by changing the content elements, without having to
recreate the layout and formatting. See the Xstudio User Manual for more information
about using Xstudio to create Vertigo templates.
Once a template is created, it is saved to a Vertigo Xmedia Server. From there, the template
and its associated graphics files are published to the Embedded Xmedia Server (EXMS) on
the iTX Playout Server, where they become available for playout. The Xpublish Agent puts
the graphics files in the Scene folder.
The VertigoXG plugin associated with the iTX Desktop allows users to browse the
templates and pages stored on the Xmedia Server. Opening the template in the plugin
allows users to edit the content of the template and save it as a graphics page on the
Xmedia Server. The Xmedia Server then publishes the page and its associated graphics
files to the Embedded Xmedia Server (EXMS) on the iTX Playout Server.
In addition to templates and pages, the VertigoXG plugin associated with the iTX Desktop
also allows users to browse for standalone scenes stored on the Xmedia Server. Like the
scene-side of a template, scenes contain the collection of graphic objects that will be
displayed on air during playout. Standalone scenes are appropriate if the scene’s objects
and playout do not require any control logic (static and/or timed playout). However, if the