To Verify 32 or 64 bit environment

• Windows 10
  View the architecture with Start menu > Settings > System > About this PC.

• Windows 7
  Navigate to Start menu > Control Panel > System and Security > System.
  

• Alternatively, run a script or the command line. The example below is a Powershell:

  show architecture

  if ((gwmi win32_operatingsystem | select osarchitecture).osarchitecture -eq "64-bit") {

  #64 bit logic here

  Write "This PC is running a 64-bit OS"

  } else {

  #32 bit logic here

  Write "This PC is running a 32-bit OS"

  }

To Browse or Change Registry Keys

• From the Windows Start menu type regedit.

  • Registry settings for the Viz Mosart ActiveX on 32-bit machines are found under the registry key:
    HKEY_LOCAL_MACHINE/SOFTWARE/Mosart Medialab/Mosart ActiveX.

  • Registry settings for the Viz Mosart ActiveX on 64-bit machines (x64) are found under the registry key:
    HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/Mosart Medialab/Mosart ActiveX.

Example:

Here, the template type=PACKAGE and variant=1 with two newsroom tags, clip_hirespath and clip_description:


In the registry, FieldNameValuesToAbstract is set to clip_hirespath:

In the MOS object generated by Viz Mosart ActiveX, the tag mosAbstract contains the clip ID:

• If FieldNameValuesToAbstract=clip_hirespath;clip_description in the registry, and clip_description is set to "Test" in Viz Mosart ActiveX for the same template taken as example above, then mosAbstract is built using the value of clip_hirespath and clip_description separated by space (<mosAbstract>MyClip Test</mosAbstract>).

• If FieldNameValuesToAbstract is set to an invalid value (for example, a naming error in the newsroom tag name), then mosAbstract tag is set to <template type> <template variant> followed by the values of newsroom tags found on the template separated by space.
  Following the example above, then mosAbstract is <mosAbstract>PACKAGE 1 MyClip Test</mosAbstract>.

Value Descriptions

• FormattedAbstract: Setting this value to 1 inserts HTML codes and newlines in the MOS Abstract field of the MOS item. Use value 0 to have a plain format of the text from MOS Abstract field. Optional. Valid values: 0 or 1.

• GenerateUniqueObjId: Enables (when set to 1) or disables (when set to 0 or blank) generation of an unique objID for a MOS object. Set this to 1 for OpenMedia which identifies a MOS object by objID and itemID. Optional. Valid values: 0 or 1.

• HideAddButton: (Optional) Force use of only Drag&Drop functionality. When MOS-based NCSs are used, setting to 1 hides the Add button in the Viz Mosart ActiveX and forces the user to use Drag&Drop.
  Default is 0 (false). Valid values: 0 or 1.

• MosId: This is the default MOS ID for the Viz Mosart ActiveX. For some NCSs like ENPS, no value is required. For other NCSs like Avid iNews or Octopus, the value must be the MOS ID as mapped in the respective NCS. See Configuring the Newsroom System below for how to configure MOS ID in some of the NCSs.

• MosVersion: Forces the Viz Mosart ActiveX to use the given version of the MOS protocol. A version higher than 2.8 enables the Add/Apply button in the Viz Mosart ActiveX. Should be set to 2.8.3 for all MOS-based newsroom systems, such as ENPS and OpenMedia.

• SortXpoints: For newsroom tags with a crosspoint value, specify the ordering of these crosspoints as they appear in the drop-down menus.
  By default, Viz Mosart ActiveX sorts the newsroom tags alphabetically (both in database and channeltemplates.xml ).
  When enabled (value 1), the crosspoints are sorted based on the order in the avconfig.xml when they were created. Optional.
  Read more about newsroom tags in Other Template Functionality, section Newsroom Tags Order .
  
  

• VerboseLogging: Viz Mosart ActiveX logs using Microsoft trace mechanisms. The logging is not written in the Viz Mosart main logs. Use Microsoft Sysinternals DebugView to monitor the logging. When set to 0 or empty, only log events of type Information, Error and Warning are logged. Setting VerboseLogging to 1 enables more elaborate logging. Optional. Valid values: 0 or 1.

Configuring ENPS for Viz Mosart ActiveX

The following configuration applies to AP ENPS version 8.0+.

• Each Viz Mosart MOS device (the MOS identification of a Viz Mosart MOS connection- see mosID property from Manus Administrator Configuration/ Settings Editor - MOS) needs the following properties set in the MOS Configuration section from ENPS System Maintenance application to be able to use Viz Mosart ActiveX in ENPS client:

To open Mosart ActiveX from ENPS

• To open Mosart ActiveX from ENPS client:
  Right-click on the MOS icon (bottom right) > Select the Mosart ActiveX (the name configured in MOS Configuration, in this example Mosart@LBU).
  If several Viz Mosart MOS devices are configured, any will open Viz Mosart ActiveX.

See the Viz Mosart User Guide, section Viz Mosart ActiveX under Mosart User Interface, for further details of operator actions.

Configuring iNews for Viz Mosart ActiveX

1. Set the MosId in the registry to the same value defined in the SYSTEM.MOS-MAP rundown. This rundown can be opened from iNEWS client as any other rundown, but the user must have administrator privileges to access:
   

   

2. The first value (MOSARTMOS) is the MOS ID that is configured in the Viz Mosart ActiveX registry. The value is case-insensitive.
   

3. The second value set in iNEWS SYSTEM.MOS-MAP (test) is used when adding the MOS object into a story script as a grommet command.
   

   

To open Mosart ActiveX from iNews

• To open Viz Mosart ActiveX from iNEWS client, go to Tools > Plugins > Mosart Item Editor.

See the Viz Mosart User Guide, section Viz Mosart ActiveX under Mosart User Interface, for further details of operator actions.

Troubleshooting

If you get an error message when dragging graphics/video or composite elements to iNews rundown:

• Ensure that ShowActiveXLaunch is set to No.
  (When ShowActiveXLaunch is set to Yes, xml-related messages appear when dragging and dropping elements to the rundown).