General

• The Viz Mosart User Guide and the Viz Mosart Administrator Guide have received more updates, both in general and for fixed issues and improvements mentioned in these Release Notes. These guides are included with the Viz Mosart GUI and Viz Mosart Server installers. At any time, more updated documentation for Viz Mosart 4.1 can be found at https://documentation.vizrt.com/viz-mosart-4.1.html.

Viz Mosart UI

• Improved status indications for Crossover (MOSART-9539).

• The font size for the Script window was reduced in Viz Mosart 4.0, but this made it hard to read the text. To improve this, the font size has now been reset to the same as it was in Viz Mosart 3.x (MOSART-9532).

NRCS integration

• Improved the MOS NRCS feedback functionality used to send template sets and templates to a NRCS. This now works a s expected when both GroupedByType and SendAllTemplateSets are enabled (MOSART-9288).

System Requirements

Upgrading FAQ

Some questions with answers around upgrading an existing installation, with respect to new features in Viz Mosart 4.

For other details see the System Requirements section in this document.

MIA (Mosart Installation Administrator)

If you use MIA, r efer to the Viz Mosart Administrator Guide , section Viz Mosart Installation Administrator for further details.

Hierarchical Template Sets

Do Hierarchical Template Sets require a complete new set of templates or are they backwards compatible with template sets from a previous version?

• You can continue to use the existing channel templates without any modifications, so Viz Mosart 4 is backwards compatible.

Can I go back to the previous Mosart version after I have started using Hierarchical Template Sets?

• Yes, you can, but with some limitations. The templates in the base template set (the template set that other template sets inherit from, either directly or indirectly) can be used with the previous version. Inherited template sets (a variant of a base template set) can in practice not be re-used in a previous version of Viz Mosart, as the variant only includes the (few) additional templates that override a base set template, plus templates specific for this template set.

I use Viz Mosart Template Database - what is the effect of upgrading from Viz Mosart 3.x to Viz Mosart 4?

• When starting Viz Mosart 4, the full Template Database (for all galleries), is automatically upgraded to a new schema. This upgrade is backwards compatible, so you can continue to operate towards the upgraded Template Database from galleries with earlier versions of Viz Mosart.

• After testing Viz Mosart 4 you can safely downgrade to an earlier version of Viz Mosart and continue to use the template database as before, although with the limitations that inherited template sets are not usable (as described in "Can I go back" above).

Viz Mosart ActiveX

Are the MOS objects the same in Viz Mosart 4 as in earlier Viz Mosart versions?

• Yes.

Can a rundown created with Viz Mosart 4 ActiveX be loaded in a Viz Mosart Server of an earlier version?

• Yes.

Can rundown elements created by Viz Mosart 4 ActiveX be edited in an earlier ActiveX, and vice versa?

• Yes.

Is this the same for all newsroom computer systems?

• Yes.

Newsroomsettings

• Before upgrading, make sure you take a backup of newsroomsettings.xml.

• If you are upgrading from a version before release 3.6.7, or before 3.7.0.23184, the newsroomsettings.xml file is upgraded to version 6 (you will be asked this when Manus Administrator is started first time after upgrade).

• If you for some reason need to roll back to an earlier Viz Mosart version, newsroomsettings.xml will not be downgraded automatically to the older version, so you have to manually replace the newsroomsettings.xml file with the backup file after downgrade.

• Alternatively, if no backup was done, you should remove the <graphicdestinationletters> tag from the XML file and re-add them using Manus Settings.

CasparCG

Binaries for CasparCG are no longer distributed as part of the Viz Mosart installers.

• Please contact Viz Mosart Support for further information.

Graphics Handling

• Fixed two issues introduced in Viz Mosart 4.0.2 that led to commands for graphics preview and preload being sent too often and at wrong times (MOSART-9330, MOSART-9381).

• When using Set As Next, graphics could be pre-taken in situations where pre-take was actually not allowed. This issue has now been fixed. (MOSART-9385, MOSART-9489).

• Fixed an issue where for some graphics handlers, typically wall handlers other than WALL, pre-take of overlay graphics would not work (MOSART-6485).

• In AVAutomation there was an issue introduced in Viz Mosart 3.9.2 where you could no longer have multiple fullscreen graphics engines for one graphics handler. The Administrator Guide has also been updated to better describe the feature of having multiple fullscreen graphics engines for one graphics handler (MOSART-8923).

• When using Media Router (MMR), it has not been possible to get preview of overlay graphics to work. This has now been fixed, so that preview engines configured for MMR will work (MOSART-9359).

Template Handling

• From Viz Mosart 4.0.0 it was not allowed to have spaces in front of template variant names. This broke existing workflows where such leading spaces were used to create a favorite templates list. In addition, the Template Editor would try to remove both leading and trailing spaces when a template was edited, but this led to problems with saving the template, and risk of losing it altogether. This issue has now been resolved so that it is again allowed to use leading spaces in template variant names. Note however that trailing spaces are still removed, since these could otherwise cause issues when saving templates to a template database (MOSART-9054, MOSART-9152, MOSART-9358).

• Fixed an issue introduced in Viz Mosart 4.0.2 when working with Hierarchical Template Sets. When trying to save templates in an inherited template set, you could get an unhandled exception in the Template Editor (MOSART-9488).

Viz Mosart UI

• Fixed an issue when the Use grouped stories feature was turned on, where Drop Keys would not show clip description if the ADLIBPIX template had graphics control enabled (MOSART-9395).

• From version 4.0.2 there was an issue in the Preview window where changing newsroomtag key sources would not have any effect on the vision mixer; no crosspoint was changed when you changed source in the Preview window. This issue has now been resolved (MOSART-9631).

• In version 4.0.2 you could with some graphics workflows have templates with graphics contents show up with checkerboard status even if the content was available. This issue has now been resolved (MOSART-9405).

• In the Quick Access Panel's Story slug filter, an issue was introduced in version 4.0.0 that made it impossible to have more than one filter active. This has now been corrected, so that you can again add several Story slug filters (MOSART-9686).

Video Server control

• On a certain video server brand, if the video server was restarted while connected to Viz Mosart, Media Administrator and AV Automation could crash with an unhandled exception (MOSART-9259).

• On the same video server brand, there was an issue in a third party library that could be triggered when Viz Mosart connected to the video server. The third party library has now been updated so that this issue shall no longer occur (MOSART-9283).

Viz Mosart Installation

• The GUI installer had a flaw in checking for whether or not Microsoft Visual C++ Redistributable 2013 x64 was installed. This flaw could make it impossible to install the Viz Mosart GUI on some 64 bit computers (MOSART-9407).