Grouped Content - PRG MBOX User Manual

Grouped Content

Description
The Mbox application supports the use of "content grouping" in order to allow every server to have content for itself and
all other servers stored on its hard-drive, but to allow each server to play only the content desired for its own output(s).
In this manner, content synchronization can ensure that all show content is on all servers, which allows for one server to
take over for another more easily. When programming, selecting a folder and file will cause content (with the matching
Folder.File index) to be played only from within the group folder having the same number as the server's group number.
To facilitate content grouping, each Mbox server can be given a numerical "Identity" value (between 0 and 255). In the
content database indexing system for Mbox, the content group is a prefixed 8-bit value - i.e. Group.Folder.File, with each
element being a number 0 - 255. This concept essentially extends Mbox's content indexing system to be 24-bit rather
than 16-bit.
If content is not assigned a group number, then it will always be played when the matching folder and file are selected.
Standard rules for file conflicts (repeated Folder.File indices are conflicts) will apply. If content is assigned a group
number, then there may be multiple Folder.File indices with the same values. But since each will have a unique Group
number, there are no conflicts. The playback of content with the matching group index is automatic and no parameter
on the controller (console or Mbox Director) selects the group number value. Users must preset the Identity of each
server in order to dictate which content is played.
Usage
A typical usage for grouped content may be when more than one Mbox server is used as a portion of a multi-server
(widescreen, matrix, etc.) setup with coordinated outputs. Often these setups will make one larger composition with
each server supplying one or more portions of the larger image. The content grouping scheme allows the programmer to
select the same folder and file values for all servers and get the appropriate portion of the larger composition to play on
each server.
Note: Content Grouping does not chop up or distribute content automatically to the relevant server. It merely causes
the server's matching grouped content to play when a Folder.File is selected.
Usage is not limited to multiple servers making up one larger coordinated raster. Grouped content can be used as a tool
for content organization even when disparate content is used on multiple servers.
Example:
Imagine a system with three servers, each having two outputs. This system has six total outputs, and for a wide blend,
each output will display 1/6th of the total image. The user may choose to supply six unique pieces of content, each
being approximately 1/6th of the final image (plus overlap as required).
The user could place all six pieces of content into the same folder and give each piece a unique file number. (e.g.
001.001, 001.002, 001.003 and so on...) When programming the show, the user would have to select six different pieces
of media for playback, two different files on each server.
With content grouping, the user would first designate the Identity number for each server in the system (e.g. 1, 2, and
3). Then the user would create three different content folders (one for each group identity) on each of the three servers,
labeling them uniquely (see below for details) with numbers to match Group 1, Group 2, Group 3, but each having the
same folder index number. Inside each folder the user would place the two content files (1/3th of the final content image)
that match that server's outputs in the overall scheme. Each pair of content files would all be given the same two file
index numbers.
MBOX® USER MANUAL
40