Saving Changes

Any changes made to the Newsroom Settings configuration must be saved:

1. Either

   1. Go to File > Save, or,

   2. Close the Newsroom Settings Editor and select Save

2. Restart Manus Administrator for changes to apply.

Newsroom Settings Editor - Edit Menu

The Edit menu lists the configuration categories that are available.

• NCS tags: Menu for assigning NCS command aliases from the newsroom system to the corresponding Viz Mosart type. Each type can have multiple aliases, i.e. for the Camera type the aliases can be 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: Only applies to the iNews system. List of iNews grommet commands that will be ignored in Viz Mosart.

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

• NCS accessory stories: Mosart perceive the story with the title as a story with accessories only.

• NCS lowerthird mapping: List for converting lower third template names from what is written in the NCS (origin) to the desired 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 should be kept on-air for the duration of the parent Viz Mosart template.

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

• Lower third none auto out: Lower third variants that should be 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 handler that will automatically take the first element in the next story on PACKAGE or VOICEOVER types.

• NCS device shortening: Only applies to the iNews system. Add 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 will be translated to Viz Mosart commands. A value of (*) will translate all commands in the form (** COMMAND ***) as the * (asterisk) value is interpreted as one or more asterisks.

• Story External Metadata: The newsroom system can send special story values in a container called the mosExternalMetadata (MEM), which can be translated to special Viz Mosart content. For detail, see Story External Metadata below.

• Graphic Destination Letters: Graphic Destination Letters is used to identify output and behavior for graphics elements. For details, see Graphic Destination Letters below.
  Only applies for Vizrt VCP MOS items and use of Viz Mosart extended data element description.

• Lower thirds type translation: Only applies for native ENPS 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:

• Omit text: Omit text from iNEWS presenters area.

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

• Ignore parenthesis: Only applies to MOS. List of start and end parenthesis that encloses text ignored in VizMosart.

• MOS Id mapping: Enables Viz Mosart to recognize MOS elements from NCS and trigger specific Viz Mosart actions when encountered. Not supposed to 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: Various keywords specified during Viz Mosart installation for installation-specific behavior of Viz Mosart. Not supposed to be changed by the user.

Story External Metadata

The newsroom system can send special story values in a container called the MosExternalMetadata (MEM). These values can be translated to special Viz Mosart content. Items IDs are:
mostagname: XML-tag name in the MEM
mos_value: Value in the mostagname from the NCS
Mosart Action:

• template_type: use the value from NCS to create a new Mosart item in the rundown story. The value from NCS can be a Newsroom tag of TEXT item scope. Newsroom tags are configured in newsroomsettings.xml, examples: CAM, KAM, KAMERA, PKG etc. Or, you can use Mosart type number, example: 0 for Camera, 1 for Package etc. If the value from NCS is empty, no item will be created.
  Example:

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

  A new Mosart item of type given in the NCS column "var-1" will be created.

• item_variable: use the value from NCS to set a field on the first primary item found in the story. Non-empty values will 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" will be set on the first primary item found in the story set to the value taken from columns "var-2" and "var-3" configured in NCS.

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

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

  • If action_value contains the template type of a Mosart item (given as a newsroomtag defined in NCS tags from Newsroomsettings or as a number, i.e CAM or 0) or a list of template types separated by comma, then the duration will apply to all items of that type (eg. 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 comma, then the duration will apply to those specific items in the story (eg. 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 NCS to add or change the variant of the first primary item found in the story.

• template_transition: use the value from NCS to add effect transitions to the first primary item found in the story.
  Example:

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

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

  Enables you to set the transition type (MIX,WIPE,EFFECT) of the first item in the story from the NRCS rundown. This also gives a good overview in the newsroom on which effects are used between the stories.

  Use the value from NCS 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 whitespace, bar (|), comma(,), semicolon(;) or colon (:). The <effect_name> can be EFFECT, MIX, WIPE or their translations as configured in the Keywords section from Newsroomsettings. For example, if EFFECT is mapped as EFFEKT in Keywords section, we can add as following effects to the Mosart item: Effekt 2

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

• story_duration: use the value from the NCS 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: will execute the direct take given in the action_value at the start of the story (in the switch from the current to the next story)

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

• guimarker_X: will translate 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 NCS to override the endfrase attribute for the last primary item in a Mosart story.

• segment_duration: use the value from NCS 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 Mosart item with the value given in NCS. 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 "clip_description" will be set to the value given in NCS in the column with id "ClipDescrCol" and the field "clip_hirespath" will be set to the value "MyClip" if the value from column "ClipIdCol" in NCS is "test".
  Notice that 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 Mosart story. This is used to store specific info going to the AsRunLog

Graphic Destination Letters

Graphic Destination Letters is used to identify output and behavior for graphics elements. Use this to parse a Viz MOS object and obtain a Viz Mosart object.

MOS ID Mapping

A MOS Id mapping can be done in the newsroomsettings.xml file, as follows:

Where:

• name: The MOS ID that identifies the MOS elements coming from NCS

• value: The mapping ID used to identify a mapping for MOS element fields to be parsed. The MOS element's fields to be parsed are defined using <mosmaps> (/mmConstants/xmltemplates/mosmaps/mosmap/)

• fieldmapping: Set to true if field mapping should apply

• appendContent: Set to true if the mapping should be appended to the Viz Mosart element item

• embeddedMosartItem: Set to true if the MOS element has a Viz Mosart command embedded

• keywords: Currently only the MOS parsing of Vizrt objects uses this column. It contains a comma-separated list of device-specific values.

  • novideo: Adding this will exclude video clip information from Vizrt Video MOS objects, and only use the lower thirds of the MOS item. The video ID can then be given from any other MOS object, or a story field. For example the video id column in iNEWS.

  • nodefaultitem: Adding this will exclude Vizrt full frame graphics if no default item is found (when missing Viz Mosart template).

  • IgnoreTemplateSet (or IgnoreTemplateSet=true): When added to a MOS ID named "MOSART", the templateset attribute from a MOS object coming from NCS will be ignored. e.g.
    <tag name="MOSART" value="" appendContent="false" fieldMapping="false" keywords="IgnoreTemplateSet=true"/>

Overriding Default Field Names When Parsing iNEWS Stories

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