Grass Valley Xnews Vertigo Suite v.5.0 - Manual (Page 72)

Xnews User Manual 4-5
Preparing to use Xnews
Choosing between embedded, shared or private pages
Before using Xnews to create graphics pages for broadcast, we recommend that you
determine whether you want to create embedded pages, shared pages or private pages. All
three types of pages provide the same playout performance in a rundown. The main
considerations that should be taken into account is whether the page is intended to be
included in only one or many stories and whether the page asset is required to be stored
and managed on the Xmedia Server.
Embedded pages exist only within a story, and it is the rundown that is saved as a whole
in the Xmedia Server. As a result, the individual page does not exist anywhere else, not
even in the Pages root category of the Asset Browser. An advantage of using embedded
pages is cleanup - once the rundown is deleted, all the pages in it are gone too. Therefore,
the Xmedia Server does not accumulate large quantities of unused/unwanted assets. The
use of embedded pages is commonly preferred in newsroom environments since pages are
usually created for a specific story or rundown and then they are no longer needed. By
default, Xnews is configured to run in E
MBEDDED P AGES MODE (see “Enabling Embedded
Pages or Shared Pages mode” on page 2-6 ).
Shared pages exist in the Xmedia Server (accessed from the Asset Browser) as distinct
assets and can be used in many different stories as a common item. The benefit of using
shared pages is that only one “copy” of that page needs to be updated for the updates to
apply to all of the stories that include that page. The drawback of using shared pages is that
deleting the shared page asset from the Xmedia Server affects all stories that use that page.
By default, Xnews is configured to run in E
MBEDDED P AGES MODE , which only allows you to
create embedded pages.To create shared pages in Xnews, you must disable the
EnableEmbeddedPages
setting in the xnews.ini file (see “Enabling Embedded Pages
or Shared Pages mode” on page 2-6 ).
Private pages are exclusively meant to replace the use of embedded pages for MOS
workflows in ENPS. In this particular application, embedded pages were previously used
which sometimes resulted in ENPS performance issues. The strategic characteristics of
private pages remedies these issues.
Private pages can only be created in Xnews and like shared pages, they exist as distinct
assets, however unlike shared pages they are not visible from the Asset Browser.
Since private pages exist only in the Xmedia Server, their lifetime must be managed by the
Xmedia Server. When a private page is no longer needed, it must be removed from the
Xmedia Server. The U
NREFERENCED P RIVATE P AGE E XPIRY setting determines how long a
Private page is kept in the Xmedia Server after it has been deleted, floated, archived or its
rundown has been made MOS Control Inactive.
Private page names must be valid Xmedia Server asset names and are limited to any
alphanumeric character, space, hyphen and underscore characters. Private pages do not
support recall IDs, so giving a private page a uniquely numeric name does not support the
usual recall id functionality.
To create Private pages, you must enable the EnablePrivatePages setting in the
xnews.ini
file (see “Enabling Privates Pages mode” on page 2-7 ).