All other brand names, product names or trademarks belong to their respective holders.
Usage Agreement
Please read the following terms and conditions carefully. By using the Xbuilder User
Manual, you agree to the following terms and conditions:
Miranda Technologies Inc. hereby grants permission and license to owners of Xbuilder and
the Xmedia Suite to use their product manuals for their own internal business use. Manuals
for Miranda Technologies Inc. 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 Miranda Technologies Inc.
Miranda Technologies Inc. makes no warranty, either expressed or implied, including but
not limited to any implied warranties of merchantability or fitness for a particular purpose,
regarding these materials and makes such materials available solely on an “As-Is” basis.
In no event shall Miranda Technologies Inc. be liable to anyone for special, collateral,
incidental, or consequential damages in connection with or arising out of purchase or use
of these materials. The sole and exclusive liability to Miranda Technologies Inc., regardless
of the form of action, shall not exceed the purchase price of the materials described herein.
Miranda Technologies Inc. reserves the right to revise and improve its products at any time
and without notice. This publication describes the state of this product at the time of its
publication, and may not reflect the product at all times in the future. Thus, different versions
of a manual may exist for any given 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 notice and does not represent a
commitment on the part of Miranda Technologies Inc.
Government Use
The Software {and Documentation} is provided with RESTRICTED RIGHTS. Use,
duplication or disclosure by the United States Government or any agency, department or
instrumentality thereof is subject to the restrictions set forth in the Commercial Computer
Software -- Restricted Rights clause at FAR 52.227-19 or the Commercial Computer
Software -- Licensing clause at NASA FAR Supplement 1852.227-86.
Printed in Canada
Document Identification
•Title: Xbuilder User Manual
•Part number: M852-0600-480
•Software version: Vertigo Suite v.4.8
•Last revised: June 21, 2012
Document Revision History
After the original release date, this user manual may be updated with edits and then rereleased. The following table tracks the versions of this document.
Publication dateDescription
June 21, 2012Original release of this user manual for Vertigo Suite v.4.8
Xbuilder’s primary role in the Vertigo Suite is to quickly and accurately build multiple
instances of template-based or pre-rendered graphics for playout. Xbuilder is also allows
you to prepare the new graphics for playout by verifying quality, previewing playout and
organizing the graphics into playlists.
While the remaining chapters provide instructions for how to use Xbuilder, the following list
provides a brief overview of Xbuilder’s main functions:
•Create and populate graphics pages from a master template
Templates created in Xstudio lock down a graphics’ layout. With no need to recreate
the graphic’s layout, Xbuilder can use templates to quickly create multiple instances of
the graphics where the content is specific to the broadcast. These new graphics called
pages are saved as individual assets whose layout is linked to the template. See page
3-1 for more information.
•Render templates to a clip file for the purposes of previewing or playout
Xbuilder can render the playout of templates into various video clip formats, so that you can
preview the graphics playout, or use the resulting clip file to playout the pre-rendered
graphic on a video server or Vertigo playout device. See page 4-1
•Perform quality control and media check of pre-rendered graphics files
Xbuilder’s Make List feature (QC workflow) allows you to preview and validate
(approve or reject) the pre-rendered graphics that the After Effects Plug-in and the
Make List file created and ingested into the Xmedia Server.
Once the graphics are approved and published to the device(s), Xbuilder’s Air List feature
(MC workflow) allows you to quickly preview and verify that all of the approved graphics
have actually been published to the correct devices. See page 5-1
•Create sequential playlists to be played out in Xplay
Xbuilder allows you to build playlists, which are ordered sequences of program clips
and branding and promotional graphics elements (i.e. pages, scenes or clips). The
resulting playlists can be edited and played back using the Vertigo Suite’s Xplay. See
page 6-1
•Create rundowns and segments for newsroom applications
Similar to sequential playlists, Xbuilder can create rundowns and segments, which are
ordered lists of the pages, scenes and clips that can be brought into newsroom
applications. See page 7-1
for more information.
for more information.
for more information.
for more information.
Xbuilder User Manual1-1
Introducing Xbuilder
1-2Xbuilder User Manual
2 GETTINGSTARTEDWITH XBUILDER
This chapter provides you with information about installing and licensing the Xbuilder
software on a client workstation. Additional information and instructions are provided for
performing a basic setup and configuration of the Xbuilder software.
Once you have completed the installation and quick setup, Xbuilder will be properly
configured to create and save pages, render graphics to clips and create playlists.
This chapter is organized into the following topics:
Installation and licensing information” on page 2-2
•“
•“Starting Xbuilder and connecting to the Xmedia Server” on page 2-3
•“Overview of Xbuilder’s user interface” on page 2-4
•“Configuring Xbuilder’s settings” on page 2-6
•“Adding and configuring a Preview device” on page 2-7
•“Configuring a device for the verification of playlist elements” on page 2-9
Xbuilder User Manual2-1
Getting started with Xbuilder
Installation and licensing information
Xbuilder is packaged with the Vertigo Suite software installation wizard. It can be installed
as part of the full installation or as an individual (standalone) component. In both cases, you
simply need to run the installation wizard on a workstation that is on the same network as
the Xmedia Server.
Information regarding the Vertigo Suite’s hardware and network requirements, as well as
instructions for installing and/or upgrading Xbuilder, are available in the Vertigo Suite’s
Release Notes, which can be downloaded from the Miranda Technical Support Services
web site.
To operate in its full capacities, Xbuilder requires that four (4) software application licenses
(listed below) be installed and validated on the Xmedia Server. Therefore, once Xbuilder is
installed, you must contact the Miranda Technical Support team (support@miranda.com
to request a license key. Then you must apply and validate the licenses using the
XmediaServer Control Panel. Instructions for acquiring and validating licenses are also
provided in the Vertigo Suite’s Release Notes.
License nameDescription
)
Xbuilder
XGSoftware
XGEncode
XGEncodeforPlayout
QC
The Xbuilder license is required to open and operate the base
features and functionality of the Xbuilder application.
The XG Software license is required to preview graphics using the
VX-Preview (Software CG) application. See page 3-11
information.
The XG Encode license is required to use Xbuilder’s Render to File
feature, which renders and saves the playout of a template, page,
and/or scene to a file in various clip formats. See page 4-1
information.
The XG Encode for Playout license is required to render pages
and/or scenes to playout server compatible formats (XDCAM and
IMX compatible MXF files). See page 4-3
The QC license is required to use Xbuilder’s Quality Control (QC)
workflow (O
preview and validate graphics before they are published to the target
devices and taken to air. See page 5-1
PEN MAKELIST feature). The QC workflow allows you to
for more information.
for more information.
for more
for more
2-2Xbuilder User Manual
Getting started with Xbuilder
Starting Xbuilder and connecting to the Xmedia Server
When you initially launch Xbuilder, a dialog box appears and asks you to configure the
server location. As a client application, Xbuilder must be connected to the Xmedia Server,
which is the centralized asset management server for Vertigo applications and devices.
Since you have only just installed Xbuilder, the first task that you must do is to connect
Xbuilder to the Xmedia Server.
To start Xbuilder and connect to the Xmedia Server:
1.Click S
2.When the message asking you to configure the server location, click the Y
TART>PROGRAMS>VERTIGOXMEDIA>XBUILDER.
ES button.
The SETTINGS dialog box appears.
Figure 2-1. Settings dialog box
3.Click SERVERS in the tree view at left. This displays the settings related to the Xmedia
Server (see page 9-15 for more information about Xbuilder’s Server settings).
4.In the X
MEDIASERVER IP ADDRESS field, replace <server IP> with the IP address of
the machine hosting the Xmedia Server.
5.Unless the port number was changed when the Xmedia Server was installed, the
default in the X
MEDIASERVER PORT field will be correct. If it was changed, enter the new
number.
6.Click OK.
Xbuilder launches. If the program does not launch, consult your system administrator.
The problem could be due to one of the following:
• The IP address or port was entered incorrectly.
• The machine hosting the Xmedia Server is down.
• The Xmedia Server is not running on the host machine.
• The machine is not connected to the network.
Xbuilder User Manual2-3
Getting started with Xbuilder
1
2
3
4
5
6
Overview of Xbuilder’s user interface
Xbuilder provides an interface provides you with the tools and features required for
accomplishing various tasks like creating and populating pages, rendering graphics to a file
or building playlists.
Figure 2-2
features and components. Information and instructions for how to use each interface
component are provided in within the applicable tasks in further chapters.
and the following descriptions provide an overview of Xbuilder’s main interface
1.Main menus - Located along the top of the interface, these menu commands provide
access to most of Xbuilder's settings and administrative functions. See “
Quick reference to Xbuilder’s menus & toolbars” on page 8-1 for more information.
2.The upper portion of the Xbuilder interface changes according to what type of project
you are working on: playlist, segment, rundown or timeline.
• Playlist Editor - The workspace where pages, templates, scenes and clips
can be organized into a sequential playlist. See page 6-2
using the Playlist Editor.
• Segment window - Very similar to the Playlist Editor, the Segment window
allows you to build a portion of a sequential playlist to be used in a rundown.
See page 7-4
for full details on using the Segment window.
Figure 2-2. Xbuilder interface
Appendix A -
for full details on
2-4Xbuilder User Manual
Getting started with Xbuilder
• Rundown Editor - The workspace for creating a sequential rundown playlist
using segments, pages, clips, scenes and template assets. See page 7-6 for
full details on using the Rundown Editor.
• Timeline Editor - The Timeline Editor allows you to create and edit
automated promos by assembling and editing episodic clips, graphics, and
audio elements within a timeline interface.
3.Asset Browser - Located in the lower left-hand portion of the interface, the Asset
Browser provides a tree view of the asset categories on the connected Xmedia Server.
When you select a category or sub-category, the assets stored within the category are
displayed in the panel to the right of the Asset Browser (Template Editor). You can
display or hide the Asset Browser by pressing C
TRL+A, or by selecting Asset Browser
from the View menu.
4.Template Editor - Its main function is to provide a canvas for displaying and editing
the variable fields on a open pages, templates and scenes. Its toolbar buttons provide
access to commands and features tat can be applied to the displayed asset.
A secondary function of this interface panel, is to display the contents of the selected
category from the Asset Browser. The assets from a selected category can be viewed
in proxy or list view mode.
5.Favorites Browser - Located in the lower right-hand portion of the interface, the
Favorites Browser provides a quick drag-and-drop area where frequently used
templates, pages, scenes and clips can be stored for easy access.
6.Status bar - Located along the bottom of the Xbuilder window, the status bar provides
process update messages (left), server connection identification (center), and preview
device connection status (right).
Xbuilder User Manual2-5
Getting started with Xbuilder
Configuring Xbuilder’s settings
Although Xbuilder’s default settings are appropriate for most operating circumstances, you
may want to customize the look and behavior of the application using Xbuilder’s settings.
Note that modifying these settings is entirely optional.
Changes to Xbuilder settings are made within the S
accessed by selecting TOOLS>SETTINGS from the Xbuilder menu commands.
This SETTINGS dialog box contains a tree-structure of thematic settings. Each of the settings
is defined in the following sections:
General settings” on page 9-2
• “
• “Display settings” on page 9-4
• “Template Favorites settings” on page 9-6
• “Automation settings” on page 9-7
• “Playlist Ingest settings” on page 9-8
• “Place Holders settings” on page 9-9
• “Merge List settings” on page 9-10
• “Logging settings” on page 9-11
• “Render To File settings” on page 9-12
• “Timelines settings” on page 9-13
• “Work Orders settings” on page 9-14
• “Servers settings” on page 9-15
• “Playlist > Basic settings” on page 9-16
• “Playlist > Highlight settings” on page 9-17
ETTINGS dialog box, which can be
2-6Xbuilder User Manual
Adding and configuring a Preview device
NOTE
In order to use Xbuilder’s features for previewing the playout (page 3-11) and/or render a
page/scene to file (page 4-1
these tasks. In most cases, a Vertigo Software CG device is used for previewing and
rendering to file in Xbuilder.
The XGSOFTWARElicense is required to fully use the preview feature.
To add and connect Xbuilder to a Preview device:
1.Open the Device Configuration window by selecting T
2.In the D
EVICE CONFIGURATION window, select the ADD button:
), you must specify which device Xbuilder will use to perform
OOLS>DEVICE MANAGER.
Figure 2-3. Device Configuration dialog box
Getting started with Xbuilder
3.The D
Xbuilder User Manual2-7
EVICE CONFIGURATION windows expands to reveal two tabs (GENERAL and ADVANCED)
with settings for identifying the device’s configuration.
Figure 2-4. Add Device Configuration section
Getting started with Xbuilder
4.Specify the appropriate General Device Configuration settings:
Device nameThe name of the selected device. This can only be modified when
Device aliasAn alternative name for the selected device on your network.
DescriptionAn optional field that lets you label the device to distinguish it from other
Device TypeIdentifies the type of device that these settings apply to. Select
Control IPThe network location (IP address) or hostname of the selected device.
Control PortThe networking port that serves as a channel for sending commands to
Publish IPThe network location (IP address) or hostname of the selected device.
Publish PortThe networking port that serves as a channel for publishing assets.
adding a device.
similar devices at your facility (for example).
REVIEW (or other device) for Software CG devices.
P
The host must be available on the network.
and from the device.
The host must be available on the network.
Typically, this value is set to 15000.
N
OTE: This value must correspond with the port used by the
XpublishAgent on the output device.
5.Click A
6.In the D
PPLY.
EVICE CONFIGURATION dialog box, click in the cell to the right of Preview.
7.Select the device from the table at left and then click .
The device now appears next to the P
REVIEW box at right.
8.Click CLOSE.
When Xbuilder successfully connects to the preview device, the LED in the lower right
corner of the Xbuilder window is green and when disconnected, it is red.
2-8Xbuilder User Manual
Getting started with Xbuilder
Configuring a device for the verification of playlist
elements
Xbuilder can be configured to manually or automatically verify the elements of a playlist
have been published to specified devices. Elements that have not been published are
identified and highlighted in the playlist so that they can be published. For this verification
step to be accomplished, the target devices that will be checked must first be assigned in
the Device Manager.
To specify a device for the verification of playlist elements:
1.Open the Device Manager by selecting T
EVICE CONFIGURATION dialog box appears.
The D
Figure 2-5. Device Configuration dialog box
OOLS>DEVICE MANAGER.
2.Verify that the intended output device is listed in the D
If it is not, then you must add it to the device list.
a.In the D
b.The D
ADVANCED) with settings for identifying the device’s configuration.
c.Specify the appropriate General Device Configuration settings:
Device nameThe name of the selected device. This can only be modified when adding a device.
Device aliasAn alternative name for the selected device on your network.
DescriptionAn optional field that lets you label the device to distinguish it from other similar
Device TypeIdentifies the type of device that these settings apply to. Choose from the following:
Control IPThe network location (IP address) or hostname of the selected device. The host
Control PortThe networking port that serves as a channel for sending commands to and from the
Xbuilder User Manual2-9
EVICE CONFIGURATION window, select the ADD button.
EVICE CONFIGURATION windows expands to reveal two tabs (GENERAL and
Publish IPThe network location (IP address) or hostname of the selected device. The host
must be available on the network.
Publish PortThe networking port that serves as a channel for publishing assets. Typically, this
value is set to 15000.
NOTE: This value must correspond with the port used by the XpublishAgent on the
output device.
d.Specify the appropriate Advanced Device Configuration settings:
Clip TemplateThe name of the template that is used to play out clips. The clip template’s control-
side must have a texture linked to a scene-side clip object. Use the button to
navigate to the Clip template.
Note that among the Vertigo Suite’s system templates are valid clip templates for
various scene formats. The system templates are export files that are stored in the
following directory: Program Files\VertigoXmedia\Apps\Support. Once
imported into the Xmedia Server, the templates are stored in the
EMPLATES>SYSTEM TEMPLATES category.
T
The Clip Template field only appears when one of the following device types is
selected: Vertigo XG, Intuition XG, Preview (and other devices), or Other.
Cel TemplateThe name of the template used to play out cel animations. The cel template’s
control-side must have a texture linked to a scene-side clip object. Use the button
to navigate to the Cel template.
Note that among the Vertigo Suite’s system templates are valid Cel templates for
various scene formats. The system templates are export files that are usually stored
in the following directory: Program Files\VertigoXmedia\Apps\Support.
Once imported into the Xmedia Server, the templates are stored in the
TEMPLATES>SYSTEM TEMPLATES category.
The Cel Template field only appears if one of the following device types is selected:
Vertigo XG, Intuition XG, Preview (and other devices), or Other.
Image TemplateThe name of the template used to play out images. The image template’s control-
side must have a texture linked to a scene-side clip object. Use the button to
navigate to the Image template.
Note that among the Vertigo Suite’s system templates are valid image templates for
various scene formats. The system templates are export files that are usually stored
in the following directory: Program Files\VertigoXmedia\Apps\Support.
Once imported into the Xmedia Server, the templates are stored in the
EMPLATES>SYSTEM TEMPLATES category.
T
The Image Template field only appears if one of the following device types is
selected: Vertigo XG, Intuition XG, Preview (and other devices), or Other.
2-10Xbuilder User Manual
Getting started with Xbuilder
External KeyerAllows you to associate another device with the current device. This setting is
specifically used when the CG output is keyed over the ImageStore output. In this
way, specific commands can be sent to the ImageStore (the External keyer) when
specific things are done on the CG.
Publish MasterLets you select a master device.
e.Click APPLY.
The device is added to the Device list in the Device Configuration dialog box.
3.In the D
EVICE CONFIGURATION dialog box, select the text box to the right of DEVICE1.
4.Select the device name from the table and click .
The device appears in the box on the right side with its name in the D
5.Click C
LOSE on the Device Configuration dialog box.
6.Restart Xbuilder and ensure that the device was added to the D
down list in the upper-right corner of Xbuilder’s Playlist Editor toolbar.
EVICE1 field.
EVICEFOR VERIFY drop-
Xbuilder User Manual2-11
Getting started with Xbuilder
2-12Xbuilder User Manual
3 CREATING, EDITINGANDPREVIEWING
PAGESAND/ORSCENES
In the Vertigo Suite workflow, Xstudio is used to author scenes, which display graphical
elements (i.e. text, images, video clips, and cel animations) on air. Scenes can be
standalone or they can be associated with a template. A template is an interface that lets
operators control and edit parts of the scene without disturbing the scene’s layout or
formatting.
The benefit of using template-based graphics is that once you have created a scene and
template in Xstudio, rather than recreating the control and layout for similar projects, you
can use the template and scene in Xbuilder to create multiple instances of the graphics
(called pages) by simply changing the content (i.e. enter the new text, images, clips, and/or
animations specific to the broadcast). Also note that no matter how many times the page is
edited, the page retains its ties to the template that it was created from. The advantage of
this is that changes to the template are easily propagated to all of the pages that were built
from using that template.
Figure 3-1. Workflow for populating templates and creating pages
There are actually two types of pages that can be created using Xbuilder: shared or embedded.
Both types of pages provide the same playout performance in a playlist. The main consideration
that should be taken into account is whether the page is intended to be included in only one or
many playlists.
Xbuilder User Manual3-1
Creating, editing and previewing pages and/or scenes
•Shared pages are the preferred type of page as they are created directly from an
existing template and they are saved to the Xmedia Server as distinct assets. Shared
pages can be used in many different playlists as a common item.
•Embedded pages are most often created from another existing page. Unlike shared
pages, embedded pages only exist within a playlist, and it is the playlist that is saved
as a whole to the Xmedia Server. As a result, the individual page does not exist
anywhere else, not even in the P
AGES root category of the Asset Browser. Embedded
page can be reused outside of its playlist if its playlist is inserted or appended to
another playlist, or if the page converted into a shared page using the SAVEAS SHARED
PAGE command. See page 6-7 for instructions on creating and adding embedded
pages to a playlist.
The following sections provide instructions for using Xbuilder to create and populate
graphics pages and scenes, either individually from a template/scene or as a batch using a
Merge List file:
Creating an individual shared page from a template” on page 3-3
•“
•“Creating pages and/or scene using a Merge List” on page 3-4
3-2Xbuilder User Manual
Creating, editing and previewing pages and/or scenes
Creating an individual shared page from a template
Shared pages are graphics created as an instance of an existing template. They are stored
on the Xmedia Server as an distinct assets and can be used in many different playlists as
a common item. Like all pages, the shared page’s formatting is linked to the original
template (changes to the template’s formatting are automatically applied to the page). The
following instructions describe how to create an individual shared page.
To create a new shared page from a template:
1.Open Xbuilder.
2.In the Asset Browser, navigate through the T
desired template listed in the Template Editor.
3.Double-click the template, or right-click on the template listed in the Template Editor
and select the O
PEN command from the context menu.
The template opens in the Template Editor.
4.Set or edit the variable fields in the template as required (see “
content elements” on page 3-10 for assistance).
5.Select the F
ILE>SAVEASA SHARED PAGE command.
The SAVE PAGE dialog box appears (figure 3-2).
EMPLATES root directory until you see the
Editing a page or scene’s
Figure 3-2. The Save As Shared Page command opens the Save Page dialog box
6.In the N
7.In the R
AME field enter a new name for the page.
ECALLID field enter a unique a unique alpha-numeric identifier that can be used
in Vertigo Suite applications (i.e. Xbuilder, Xplay) to quickly call up the specific page.
(optional)
8.Enter your name in the A
9.Enter a short description of the page in the D
UTHOR field (optional).
ESCRIPTION field (optional).
10. Link the page to the Pages root category or to sub-categories by selecting the check
box for each place where you want the page to be accessible from.
11. Click OK to save the page and exit the dialog box.
Xbuilder User Manual3-3
Creating, editing and previewing pages and/or scenes
Creating pages and/or scene using a Merge List
Xbuilder’s Merge List feature (ACTIONS>OPEN MERGE LIST) allows you to create multiple
pages and/or scenes from a single Merge List file (spreadsheet or XML file). Acting as the
data source, the Merge List file provides Xbuilder with the information it needs to create new
instances of pages/scenes from existing template and scene assets.
The following table describes the Merge List workflow for creating new pages and/or scenes:
StepTask Description
1Configure Xbuilder’s Merge List settings
Specify the default categories in which new pages and scenes will be stored. Since scenes will
only be moved to the default category after they have been approved, you must also specify a
temporary category for new scenes.
1. Open Xbuilder and select T
2. For each of the settings, select the button and select a destination category.
Merge List settings” on page 9-10 for more information.
See “
2Create the templates and scenes in Xstudio
In Xstudio, create or verify the existence of the templates and scenes that you want to create
the new pages and scene from.
3Create the Merge List file
Xbuilder generates the new pages and/or scenes based on the data provided in the Merge List
file. The Merge List file can be in XML format or an Excel spreadsheet. The following sections
provide instructions for creating an appropriate Merge List file:
Creating Merge List file in Microsoft Excel” on page 3-5
•“
•“Creating an XML Merge List file” on page 3-6
OOLS>SETTINGS>MERGE LIST.
4Load the Merge List file in Xbuilder
When a Merge List file is loaded, Xbuilder generates the new pages and/or scenes based on
the data provided in the Merge List file. After being processed, the new pages and/or scenes are
added to a playlist in Xbuilder’s Playlist Editor.
1. Open Xbuilder and select A
2. Use the O
5Approve or reject the new pages and/or scenes
When new pages are generated by the Merge List, they are added to the playlist as embedded
pages until they have been “approved”. Approved pages become assets (shared pages) and
they are saved in the specified default render path. Rejected pages remain in the playlist as
embedded pages.
When new scenes are generated by the Merge List, they are first placed in the specified
temporary scenes category. Scenes are only moved to their specified render path location after
they have been approved. Rejected scenes remain in the temporary scene folder.
See page 3-8
3-4Xbuilder User Manual
PEN MERGE LIST FILE window to navigate to and open the Merge List file.
for instructions on how to approve or reject new pages and scenes.
CTIONS>OPEN MERGE LIST.
Creating, editing and previewing pages and/or scenes
StepTask Description
6With the new pages/scenes, you can perform the following tasks:
•Preview the new pages/scenes on a software CG (see page 3-11
•Render all or an individual page/scene to a clip file (see page 4-1
•Create and save a snapshot image of a new page or scene (see page 3-12).
•Perform edits to the content of new pages/scenes (see page 3-10
Creating Merge List file in Microsoft Excel
The Merge List file can be in the form of a Microsoft Excel spreadsheet (.xls only), which
contains specific column headers that allows Xbuilder to create new pages and/or scenes
from existing assets (templates/scenes), apply specific attributes, and/or populate the
asset’s fields.
Figure 3-3. Merge List spreadsheet
).
).
).
Figure 3-3
first row in the Merge List spreadsheet contains the mandatory column headers for the data
the Xbuilder needs to create the new pages and/or scenes.
The following list identifies and describes the columns and information are mandatory or
commonly used in a Merge List spreadsheet:
•PageName: The path and asset name of the template that the new page will be created
•OutputName: The path and asset name given to the new page or scene. The
•RecallId: An alpha-numeric identifier given to the new page or scene. (Optional)
•ExpiryDate: The date when the new page or scene is to be deleted from the repository.
•PublishLifespan: The number of days that must elapse since the last time the new
•RenderProfile: The name of the render profile to use when the user wants to render the
•RenderPath: The folder where the user wishes the rendered file will be saved.
provides and example of a Merge List spreadsheet and demonstrates that the
from or the scene from which the new scene will be based.
outputName specified can be fully qualified. If it is not fully qualified the new page will
be saved to a default path specified in the settings. If no default path is specified will
then save to the asset root category.
The format is yyyy-mm-dd. (Optional)
page or scene has been accessed before it is removed from the published device. This
does not remove it from the repository. (Optional)
page to file. The name of the render profile is defined inside of the render profile xml.
Xbuilder User Manual3-5
Creating, editing and previewing pages and/or scenes
NOTE
•Duration: The duration of the page in dropframe timecode. This will be the duration of
the file generated.
•<objectName>: Column 9 (I) and beyond are the name of a target control side object.
The target object can be a text, textbox, image, clip, or cel animation object.
The value for the image, clip, or cel animation override can be a fully qualified asset
name. If the asset name is not fully qualified the asset will be searched for by the
existing object's type. The asset from the first category in which it was found will be
used. If the asset is not fully qualified and there is no existing object in the originating
template then the asset cannot be found.
The object type is not defined in the object name to allow the reuse of the object names
across types. This reduces the number of columns in the spreadsheet.
Be mindful of the following conditions and behaviors when creating or using the Merge List
spreadsheet file:
•Do not enter blank rows between the data as blank rows are interpreted as the end of file.
•If the name and category specified for the new page or scene matches an existing
page/scene and the Merge List is being processed, you will be prompted as to whether
you want to replace it.
•If the specified recalI Id is already being used elsewhere, the new page or scene will
steal the recalI Id.
•The items specified in the Merge List will be converted into embedded pages in a playlist.
Once approved, the embedded pages from the playlist will then be saved as shared pages.
Creating an XML Merge List file
The Merge List file can be in the form of a XML file, which contains specific attributes (tags)
allowing Xbuilder to create new pages and/or scenes from existing assets (templates/scenes),
apply specific attributes, and/or populate the asset’s fields.
The following example and the list below identifies and describes the attributes (XML tags) that
are mandatory or commonly used in a Merge List to create new instance of pages and/or scenes: