Viz Mosart Administrator Guide
Version 5.1 | Published January 19, 2023 ©
MOS Object with Clip Templates Merged in a Mosart Template
A single MOS object is created for all Mosart templates of type PACKAGE or VOICEOVER from the default template set. In this example:
-
<mosExternalMetadata> node contains the list of variants for the Mosart templates of type PACKAGE and VOICEOVER.
-
<objID> of the MOS object is set to 25, representing a Mosart item type CLIP.
-
<objGroup> is the default template set name.
-
<type> node has name and category set to “CLIP”, and templateset set to the name of the default template set.
-
The variant for each template is built using some prefixes:
1) for PACKAGE, the variant is set to MAZ-<template variant>
2) for VOICEOVER, the variant is set to OFFMAZ-<template variant>
Note: When GroupByType is false, no MOS object will be sent for templates of type PACKAGE and VOICEOVER.
<
mosObj
>
<
objID
>LOWERTHIRDS</
objID
>
<
objSlug
>LOWERTHIRDS</
objSlug
>
<
mosAbstract
/>
<
objGroup
>TEMPLATES</
objGroup
>
<
objType
>STILL</
objType
>
<
objTB
>50</
objTB
>
<
objRev
>1</
objRev
>
<
objDur
>0</
objDur
>
<!-- The status of the MOS object can be NEW, UPDATED or DELETED -->
<
status
>NEW</
status
>
<
objAir
>NOT READY</
objAir
>
<
createdBy
/>
<
created
/>
<
changedBy
/>
<
changed
/>
<
description
/>
<
mosExternalMetadata
>
<
mosScope
>PLAYLIST</
mosScope
>
<
mosSchema
>
http://www.mosartmedialab.no/schema/mositem.dtd
</
mosSchema
>
<
mosPayload
>
<
mosarttemplate
>
<
type
name
=
"LOWERTHIRDS"
category
=
"GRAPHICS"
>
<
variants
fieldtype
=
"LIST"
value
=
"AUTOOUT"
>
<
variant
name
=
"AUTOOUT"
>
<
fields
>
<
field
name
=
"graphics_description"
fieldtype
=
"TEXT"
/>
<
field
name
=
"graphics_id"
fieldtype
=
"TEXT"
/>
<
field
name
=
"tc_in"
fieldtype
=
"TIMECODE"
inputmask
=
"mm:ss"
default
=
"00:00"
/>
<
field
name
=
"tc_out"
fieldtype
=
"TIMECODE"
inputmask
=
"mm:ss"
default
=
"00:00"
/>
<
field
name
=
"channel"
value
=
"DSK"
fieldtype
=
"LIST"
keylist
=
"channels"
/>
<
field
name
=
"take"
value
=
"AUTO"
fieldtype
=
"LIST"
keylist
=
"taketypes"
/>
</
fields
>
</
variant
>
<
variant
name
=
"KEEPWHILEBACKGROUND"
>
<
fields
>
<
field
name
=
"graphics_description"
fieldtype
=
"TEXT"
/>
<
field
name
=
"graphics_id"
fieldtype
=
"TEXT"
/>
<
field
name
=
"tc_in"
fieldtype
=
"TIMECODE"
inputmask
=
"mm:ss"
default
=
"00:00"
/>
<
field
name
=
"tc_out"
fieldtype
=
"TIMECODE"
inputmask
=
"mm:ss"
default
=
"00:00"
/>
<
field
name
=
"channel"
value
=
"DSK"
fieldtype
=
"LIST"
keylist
=
"channels"
/>
<
field
name
=
"take"
value
=
"AUTO"
fieldtype
=
"LIST"
keylist
=
"taketypes"
/>
</
fields
>
</
variant
>
<
variant
name
=
"KEEPWHILESTORY"
>
<
fields
>
<
field
name
=
"graphics_description"
fieldtype
=
"TEXT"
/>
<
field
name
=
"graphics_id"
fieldtype
=
"TEXT"
/>
<
field
name
=
"tc_in"
fieldtype
=
"TIMECODE"
inputmask
=
"mm:ss"
default
=
"00:00"
/>
<
field
name
=
"tc_out"
fieldtype
=
"TIMECODE"
inputmask
=
"mm:ss"
default
=
"00:00"
/>
<
field
name
=
"channel"
value
=
"DSK"
fieldtype
=
"LIST"
keylist
=
"channels"
/>
<
field
name
=
"take"
value
=
"AUTO"
fieldtype
=
"LIST"
keylist
=
"taketypes"
/>
</
fields
>
</
variant
>
<
variant
name
=
"NONEAUTOOUT"
>
<
fields
>
<
field
name
=
"graphics_description"
fieldtype
=
"TEXT"
/>
<
field
name
=
"graphics_id"
fieldtype
=
"TEXT"
/>
<
field
name
=
"tc_in"
fieldtype
=
"TIMECODE"
inputmask
=
"mm:ss"
default
=
"00:00"
/>
<
field
name
=
"tc_out"
fieldtype
=
"TIMECODE"
inputmask
=
"mm:ss"
default
=
"00:00"
/>
<
field
name
=
"channel"
value
=
"DSK"
fieldtype
=
"LIST"
keylist
=
"channels"
/>
<
field
name
=
"take"
value
=
"AUTO"
fieldtype
=
"LIST"
keylist
=
"taketypes"
/>
</
fields
>
</
variant
>
</
variants
>
<!-- List of active channels (graphics destinations) as configured in OverlayGraphics Interface-->
<
keys
name
=
"channels"
>
<
k
>WALL_2</
k
>
<
k
>WALL</
k
>
<
k
>TABLE</
k
>
<
k
>DSK</
k
>
</
keys
>
<
keys
name
=
"taketypes"
>
<
k
>AUTO</
k
>
<
k
>MANUAL</
k
>
</
keys
>
</
type
>
</
mosarttemplate
>
</
mosPayload
>
</
mosExternalMetadata
>
</
mosObj
>
The list of channels contains the active destinations (destinations linked to a graphic engine) as configured in the Overlay Graphics interface.
For details of configuration, refer to section xxx.