Configuring NRCS Tags

Newsroom Settings Editor - Edit Menu

The Edit menu lists the configuration categories that are available.

• NCS tags: Menu for assigning the NRCS command aliases from the newsroom system to the corresponding Viz Mosart type. Each type can have multiple aliases. For example, Camera type can have aliases CAM, CAMERA, KAM, KAMERA, and so on.

• NCS omit stories: List of stories that should be ignored, and not displayed in the Viz Mosart GUI.

• NCS omit tags: (iNews only) List of iNews grommet commands that are ignored in Viz Mosart.

• NCS breakline stories: List of story names that are automatically converted to a Viz Mosart break line story when the story is tagged as break.

• NCS accessory stories: Viz Mosart interprets a story with this title as a story with accessories only.

• NCS lowerthird mapping: List for converting lower third template names from what is written in the NRCS (origin) to the required template (translated) in the graphics system.
  Transtype can be begins, exact or contains.

• Timecode character: Settings for textual analysis of timecode character, start character and split character.

• Keywords: Translation of CUT , MIX , WIPE and EFFECT transition keywords.

• Lower third keep while background: Lower third variants that are kept on air for the duration of the parent Viz Mosart template.

• Lower third keep while story: Lower third variants that are kept on air for the duration of the parent story.

• Lower third none auto out: Lower third variants that are kept on air until replaced by another lower third of the same variant. Can be taken out with a keyboard shortcut (for example HOME).

• Lower third keep until manual taken out: Deprecated.

• Pretake overlay on handler: Name of the overlay handlers that automatically take the first lower third element in the next story on item types configured in Manus Administrator Settings, Template allowing graphic pretake (same configurations for MOS Settings Editor MOS or iNews).
  The graphic is taken immediately regardless of its start time.
  In the following example, only the graphics with destination DSK, WALL or WALL_2 are pretaken.

  Example

  <pretakeoverlayhandlername>

  <handlername name="DSK" />

  <handlername name="WALL" />

  <handlername name="WALL_2" />

  </pretakeoverlayhandlername>

• NCS device shortening: (iNews only) A list of aliases for clipname or clip_hirespath values that can be used as newsroom tags in iNews grommets.

• Parenthesis: Start and end parenthesis. Content within these parentheses is translated to Viz Mosart commands. A value of (*) translates all commands in the form (** COMMAND ***) as the * (asterisk) value is interpreted as one or more asterisks.

• Story External Metadata: The NRCS can send external story values in a container called mosExternalMetadata (MEM). These can be translated to Viz Mosart content, as described in section Story External Metadata below.

• Graphic Destination Letters: Used to identify the output and behavior of graphic elements. See Graphic Destination Letters below.

  Note: Only applies Vizrt VCP MOS items and the use of the Viz Mosart extended data element description.

• Lower thirds type translation: (ENPS only) CG commands. Use this to translate a CG item to a Viz Mosart primary story element

  • templatetype: CG template ID to translate

  • type: Viz Mosart primary story element

  • variant: Viz Mosart variant of the primary story element

  • transtype: begins, contains or exact. Describes the usage of the templatetype value when searching the CG item.

• Newsroom tag to lowerthird channel map: Translate the handler name of a graphic item into the value defined by this mapping in the newsroomsettings.

  For example, with the following configurations in newsroomsettings.xml:

  <inewstags>

  <tags>

  <tag name="CAMERA" type="CAMERA" scope="All" />

  <tag name="PACKAGE" type="PACKAGE" scope="All" />

  <tag name="VOICEOVER" type="VOICEOVER" scope="All" />

  <tag name="VOICE OVER CLIPS" type="VOICEOVER" scope="All" />

  <tag name="CG" type="LOWERTHIRDS" scope="All" />

  <tag name="FLOAT" type="ADLIBPIX" scope="All" />

  </tags>

   

  <newsroomtypehandlernamemap>

  <tag name="CG" value="DSK" />

  </newsroomtypehandlernamemap>

   

  </inewstags>

  when a graphic MOS object is parsed in Viz Mosart and found to be a CG command as defined in the <tag> node, Viz Mosart converts it to a Viz Mosart graphic item.
  It then sets the handler_name attribute to DSK, based on the mapping defined in <newsroomtypehandlernamemap> node.
  In this case, the graphic is redirected on the DSK channel of the configured graphic engine.

• Omit text: (iNews only) Omit text from iNEWS presenters area.

• Properties: (iNews only) iNEWS custom settings, see Overriding Default Field Names When Parsing iNEWS Stories below.

• Ignore parenthesis: (MOS-systems only) List of start and end parenthesis that encloses text ignored in Viz Mosart.

• MOS Id mapping: Enables Viz Mosart to recognize MOS elements from the NRCS and trigger specific Viz Mosart actions when encountered. Must not be changed by the user.
  See MOS ID Mapping below for a description of mapping MOS ID fields in the newsroomsettings.xml file.

• MediaObject property mapping: keywords specified during Viz Mosart installation for installation-specific behavior of Viz Mosart. Should not be changed by the user.

Story External Metadata

The NRCS can share story values in a container called MosExternalMetadata (MEM). These values can then be translated to Viz Mosart content. The values are:

• mostagname: An XML element, often originating from a column name in the NRCS.

  You can derive this NRCS-assigned name for example in iNews, by Right-clicking > Field Properties:
  
  In this example, the user friendly SR Base Name is stored internally in iNews as var-007.

• mos_value: This is the text that appears in the XML element mostagname (set in the NRCS).

• Mosart Action:

  • template_type: Use a value from the NRCS to create a new Mosart item in the rundown story. The value from the NRCS can be a newsroom tag of TEXT item scope. Newsroom tags are configured in newsroomsettings.xml, (for example, CAM, KAM, KAMERA, PKG).
    You can also use the Viz Mosart type number, where for example, 0 is for Camera, 1 for Package. If the value from NRCS is empty, no item is created.
    Example:

    <mostag mostagname="var-1" mosart_action="template_type" format_type="String" />

    A new Viz Mosart item of type given in the NRCS column var-1 is created.

  • item_variable: Uses the value from NRCS to set a field on the first primary item found in the story. Non-empty values overwrite any existing fields.

    Example:

    <mostag mostagname="var-2" mosart_action="item_variable" action_value="clip_hirespath" format_type="String" />

    <mostag mostagname="var-3" mosart_action="item_variable" action_value="output_preview" format_type="String" />

    The fields clip_hirespath and output_preview are set on the first primary item found in the story, with the values taken from the columns var-2 and var-3 configured in NRCS.

  • item_duration: Use the value from the NRCS column as the duration for an item or several items in the story.

    • If action_value is empty,
      - the duration is applied to the first primary item in the story.

    • If action_value contains the template type of a Viz Mosart item (given as a newsroomtag defined in the NRCS tags from Newsroomsettings or as a number (for example CAM or 0) or a list of template types separated by comma,
      - the duration applies to all items of that type.
      For example: action_value=CAM or action_value=PKG, JINGLE or action_value=0 or action_value=1,JINGLE.

    • If action_value contains pairs <type><separator><variant> or a list of such pairs separated by a comma,
      - duration applies to those specific items in the story.
      For example: action_value=CAM=1 or action_value=CAM|1,PKG).
      The <separator> can be "=", "|", ":" , "-" or ";".
      Use Format type to select if the value is given as seconds (integer), frames (integer) or as a time code.

  • template_variant: Use the value from the NRCS to add or change the variant of the first primary item found in the story.

  • template_transition: Use the value from the NRCS to add effect transitions to the first primary item found in the story.
    This also provides a good overview in the newsroom about which effects are used between the stories.
    For example:

    <mostag mostagname="TranFromNcs" mos_value="SLIDE" format_type="String"

    mosart_action="template_transition" action_value="MIX,24" />

    Use the value from the NRCS to add effect transitions to the first primary item found in the story.
    The effect transition is given in the format <effect_name><separator><input> , where <separator> can be white space, bar (|), comma(,), semicolon(;) or colon (:).
    The <effect_name> can be EFFECT, MIX, WIPE or their translations as configured in the Keywords section in Newsroomsettings.
    For example, if EFFECT is mapped as EFFEKT in the Keywords section, we can add the following effect to the Viz Mosart item: Effekt 2.

  • story_variable: Use the value from the NRCS to set a field on all items (excluding prompters and some secondaries with type > 300) found in the story. Non-empty values do not overwrite existing fields.

  • story_duration: Use the value from the NRCS as the planned duration for this story. Use Format type to select if the value is given as seconds (integer) or as a time code.

  • directtake_pre_story: Executes the direct take template given in the action_value at the start of the story (in the switch from the previous to current story).

  • directtake_post_story: Executes the direct take template given in the action_value at the end of the story (in the switch from the current to the next story).

  • guimarker_X: Translates the set of mostagname and mos_value to a marker in the GUI, valid action_values are blank , 0 (green), 1 (orange) and 2 (red).

  • device_property: Sends a key-value pair to the device driver. For example, for camera robots this can be used to adjust speed and camera positions.

  • story_endphrase: Use the value from the NRCS to override the endphrase attribute for the last primary item in a Viz Mosart story.

  • segment_duration: Use the value from the NRCS to set the duration of a group of stories.

  • words_per_minute : Sets the read rate for a story.

  • back_time: Sets the backtime attribute for a story (the exact time when a story must start in order for the show to remain on schedule.). This is used to set a next break time of the show. The break attribute must be set to true.

  • cume_time: Sets the cumetime attribute for a story - the amount of airtime required from the beginning of the show up to a certain point in the show in order for the show to remain on-schedule. This is used to set a next break duration of the show. The break attribute must be set to true.

  • category: Sets the category attribute for a story used to identify a story category such as sports, news, business etc.

  • field_value_X : Overrides the field value of a Viz Mosart item with the value stipulated in the NRCS. This applies only to the first primary item in a story and the field must already exist for that item. For example, if the first primary item in a story is a Package with the following fields:

    <fields>

    <field name="clip_description" value="" default="" fieldtype="TEXT" keylist="" />

    <field name="clip_hirespath" value="" default="" fieldtype="TEXT" keylist="" />

    <field name="metadata_lookuppath" value="" default="" fieldtype="TEXT" keylist="" />

    </fields>

    and the following mappings are given in newsroom settings:

    <mostag mostagname="ClipDescrCol" mosart_action="field_value_1" action_value="clip_description" format_type="String" />

    <mostag mostagname="ClipIdCol" mosart_action="field_value_2" action_value="clip_hirespath=MyClip" mos_value="test" format_type="String" />

    then the field is set to the value given in the NRCS in the column with id ClipDescrCol and the field clip_hirespath are set to the value MyClip if the value from column ClipIdCol in the NRCS is test.

    Note: The attribute action_value for <mostag> node in newsroom setting can contain the field name or pairs of field name=field value separated by comma, colon, semi-colon, dash, equal or bar.

  • asruninfo: Sets the attribute asruninfo for all items in a Viz Mosart story. This is used to store specific information that is stored in the AsRunLog.

Graphic Destination Letters

Graphic destination letters identify output and behavior for graphics elements. Use them to parse a Vizrt MOS object and obtain a Viz Mosart object.

Properties

Each row contains the following columns:

• Destination mapping: The mapping defined in the Viz Mosart command from Viz super.

• Graphic type: Used to identify the output for the graphics elements, either on predefined channels:

  • Fullscreen: Full screen graphics for FULL output (channel)

  • Lowerthird: Overlays for DSK output

  • Wall: Overlays for WALL output

  • WallN: Overlays for outputs WALL_1, WALL_2, WALL_3 etc.

  • Ticker: Ticker for TICKER output
    or on custom channels (so any string can be set as graphic type).

• Templatetypefield: Index of the description field which is set as the TemplateType. (the value of the description field found at the specified index). The index is 0-based. Default: empty.
  For example: If the MosAbstract is: <mosAbstract>field1/field2/field3/field4/Mosart=S|00:04|00:10</mosAbstract> , and you set Templatetypefield=1 , then the templatetype attribute from the Viz Mosart object is set to field2 .

• Descriptionfields: A list of indexes of the fields which should be shown in the description of a Mosart story item. These fields are shown in the Viz Mosart GUI separated by the character given in the outputtxtdelimiter setting. The indexes are 0-based and are separated using a pipe ‘|’ character.
  For example: descriptionfields="0|1". Default: empty.

• Use TC Out: Specifies if the duration should be used as tc_out.

• Inputtxtdelimiter: Vizrt MOS object delimiter. Default: ‘/’ (slash)

• Outputtxtdelimiter: Viz Mosart object delimiter. Default: ‘/’ (slash)

• Mask: Specifies the timecode format of the graphics starting time, end time or duration. Default: mm:ss. Example of formats: hh:mm, hh:mm:ss, mm:ss:ff, mm:ss, ss:ff, ff.
  
  Mapping example:

Walls
There are two ways to support a configurable number of walls:

1. By having a general rule in the graphics destination mappings where the graphics type must be WallN. The destionationmapping attribute can be set to any string of alphanumeric characters.

   <graphicdestinationletter destinationmapping="Walls" type="WallN" templatetypefield="" descriptionfields="-1" use_tc_out="False" inputtxtdelimiter="" outputtxtdelimiter="" mask="mm:ss"/>

   In this case, the Vizrt graphic objects must contain a Viz Mosart string command ending in a number (this provides the wall number).
   For example:
   Mosart=cgw1|00:00|00:05 or Mosart=something2|M|S or Mosart=wall3|00:00|B or Mosart=W4|00:04|00:10 and so on.
   Given these examples, the destination for the first graphic is WALL_1, followed by WALL_2, WALL_3 and WALL_4, respectively.

2. By not ending the Viz Mosart string destination mapping with a number.
   For example:
   Mosart=B|00:00|00:05, Mosart=Z|00:00|00:05, Mosart=Wall|00:00|00:05, Mosart=Something|00:00|00:05 and so on.
   In this case, the configuration in newsroomsettings must specify the wall number in the graphics type. For the Mosart string examples given above, the configuration can therefore be:

   <graphicdestinationletter destinationmapping="B" type="Wall_2" templatetypefield="" descriptionfields="-1" use_tc_out="False" inputtxtdelimiter="" outputtxtdelimiter="" mask="mm:ss"/>

   <graphicdestinationletter destinationmapping="Z" type="Wall_3" templatetypefield="" descriptionfields="-1" use_tc_out="False" inputtxtdelimiter="" outputtxtdelimiter="" mask="mm:ss" />

   <graphicdestinationletter destinationmapping="Wall" type="Wall_4" templatetypefield="" descriptionfields="-1" use_tc_out="False" inputtxtdelimiter="" outputtxtdelimiter="" mask="mm:ss"/>

   <graphicdestinationletter destinationmapping="Something" type="Wall_5"templatetypefield="" descriptionfields="-1" use_tc_out="False" inputtxtdelimiter="" outputtxtdelimiter="" mask="mm:ss"/>

   Overlays with Mosart=B|00:00|00:05 are then redirected to WALL_2, those with Mosart=Z|00:00|00:05 to WALL_3 and so on.

As well as redirecting graphics to predefined destinations like DSK, WALL, WALL_i, FULL, the graphic destination letters rules can be used for any desired destination.
For example:

and a Vizrt graphic with Mosart string T|00:00|00:06 sends the graphic for playout on the channel TEST.

Vizrt MOS Item With Payload Data Nodes

If a Vizrt MOS item contains <mosPayload> with data entries, then the graphics_description is built from these data nodes delimited by outputtxtdelimiter.

The property inputtxtdelimiter is used only to build the slug, not the description.

If descriptionfields is empty, then the graphics_description attribute from the Viz Mosart item (created from the Vizrt MOS item) is set to the slug value (created from MosAbstract, see above).

If the field is populated, the slug is set to the description created from data nodes entries where only the data nodes from the positions specified in the descriptionfields are added and separated by outputtxtdelimiter.

Example 1:

Using a Vizrt MOS item containing the following values:

apply the following mapping:

Note that inputtxtdelimiter is empty, so the default ‘ / ’ is used.

The result is the following Mosart item. Note the slug and description attributes and graphics_description field:

Example 2:

Using the same Vizrt MOS item as above, but with the following mapping:

In the result below you can see that the delimiters are now ‘%’ instead of ‘|’. Note that templatetype is set to the value found at index 1.

Vizrt MOS Item Without Payload Data Nodes

Basic requirements

Viz Mosart requires details on whether the graphics element is a lower third, a graphics played out on a video wall engine, or a full screen graphics. Any graphic requires the following properties:

• Destination: lower third, video wall or full-screen graphics

• For lower thirds/video walls:
  - Play-out: manual or automatic
  - For automatic play-out: in time
  - Duration/out time or the special durations background end, story end or open end

• Mosart item (optional): Stored at the end of the description of the data element or as a specified field in the mosExternalMetadata section of the MOS item and is formatted as follows:
  Mosart={destination}|{in behaviour}|{out behaviour}|{X}|{F}
  where

  • {destination} is an alphanumeric string specifying the destination of the graphic. Suggested values are L=lower third, W=wall, F=full screen graphics

  • {in behaviour} is
    - either M for manual play-out
    - or a time code formatted as mm:ss (minutes, seconds) as in time

  • {out behaviour} is
    - either a time code formatted as mm:ss (minutes, seconds) as duration
    - or a single character field with values B, S or O where B=background end, S=story end and O=open end

  • X is used only for lower thirds to ignore “Replace TakeOut Logic” meaning that when taking and taking out the item, the replace logic is ignored if the value is set on the item

  • F is used only for lower thirds to force “Replace TakeOut Logic” for graphics coming from different templates with same layers (when used, it practically ignores the “O” state for a layer). Not to be confused with destination letter “F” often used for full screen graphics.

The rules which define the output and behavior for graphics elements can be configured in Graphic Destination Letters.

Field Example:

The following table contains examples of the Mosart= part of the Vizrt data element description in the value cg_gordon_brown/prime minister/Mosart=L|00:02|00:05. The data element is played out as a lower third, automatically in at two seconds with five seconds duration.

If no fields are given, the element defaults to a full screen graphics element.

VCP template requirements

The Mosart field is supported when embedded as a part of the VCP data element description or as a dedicated field in the mosExternalMetadata section.

Storing the Mosart field in the VCP data element description

When saving the VCP data element, the Mosart field shall be appended to the stored database description (the name of the data element).

Storing the Mosart field in the mosExternalMetadata section of the VCP data element

This method is only supported if the mosExternalMetadata data section is enabled for the VCP Template Filler ActiveX. See Appendix A for configuring the ActiveX to include this section in the MOS object.

The scene needs a ControlObject. The Mosart field should be stored in a hidden text field in the template, and the text field shall use Mosart in the ControlObjectName property. The Mosart field can either be included in the scene or added manually after importing the scene to the Viz Template Wizard.

VB script Example

The following VB script can be used in a Vizrt Template Wizard template and returns a properly formatted Mosart field string:

Viz Pilot plugin Prerequisites

To enable the mosExternalMetadata section in the Viz Pilot News (Active X) plugin, the system administrator must also enable a field in the VCP parameters list in the Viz Pilot database.

If you Viz Pilot 5.7 or later, this setting is available in the Viz Pilot Data Server settings page found in:

http://[hostname of PDS]:8177/settings#Params

In the Value column, the checkbox should be checked (set to true).

If you have a Viz Pilot version older than 5.7 this is easily achieved by opening the Preferences editor in the Viz Content Pilot (Options → Preferences → Advanced), by adding or editing the field called ax_add_dbdata_to_mosexternal setting the value to y.

Defining Default Values for Lower Thirds

You can set default values for parsing of lower third objects. Usually these values are set from the objects received from the NRCS. Altering these values is usually part of a customization task.

• In newsroomsettings.xml add the default values to the mmConstants/inewstags/properties element:
  

  <mmConstants><inewstags>

  <properties>

  <item name = "DefaultLowerThirdDuration" value = "125"/>

  <item name = "DefaultLowerThirdHandlerName" value = "DSK"/>

  <item name = "DefaultLowerThirdOutBehaviour" value = "TIMECODE"/>

  <item name = "DefaultLowerThirdOwnerMedia" value = "MEDIA"/>

  </properties>

  </inewstags></mmConstants>

iNEWS: Overriding Default Field Names when Parsing Stories

When parsing the iNEWS NSML, the system extracts various field values using default field names.
These defaults can be overridden by setting new values in Newsroom Settings > Edit > Properties.

iNEWS: Presenter Instructions

You can use Mosart commands as presenter instructions in iNEWS for item types CAMERA, PACKAGE, VOICEOVER, ENDFRASE, ATTACHA, CLIPSTART, FULLSCREENGRAPHICS, DVE, TELEPHONEINTERVIEW, BREAK, JINGLE, LIVE, ADLIBPIX, CLIPHIRESPATH and ACCSESORIES.

A presenter instruction (red text) command in iNews is a text command written in the story script. The journalist designates text as a presenter instruction by selecting the text, right-clicking and selecting Format > Presenter Instruction (or shortcut Ctrl+Alt+P). The selected text appears in red indicating it is not standard story text.