Viz Mosart is Vizrt's powerful suite of tools for studio automation, production assistance, and advanced graphics control. It enhances consistency and efficiency in live and as-live production, so that even complex shows can be run error-free from a single operator position.

Viz Mosart controls devices flexibly according to templated sets of repeatable actions, automating that control according to stories prepared in a rundown and enabling creative manual interaction whenever needed.

In this document you will find listed all important changes since Viz Mosart 5.15.

Viz Mosart 5.16.0

Release Date: 2026-08-03

Release Highlights

Viz Mosart 5.16 extends live sport workflows with control of EVS playlists over LinX and the ability to address EVS clips by LSM ID. Overlay graphics gain a new browser-based Named Overlays Editor, and the Overlay Graphics Interface can now run as a Windows service. A new REST endpoint takes the Mosart server out of idle, so client applications and external panels can activate a server without the Viz Mosart GUI.

Adaptive Live Producer continues as an early preview feature, with a set of preview wall and transition fixes in this release.

New Features and Improvements

Video Clip Playout

• Control of EVS playlists over the LinX protocol. A playlist can be planned and played from the rundown without its contents being known in advance. This is built for live sport, where highlight packages are assembled minutes before air and are sometimes still being edited after playout has started.

• EVS clips can be addressed by LSM ID instead of by clip name.

• Loop command support for Ross video servers in the VDCPtcp (MDIO) driver, enabled by an opt-in configuration flag.

• The Grass Valley AMPP driver now loads large clip lists in the background, so video servers, the vision mixer and Media Administrator remain available while the list loads.

Graphics

• A new Named Overlays Editor lets operators create, edit, import, export and manage named overlay graphics from the browser, instead of hand-editing NamedOverlayGraphics.xml on the Mosart Server.

• Early access - The Overlay Graphics Interface can run as a Windows service, as alternative to its existing interactive mode.

• Manual overlay graphics are now displayed in stories that contain no Mosart primary template. Previously a primary template was required, and had to be placed ahead of the manual graphics in the story body — so operators added a dummy ADLIB template to every story just to make manual graphics appear.

• The Overlay Graphics Interface now pushes a handler to every destination it is mapped to. Previously only the first destination found for a handler reached the Media Sequencer profile, which had to be worked around with dummy configuration entries or macros.

• Overlay graphics destinations can be changed directly from the Showmaker rundown editor. The change is saved onto the rundown, so it applies whenever that rundown airs.

• Overlay graphics from AE Live now honour the out behaviour set in the plug-in — open, story end or background end — instead of always falling back to the default. The AE Live graphics driver was introduced in Viz Mosart 5.15.

Rundown and Story Handling

• Keyboard shortcuts now show on-air status for overlay graphics, not only for Mosart primary templates.

• The Viz Mosart GUI setting Disable rundown autoscroll now also keeps keyboard shortcut binding on the selected story, instead of letting the bindings follow the on-air story.

• The newsroom setting NCS omit stories (omitrows) now works for MOS-based newsroom systems such as OpenMedia and Showmaker. Previously it worked only with iNews.

Template Editor

• A template can now restrict which templates its items may be changed into from the Quick Editor, chosen from the template hierarchy in a new Quick Edit tab in the Template Editor. This prevents incorrect on-air selections in composite lower-third workflows, where the Quick Editor would otherwise offer every template of the type. Templates without a restriction behave exactly as before.

Remote Control API

• A new REST endpoint takes the Mosart server out of idle, the equivalent of clicking the status indicator in the Viz Mosart GUI. Client applications and external panels can now activate a server that has just been started or switched to standby. Connected clients are also notified of idle and active state changes, so status indicators stay correct across a server restart.

Web Applications

• The Rundown Viewer now shows the auto-take indicator already present in the Viz Mosart GUI.

Server Administration

• AV Automation Subtitles settings have moved from Device Properties into the unified Settings window. Existing settings are imported automatically, and saving applies them without restarting AV Automation.

Security

Viz Mosart 5.16 strengthens both directions of trust: how the Mosart Server is reached from browsers and other systems, and how Viz Mosart authenticates towards the devices it controls. For setting up sign-in end to end, including what your identity provider must put in the tokens, see the Viz Mosart Administrator Guide, chapter Security in Viz Mosart Ecosystem.

• Per-user roles on the Named Overlays API. When OIDC authentication is enabled, the Mosart Server now enforces the mosart-admin and mosart-viewer roles on the Named Overlays API. Viewers can read named overlays but cannot create, edit, delete or import them, and the restriction is applied on the server rather than only hidden in the browser. With OIDC disabled, behaviour is unchanged.

• Generic REST devices can authenticate with tokens. The Generic REST driver gains an OAuth2 Client credentials grant, with client ID, secret and optional scope, so a device signs in as its own service account rather than with a person's credentials. A new TokenLogin authentication type covers devices that issue tokens from their own login endpoint, with configurable credential format, token response format, token header and refresh interval.

• Control Mosart over REST with authentication on. A Generic REST device pointed at a Mosart Server used to stop working the moment OIDC authentication was enabled, because the shared API key it relied on is turned off in that mode. The device now gets its own token from your identity provider instead.

• Device certificates are trusted explicitly. A new Device certificate thumbprint setting lets a Generic REST device with a self-signed certificate be trusted by pinning that exact certificate. An expired certificate, or one belonging to a different device, is still rejected.

• Mosart server settings cannot be edited from a browser when OIDC is enabled. The Mosart Server Settings page that the Web Apps Configuration Tool opens is not available with authentication enabled. Edit the settings on the Mosart server itself: in Manus Administrator, type settings in the console, or in AV Automation use Devices > Settings.

• Enabling OIDC authentication on a Mosart Server switches off the shared REST API key entirely: the key is not checked at all, so every integration that authenticates with X-API-Key is refused with 401. This includes the Elgato Stream Deck plugin and your own scripts. Plan for it before enabling authentication in production. See the Viz Mosart Administrator Guide, chapter Security in Viz Mosart Ecosystem.

Fixes

Adaptive Live Producer

• Preview wall and transition fixes: leftover content no longer remains on a superchannel after a DVE story is set as next; DVEs without a switcher crosspoint now receive their preset transition on the preview wall; background content transitions are no longer replaced by the keyer's transition; and a cued fullscreen graphic no longer plays its in-animation twice when two such stories are cued back to back.

Switching and Routing

• The RossTalk driver for Ross Carbonite and Acuity now sends explicit keyer on and off commands instead of a toggle.

• The Template Router now routes switcher crosspoints through Keyfill devices. This previously required internal aux routing on the vision mixer as a workaround.

Video Clip Playout

• Playout no longer freezes on the last frame when short EVS clips play back to back. Clip database resynchronisation no longer delays cueing.

• On-air AUTO TAKE NEXT now follows a growing clip, instead of firing at the clip's original duration.

• Clip durations reported by video servers controlled over VDCP are no longer corrupted after a rundown reload. Overlapping requests on the VDCP connection could interleave and return the wrong mark-out, so clips showed incorrect durations in the Viz Mosart GUI until Media Administrator was restarted.

Frame Accuracy

• In genlock mode, autotakes no longer fire early, and video server calibration is applied, when a show starts on an autotake story.

Audio

• The Calrec audio mixer driver now connects when the Mosart server goes from idle to active. A queued connect could be discarded by the preceding disconnect, leaving the mixer unusable until the driver was reloaded manually — including after a switch between main and backup servers.

• Muting a fader directly in the Sisyfos audio controller is now reflected in Mosart. Previously Mosart derived the mute state from program and voice-over state only, so a mute set on the Sisyfos surface went unnoticed. This requires a Sisyfos version that reports the mute flag; against earlier versions behaviour is unchanged.

• Duplicate audio channel names imported from TriCaster are now distinguished from each other, so the intended fader is addressed.

Media Administrator

• Quantel connection strings using Type=QuantelPlayer now import correctly, instead of being read as AirSpeed.

• The TriCasterSearch driver no longer re-adds clips without metadata to the DDR on every reconnect.

Camera Robotics and Lighting

• The Camerobot SendDuration option can now be enabled through configuration. It was previously stripped before reaching the driver, making the feature unreachable.

• Communication with a MIDI Show Control light controller works again when Media Router is enabled for light control.

Viz Mosart GUI

• Duplicating a shortcut in the Keyboard Shortcut Editor now duplicates the selected shortcut, rather than the first one in the list.

• Rundown changes made in SAGA are now reflected reliably in the Viz Mosart GUI when both main and backup are active.

Remote Control Service and API

• Commands are no longer delivered twice to Manus Administrator after a SignalR reconnect, or through REST broadcast fan-out.

• Saving in the Remote Control Service settings editor no longer discards all values.

• Keyboard shortcut export from the Viz Mosart GUI to the server now works when SignalR is configured for HTTPS.

• Hold Audio Transition and Hold Video Transition now work from template control commands and from the REST API.

• SignalR clients that fall back to Server-Sent Events or long polling are no longer rejected for a missing API key on the Mosart hub. Previously only the initial negotiate request was exempt, so every subsequent message and the closing request failed authentication.

Logging

• As-run log events triggered by a template command are no longer silently dropped when the template is taken through AV Automation, for example from a direct-take keyboard shortcut. The event now reaches the as-run log as intended.

Jira Issues in This Release

The Viz Mosart issues covered by this release note.

MOSART-11509, MOSART-11551, MOSART-12797, MOSART-14281, MOSART-14345, MOSART-14427, MOSART-14438, MOSART-14441, MOSART-14458, MOSART-14500, MOSART-14668, MOSART-14701, MOSART-14704, MOSART-14785, MOSART-14803, MOSART-14804, MOSART-14809, MOSART-14810, MOSART-14813, MOSART-14816, MOSART-14819, MOSART-14822, MOSART-14843, MOSART-14844, MOSART-14845, MOSART-14851, MOSART-14857, MOSART-14879, MOSART-14885, MOSART-14887, MOSART-14914, MOSART-14916, MOSART-14917, MOSART-14920, MOSART-14922, MOSART-14934, MOSART-14945, MOSART-14954, MOSART-14955, MOSART-14966, MOSART-14973, MOSART-14980, MOSART-14981, MOSART-14987, MOSART-14988

Deprecations

Recent notable changes

• 5.14.0: the Keyable Timing Display is deprecated, and is no longer included in the Viz Mosart Timing Display installer.

• 5.14.0: the installer for ActiveX NRCS plugin is no longer included, since the ActiveX NRCS plugin was deprecated in Viz Mosart 5.13. Customers will need to use the HTML-based plugin (Mosart Web Apps NRCS Plugin).

• 5.12.0: the legacy Showmaker Windows application is no longer supported. The new Showmaker (currently in early access mode) is part of the Mosart Web Applications (Mosart Web Apps Showmaker).

• 5.11.0: the MMTrio executable is no longer included.

• 5.10.0: It is expected that users of Viz Mosart have now migrated to the Combined Manus Administrator introduced in Viz Mosart 5.2.0. From this version of Viz Mosart, the two original iNews and MOS versions of Manus Administrator are deprecated.

Upcoming changes

• In a future version of Viz Mosart (version TBC), support for the Viz Mosart Timing Display client application will be deprecated. Customers are encouraged to migrate to the HTML-based timing display that is available through the Mosart Web Applications. Vizrt is continuing to strengthen the web-based architecture which serves this timing display, and to enhance its functionality where customer experience exposes use cases which are not yet fully satisfied.

• In a future version of Viz Mosart (version TBC), the Keyboard Shortcut Editor (legacy) in the Viz Mosart GUI will be deprecated, to be fully replaced by the new improved Keyboard Shortcut Editor. This new editor is already available in parallel to the original one in the Viz Mosart GUI. Customers are encouraged to start using this new editor, since Vizrt will continue to enhance its functionality, based on customer experience and feedback.

Installation and Upgrade

Installing for Current user only or for Anyone who uses this computer

Normally, Viz Mosart applications are installed for Anyone who uses this computer, but in some situations it is preferable to install for Current user only. If you have a previous installation for Anyone who uses this computer and then install for Current user only, Windows' Apps & Features will show two installations of the application, both the previous one and the new one, and you will also see two shortcuts on your desktop. This is a feature of Windows, but could lead to confusion with subsequent updates.

• A recommendation to avoid this particular situation is to uninstall the previous Viz Mosart application before installing the new one.

[*] The various Viz Mosart applications shall normally always be on the same version, to ensure compatibility of features. If the Viz Mosart applications were installed under the various users' dedicated locations, then during an upgrade, you would have to repeat the installation of a new version for all Viz Mosart users for that computer. In addition to the time and effort this would require, you risk that some users might miss the upgrade. When one of these users later starts a Viz Mosart application, for example the Viz Mosart GUI, it would no longer be compatible with the commonly upgraded Viz Mosart applications, like the Viz Mosart Server.

Please refer to the Viz Mosart Administrator Guide, section Installation.

System Requirements

Recommendations

For further details, see the Installation > Prerequisites section in the Viz Mosart Administrator Guide.

General

• Microsoft .NET Framework 4.8.

• Microsoft Visual C++ 2015-2022 Redistributable (both x86 and x64).

• Microsoft Edge WebView2 Runtime (x64).

Viz Mosart Server

• Microsoft Windows Server 2022.

• Microsoft Windows Server 2019 (only with Extended Support from Microsoft - until 2029-01-09).

• Microsoft Windows Server 2016 (only with Extended Support from Microsoft - until 2027-01-12).

• Microsoft Windows Server 2012 R2 (only with Extended Security updates from Microsoft - until 2026-10-13).

Viz Mosart client computers (GUI, Audio Panel, Timing Display, Audio Player)

• Microsoft Windows 11.

• Microsoft Windows 10 (only with the Windows 10 Extended Security Updates program).

Network Bandwidth

• 1000 Mbps (Gigabit) Ethernet card is required on the Viz Mosart client computer if NDI is used for live preview in the Preview and Program windows.

Upgrade

As a standard procedure, always make backups before upgrading. Please backup all files in the following locations:

• C:\channeltemplates

• %localappdata%\Mosart_Medialab

• %programdata%\Mosart Medialab\ConfigurationFiles

• %programfiles(x86)%\Mosart Medialab\<Mosart application>\ConfigurationFiles

• All files with extension .exe.config in folders %programfiles(x86)%\Mosart Medialab\<Mosart application>\ where <Mosart application> is the relevant Viz Mosart application (for example Mosart Server, Mosart GUI).

Windows registry settings for:

• HKEY_CURRENT_USER\Software\[Wow6432Node\]Mosart Medialab

• HKEY_LOCAL_MACHINE\Software\[Wow6432Node\]Mosart Medialab

For the upgrade procedure, see the Viz Mosart Administrator Guide, section Installation.
You will always find the latest updated documentation for Viz Mosart at the Vizrt Documentation Center.

If you do not have Internet access to the above documentation, a quick guide for installation is given here:

1. Download all relevant Viz Mosart installation files to the preferred location.
   The default location is C:\Mosart\Installers. You are advised to make a sub-directory for the installers for a particular version/build containing all the MSI installer-files and any other supplemental files.

2. Stop all Viz Mosart Windows services.

3. Double-click the installation file, and follow the prompts to complete installation. Note that after completing this step for the Viz Mosart Server and the Viz Mosart GUI, the documentation is available in the installation sub-folder Documentation.

4. Repeat the above step for all relevant installation files.

5. As the last steps you may need to start a set of Windows services to make Viz Mosart run properly (not needed after installing the Viz Mosart Server or the Viz Mosart GUI client, these services are started by the installer). The services are configured to automatically start when the computer is started. The safest is to reboot the computer to verify that this automatic start of the services is working.

Installations with Viz Mosart in several galleries

If you have several galleries running an earlier Viz Mosart version, like Viz Mosart 3.x or Viz Mosart 4.x, you can safely upgrade one of the galleries to Viz Mosart 5.x while the others stay on their current version.

Previous Versions

In accordance with the Vizrt Global Support Handbook section Software Lifecycle, support for older versions of Viz Mosart ends 24 months after a subsequent minor or major version is released.

• With this release of Viz Mosart version 5.16, earlier versions will therefore no longer be supported after 2028-08-03

• At the date of this release, Viz Mosart versions 5.7 and earlier are no longer supported.

Documentation

Latest, continually updated documentation for Viz Mosart 5.16 is available at the Vizrt Documentation Center.

Support

Support is available at the Vizrt Support Portal.