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.1

Release Date: 2026-08-10

Release Highlights

This 5.16.1 version is a maintenance release with no new features to the software since Viz Mosart 5.16.0.

Fixed Issues

Video Clip Playout

• Fixed an issue affecting EVS video servers configured in mirror mode with IPDirector (IPD API). If one of the mirrored servers became unavailable, Viz Mosart could no longer cue or play out clips from the remaining server either, failing with a Clip not found error (The previous workaround was to select a salvo containing just the available server) (MOSART-15009).

Viz Mosart 5.16.0

Release Date: 2026-08-03

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.

Adaptive Live Producer

• Fixed: Some remaining issues in this early preview feature have been resolved, mainly affecting the preview wall and content transitions (MOSART-14785, MOSART-14809, MOSART-14816, MOSART-14822).

Switching

• New: The Generic REST driver can now control an Imagine Selenio Network Processor (SNP). A template command recalls a logo on a master-control keyer by logo ID, and the master-control status endpoint serves as the driver's heartbeat. Setup uses the new TokenLogin authentication type and, for the SNP's self-signed certificate, the new Device certificate thumbprint setting (MOSART-14668).

• Fixed: The Template Router now routes switcher crosspoints through Keyfill devices. Previously only Aux devices worked, so operators had to set up internal aux routing on the vision mixer as a workaround (MOSART-12797).

• Fixed: The RossTalk driver for Ross Carbonite and Acuity now sends explicit keyer on and off commands instead of a toggle. A toggle could leave a keyer in the opposite state to the one the template asked for (MOSART-14844).

Video Clip Playout

Clip Players

General

• Fixed: On-air AUTO TAKE NEXT now follows a growing clip. Previously the displayed duration grew as the clip recorded, but the auto-take still fired at the clip's original cued duration. Affects all video-server drivers with growing clips (MOSART-14954).

EVS

• New: Viz Mosart can control EVS playlists over the LinX protocol. A playlist can be planned and played from the rundown without its contents being known in advance — built for live sport, where highlight packages are assembled minutes before air and are sometimes still being edited after playout has started. Enable it by setting a PlaylistPrefix such as PL: on the EvsLinX connection; a clip name of <prefix><number> is then treated as a playlist reference. Playback starts from the first element, and the feature requires UseIPDirectorAPI=false (MOSART-14345).

• New: EVS clips can be addressed by LSM ID instead of by clip name (MOSART-14704).

• Fixed: Playout could freeze on the last frame for several seconds when very short EVS clips played back to back, then recover on its own. A clip-database resynchronization on the LinX connection delayed the cue of the next clip past the point where it was needed on air (MOSART-14980).

GV AMPP

• Improved: The Grass Valley AMPP driver now loads large clip lists in the background. Previously the video servers, the vision mixer and Media Administrator were all unavailable until the full clip list had loaded (MOSART-14458).

VDCP

• Improved: Loop command support for Ross video servers in the VDCPtcp driver, where the loop template function previously had no effect. Enable it with the new EnableLoopingRoss flag in ClipServerVDCP.xml (MOSART-14922).

• Fixed: Clip durations reported by video servers controlled over VDCP could become wrong after a rundown reload, showing random mark-out values in the Viz Mosart GUI until Media Administrator was restarted (MOSART-14813).

Clip Status

• Fixed: Media Administrator connection strings using Type=QuantelPlayer now import correctly. They were previously read as AirSpeed, so the media servers were misconfigured after upgrading (MOSART-14810).

• Fixed: The TriCasterSearch driver no longer re-adds clips without metadata to the DDR on every reconnect. Against an unstable TriCaster this could compound into tens of thousands of duplicate DDR entries and destabilize the device further (MOSART-14966).

Graphics

• Fixed: 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, so complex graphics configurations had to be worked around with dummy configuration entries or by pushing the whole configuration from macros in INIT break templates (MOSART-11551).

• New: A 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. Graphics can be dragged in from Viz Pilot Edge, and the editor imports and exports both current and legacy XML formats, so an export is a drop-in replacement for the file. It is studio-scoped, shows main and backup server status, and can sync overlays to the backup server (MOSART-14427).

• New: When OIDC authentication is enabled, the Mosart Server 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. The roles were previously named namedoverlays-admin and namedoverlays-viewer; if you have already assigned those in your identity provider, rename them before upgrading. Assign the roles before enabling authentication. With OIDC disabled, behavior is unchanged (MOSART-14885).

• Improved: Overlay graphics from AE Live now honor the destination and out behavior set in the plug-in — open, story end or background end — instead of every graphic being treated as fullscreen. The AE Live graphics driver was introduced in Viz Mosart 5.15 (MOSART-14441).

• Improved: 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 (MOSART-14803).

• New: An overlay graphics item can be re-routed to a different destination — DSK, WALL, TICKER or a configured custom destination — directly from the Showmaker rundown editor. The change is saved onto the rundown rather than applied as a runtime override, so it takes effect whenever that rundown airs (MOSART-14851).

• New: Early access - The Overlay Graphics Interface can run as a Windows service, as an alternative to its existing interactive mode. The service is registered by the installer with manual startup, so existing interactive workflows are unchanged (MOSART-14917).

Audio

• Fixed: Duplicate audio channel names imported from TriCaster are now distinguished from each other. A TriCaster Quick Connect could produce two channels both named INPUT 15 — one the input, one its talkback channel — and Mosart addressed the wrong fader, so level changes appeared to have no effect (MOSART-14438).

• Fixed: The Calrec audio mixer driver now connects when the Mosart server goes from idle to active. Previously the mixer stayed unconnected and unusable until the driver was reloaded by hand, which also made a switch between main and backup servers impractical. With this, it is no longer a requirement to have Connected When Idle active for Calrec Audio Mixers (MOSART-14934).

• Fixed: 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 and Mosart-side mute operations could behave opposite to what the operator expected. This requires a Sisyfos version that reports the mute flag; against earlier versions behavior is unchanged (MOSART-14987).

Camera Robotics and Lighting

• Fixed: Communication with a MIDI Show Control light controller works again when Media Router is enabled for light control (MOSART-14500).

• Fixed: The Camerobot SendDuration option can now be enabled through configuration. The option was added in Viz Mosart 5.15 but was stripped before reaching the driver, so the movement-duration feature could not be turned on at all (MOSART-14955).

Rundown and Story Handling

• Improved: The Viz Mosart GUI setting Disable rundown autoscroll now also keeps keyboard shortcut binding on the selected story. Previously the selected story and the Media Pool stayed put after a Take Next, but the shortcut bindings jumped to the on-air story — so an operator working from a Stream Deck, with the Keyboard Shortcuts window hidden, had no way to tell what the keys were bound to (MOSART-11509).

• Fixed: The newsroom setting NCS omit stories (omitrows), which ignores stories by name, now works for MOS-based newsroom systems such as OpenMedia and Showmaker. Previously it worked only with iNews (MOSART-14804).

• Improved: Keyboard shortcuts now show on-air status for overlay graphics, not only for Mosart primary templates — useful where a keyboard is largely given over to graphics. Note that the on-air status is read from the Viz Mosart GUI program state, which does not retain graphics across a GUI restart (MOSART-14819).

• Fixed: Rundown changes made in SAGA are now reflected reliably in the Viz Mosart GUI. With both SAGA main and backup active, moving a story could leave the GUI out of sync with the actual rundown order until the operator switched to another rundown and back (MOSART-14945).

Viz Mosart GUI

• New: The Quick Editor can be limited to a chosen set of templates. When an operator double-clicks a story item to change its template, if the item's template has a restriction configured, only the permitted templates are offered — preventing wrong picks on air in composite workflows. The item's current template is always among them and stays pre-selected. To set this up, open the template’s properties in the Template Editor, tick Limit the templates offered in Quick Edit to the list below on the new Quick Edit tab, and add the templates its items may be changed into, chosen from anywhere in the template hierarchy and optionally of a different type. For templates with no such restriction the behavior is exactly as before (MOSART-14920).

• Fixed: Duplicating a shortcut in the Keyboard Shortcut Editor now duplicates the selected shortcut, rather than the first one in the list. The cause was legacy shortcuts saved without an ID; those now get one at startup. The same fault also affected deleting and unassigning such shortcuts (MOSART-14914).

Frame Accuracy

• Fixed: In genlock mode, autotakes no longer fire early and video server calibration is now applied, when a show starts on a story that has autotake enabled. Previously the whole show ran unaligned: fixed-duration stories played roughly 20 frames short, and clips went to air frozen because the calibration pre-roll never happened, with the configured calibration value having no effect. Taking any item manually restored correct behavior for the rest of the show (MOSART-14988).

Remote Control Service and API

• Fixed: Commands from the Remote Control Service could reach Manus Administrator twice, so toggle commands canceled themselves and appeared to do nothing — most visibly the Rehearsal toggle in Smart Panel. Both causes are fixed: a stale registration surviving a SignalR reconnect, and REST commands being fanned out to Manus Administrator a second time as broadcasts. Affects deployments running the RemotePanel link over SignalR (MOSART-14843, MOSART-14879).

• Fixed: Keyboard shortcut export from the Viz Mosart GUI to the server now works when SignalR is configured for HTTPS. Previously the export failed and dropped the GUI's connection, which then reconnected (MOSART-14281).

• Fixed: Saving in the Remote Control Service settings editor no longer discards all values. The editor reported success and wrote a backup while leaving the settings file byte-identical, so changes silently vanished. Affects the opt-in Manus and RCS settings editors (MOSART-14845).

• New: 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 (MOSART-14857).

• Fixed: Hold Audio Transition and Hold Video Transition now work from template control commands and from the REST API. Previously both were accepted but did nothing, so they were unusable from an external panel (MOSART-14973).

• Fixed: 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. Only the initial negotiate request was exempt, but those transports send every message as POST and close with DELETE, so all subsequent traffic failed authentication (MOSART-14981).

Server Administration

Configuration and Settings

• Improved: AV Automation Subtitles settings — enable, subtitling system, host, port and back-to-back play delay — have moved from Device Properties into the unified Settings window. Existing settings are imported automatically, and saving re-initializes the device without restarting AV Automation (MOSART-14916).

Logging

• Fixed: 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 ASRUNLOG_EVENT command on take was affected for every event name, so the event never reached the as-run log (MOSART-14701).

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.

• New: 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 (MOSART-14668).

• New: Device certificates can be 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-14668).

• Improved: A Generic REST device can control a Mosart Server with authentication enabled. Such a device used to stop working the moment OIDC authentication was turned on, because the shared API key it relied on is not used in that mode. The device now obtains its own token from your identity provider instead (MOSART-14668).

• Improved: The Mosart Server settings editor cannot be used from a browser when OIDC authentication is enabled. The editor has no browser sign-in of its own, so it now returns a page explaining this rather than a bare refusal. Instead, edit the settings directly on the Mosart server, in the unified Settings window (MOSART-14668).

• Note: 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 — including the Elgato Stream Deck plugin and your own scripts. This has been the behavior since OIDC authentication was introduced in Viz Mosart 5.15. Plan for it before enabling authentication in production. See the Viz Mosart Administrator Guide, chapter Security in Viz Mosart Ecosystem.

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.