This section describes how to set up and configure Story Recorder in Viz Mosart. Story Recorder settings have been consolidated into the new (Manus) Settings menu, providing a centralized UI for managing all output workflows and their parameters.

End user (Viz Mosart operator) documentation for Story Recorder is provided in the section Operation > Story Recorder of the Viz Mosart User Guide.

Prerequisites

• Verify Supported Configurations for which product versions to use with your intended Story Recorder workflow.

• The Viz Mosart system is already fully operative in live (non-Story Recorder) mode.

• The system, including studio equipment, has been calibrated for frame-accurate operations, as described in section Frame Accurate System Operations.

• A dedicated show design for Story Recorder has been prepared. Story Recorder operates in frame-accurate mode, which introduces latency compensation on primary events. Some templates and features available in Standard mode may not be supported in frame-accurate mode. A specific, separate Story Recorder show design must account for these differences.

• An SR operating license obtained from Vizrt Support.

Supported Configurations

Story Recorder supports three output workflows, each targeting a different production need:

• Story-clip production and publishing
  Stories marked for recording in the NRCS are individually recorded and published as clips, either during a live broadcast or in an offline session.

• Show-clip production with pause and retake
  Full show recording with the ability to pause, retake, and backtrack. At completion, an EDL is broadcast to a transcoder that stitches all recorded segments into a single final clip.

• Mosart EDL generation
  Generates JSON-format EDL files locally, for post-processing, transcoding, or third-party integrations. Output level: Item, Story, or Show.

The table below lists the validated combinations of NRCS, recorder, and transcoder for each workflow. Story Recorder has been designed with a flexible output architecture, and new devices and integrations can be added as needs evolve.

^*An NRCS that can provide the required story metadata fields via the MOS protocol.

1. Saga offers built-in integration.

2. Other NRCS systems (for example, iNEWS) can be configured using Newsroom Settings field mapping.
   See Viz Mosart User Guide sections Story Recorder Mode for the MOS integration details.

Overview

Story Recorder relies on several Viz Mosart server components working together:

• All Story Recorder settings are managed through Viz Mosart Central Settings.

• Manus Administrator receives the rundown and story metadata needed for Story Recorder from the NRCS.

• Av Automation controls the video server (clip playout and record start/stop), handles communication with external renderers and transcoders, and uses genlock-synchronized timecodes to ensure frame-accurate clip boundaries and EDL entries.

• Mosart Logging Service (from the Mosart Server installation, not the UI) plays a central role by capturing all on-air events with frame-accurate timecodes. Story Recorder uses these events to build EDLs and determine clip in/out points.

• Viz Coder (optional) generates short snippet clips around retake cut points for review in the Mosart UI.

The diagrams below show the data flow for each Story Recorder output workflow. See the configurations table above for the specific devices validated with each workflow.

Story clip production workflow

Stories marked for recording in the NRCS are individually recorded and produced as clips.

Show clip production with pause and retake

The entire show is recorded with the ability to pause, retake, and backtrack. An EDL is sent to a transcoder that stitches the segments into a final clip.

Mosart EDL generation

JSON-format EDL files are generated locally for post-processing or third-party integrations.

Detailed example: Vantage workflow with Harmonic Spectrum, clean/dirty recording, and snippet review

This diagram shows a specific deployment of the show clip production workflow using Harmonic Spectrum as video server, Vantage as transcoder, and Viz Coder for snippet generation around retake cut points. This configuration requires at least 2 playout ports (for A/B playout of show clips and preroll recordings) and 2 recording ports (for clean and dirty feeds).
Note: The folder where the final show clips reside is not controlled by Viz Mosart. This is set on the EDL transcoder side. In the above setup, the EDL transcoder is Vantage.

Settings (Manus ) Configuration

Story Recorder output workflows and their parameters are configured through the centralized Manus Settings menu (stored inmanus_settings.json).
This method replaces the previous XML-based configuration in LogAdapterStoryRecorderConfig.xml.

Enable Story Recorder

Clip Outputs

Configure clip output device types. Story clips are produced by the listed devices as configured here.

TriCaster

Mimir

EDL File Outputs

Configure EDL (Edit Decision List) outputs. EDL files are generated for post-processing by transcoders or for local storage.

Vantage

Produces .tsedl (Telestream EDL) files consumed by a Vantage transcoder for show-level clip stitching.

The following settings are visible only when Enable retakes is on:

Mosart

Produces JSON-format EDL files for local use, post-processing, or third-party integrations.

Recordings Housekeeping

Automatic cleanup of temporary Story Recorder recording files on the video server.

Other Settings

Related General Setting

The Use local time setting in the General section of Manus Settings affects Story Recorder EDL timecodes:

Configuring the Video Server

The video server is used playout of clips both during the show, and when recording. The setup involves configuring playout ports, recorder ports, and ensuring the correct directory and file extension settings for the various types of media resources involved.

• Media resource types

• Configuring video server recorder ports

• Clip naming pattern of temporary recordings

Media resource types

Story Recorder operations involve various types of media resources. Understanding these is important for correct directory and port configuration:

• Playout clips: The rundown clips monitored by Media Admin , cued and played out by AV Automation. They must reside in a directory that the video server accepts for playout.

• Recordings: Clips produced when recording the video server output (typically the PGM output). In the story clip production workflow, these are the raw continuous recordings from which story clips are cut. These clips are not needed for playout unless the show clip production workflow is used, where the preroll template is played-back from a recording clip. In this case, the recording directory must be the same as the playout directory.

• Story clips: Segments cut from the growing recordings, using an export job. Story clips are typically needed for playout, so they should reside in the same folder that is monitored by Media Admin (through Media Service).

• Snippet clips: Short review clips generated around retake cut points in the show clip production workflow. These are browsed in the Story Recorder floating window in the Viz Mosart UI, and used purely as visual verification of cut quality. They do not need to be available for playout.

To configure video server recorder ports

1. In AV Automation, navigate to Devices > Properties > Video Servers.

2. The Video server configuration and Mosart port configuration should already be working for your system. Otherwise, refer to the Video Servers documentation.

3. Configure the recording port(s) dedicated for Story Recorder.

4. For the recording port(s), select IsEnabled in the Story Recorder section. This reserves the port for Story Recorder.

   

5. Set the recording file extension to match the format produced by the video server (for example, mov for TriCaster, mxffor Harmonic Spectrum).
   Story Recorder uses this extension to build the correct file path when referencing the recording clip in EDLs and render jobs. The extension is resolved with the following priority:

   1. Extension field on the recording port (per-port setting).

   2. Ext property in the Server connection string.

   3. ExtList property in the Server connection string (the first entry is used).

   4. If none of the above are set, the default is mxf.

      

6. By default, Mosart supports separate directories for playout clips and recordings (see screenshot above). However, for the show clip production workflow, the recording directory must be the same as the playout directory, because the preroll template is played back from the recording clip.

7. For TriCaster, verify that the Server connection string includes the following properties:

   • HttpUsername: HTTP username for the TriCaster REST API (default: admin). Used by all workflows. Mosart needs this to request Start of Media (the timecode of the first frame) used in the command for the render job. These credentials authenticate Mosart against the TriCaster HTTP interface. Can be added via TriCaster Quick Connect editor.

   • HtpPassword: HTTP password for the TriCaster REST API . Used by all workflows, together with HttpUsername. Can be added via TriCaster Quick Connect editor.

   • AddExportJobDelayMs: delay in milliseconds before sending the export job request to TriCaster (default: 5000). Used by story clip production only. When a story ends, Mosart sends an export job to TriCaster to cut the story clip from the ongoing recording. If the export request is sent too soon (within 1–2 seconds of the cut point), TriCaster may not be ready to process it because the recording file is still growing. This delay ensures TriCaster has time to finalize the recording segment before the export is triggered.

   Example: ...;HttpUsername=admin;HttpPassword=admin;AddExportJobDelayMs=5000

8. Click Apply then Save & Close.

9. Force a reconnect to the video server with Ctrl+Shift+V (or restart AV Automation).

Clip naming pattern of temporary recordings

The temporary recording files generated by Viz Mosart are automatically named.

Single recorder:
<prefix>_<counter>_<timestamp>.<ext>

Multiple recorders:
<prefix>_<recorder name>_<counter>_<timestamp>.<ext>

Where:

• prefix: The Recording clip name prefix configured in Manus Settings (default: SRVizrt). This prefix is also used by the housekeeping job to identify SR-generated recordings.

• counter: A sequence number, reset to 1 for each Story Recorder session.

• timestamp: An automatically generated (format YYMMDDHHmmss).

• ext: The file extension configured in AV Automation > Devices > Properties > Video Servers > ExtList (the first in the list is used).

• recorder name: The Name setting on the virtual recorder port in AV Automation (for example, Rec1). Only included when multiple recorders are configured.

Example: A single recorder, prefix SRVizrt

Example: Two recorders (Rec1, Rec2), prefix SRVizrt

Show Clip Production Setup

In the Show clip production workflow, the operator pauses and retakes story items while recording a complete show.
These topics are covered:

• NRCS Metadata for Final Clip Name

• Configuring Automatic Naming of the Final Clip

• Enabling Snippet Generation at the Cut Point

• Pre Roll Duration

• Automatic Pause at end of Show

NRCS Metadata for Final Clip Name

This step is optional. By default, naming of the show (and EDL files) is derived from the rundown name.

As a convenient option, you can instead provide a flexible and predictable naming scheme through a mapping field defined in the NRCS story.
Viz Mosart will then pick up this value and use it as the base for file naming, including the final show clip name. This is explained in Configure the NRCS and Viz Mosart for automatic naming of the Final Clip Show below.

In addition, the user can also manually enter a name for the show's final clip, in the Story Recorder UI. This will overwrite the value given in NRCS.

To configure automatic naming of the final clip

In the NRCS, you can add a name that becomes the base of the final clip name in Story Recorder.

1. From the NRCS, open the corresponding rundown for the show.

2. Add an NRCS column (here for example, SR Base Name).
   The procedure is NRCS-specific and may require administrator privileges.
   The following example is from iNEWS.

   

3. Under this new column, provide a name for the show, in the first story in the rundown (here, 9AM news show - en).

4. This name will be mapped in Mosart to appear in the Story Recorder UI, when SR is enabled, as illustrated at the end of this procedure.

   The NRCS-side configuration is complete, next is to arrange value-mapping on the Viz Mosart side.

5. In the Viz Mosart console application Manus Administrator, type ns. This opens the Newsroom Settings menu.

6. From the menu bar select Edit > Story External Metadata and add the following row if not already present:

   
   where
   mostagname: the column name as specified in the NRCS (in this iNews example, var-007).

Mosart Action : must be set to item_variable .
Format Type : must be set to String .
mos_value : empty.
action_value : must be sr_final_clip_name .

7. Restart the Viz Mosart Server.

8. Verify the setup:

   1. Provide the Final Clip Show name as described.

   2. Load the rundown in Mosart UI.

   3. Enable Story Recorder mode (see Viz Mosart User Guide, in the Story Recorder section).

   4. Check that the name provided in NRCS appears in the Story Recorder UI when the associated rundown is loaded and Story Recorder mode activated.

   

Clip naming pattern for EDL files and the final show clips

EDL files and final show clips are automatically named by Viz Mosart using the following pattern:

First broadcast:
<name>_<timestamp>.<ext>

Subsequent broadcasts of the same show:
<name>_v<n>_<timestamp>.<ext>

Where:

• name — the Final Clip Show name, determined in this order of priority: value provided from the NRCS (sr_final_clip_name), or overridden by the operator in the Story Recorder panel, or the rundown name (default).

• timestamp — automatically generated (format YYMMDDHHmmss).

• ext — depends on the output: .tsedl for Vantage EDL files, or the media extension configured on the transcoder for the final clip (e.g. .mxf).

• v<n> — version counter, added from the second broadcast onwards.

Example with Final Clip Show name 9AM news show - en:

Enabling Snippet Generation at the Cut Point

To enable snippet generation

This setup is optional and generates a few seconds (configurable) of verification video, intended to reveal the integrity of a fresh cut, after a story item has been paused and then retaken. This snippet creation employs Vizrt's versatile transcoder, Coder. 

1. Download the most recent .exe version of Coder from the customer FTP, by navigating to
   /products/VizOne/Latest Versions/Individual Installers and Docs/Coder/Latest Version.

2. You need only install the Coder Worker .
   Install Coder on the same machine as the Viz Mosart Server. Coder's default installation location is in C:\Program Files\Vizrt\Coder.

3. On the machine that runs the Viz Mosart GUI, define a default media player for *.mxf files (for example, VLC).

4. In the (Manus) Settings menu, for Vantage, configure the following settings:

   1. Snippet clips folder

   2. Snippet generation delay

   3. Snippet length

5. Restart both the:

   1. Mosart Log Service (Windows Services)

   2. Viz Mosart UI

Pre-Roll Duration

The pre-roll period must be long enough for the video server hardware to reset itself and be ready to continue recording, after a pause.

To set a pre-roll duration

1. Determine the time required by your video server hardware to commence recording. This is typically 10-15 seconds.

2. Configure this value as described in Min Preroll Duration. 

3. You may increase the value in the SR panel:

   

   This setting is retained between SR sessions.

Automatic Pause at end of Show

As an option, you can automatically pause the show and recording.

To set automatic pause

1. Create a dedicated template, typically a Break.

2. Define a PAUSE_TIMELINE control command configured on the template.

   

3. Insert this template at the end of the rundown.

In the Story Recorder session, when the story before this template is taken on air, a message warns the operator that the next story is going to pause the show and thus the recording too:

Story Clip Production Setup

The following sections apply only to the story clip production workflow, where individual story items are recorded as separate clips.

NRCS Metadata for Story Clip Production

For the story clip production workflow, each story that should be recorded must carry metadata that tells Viz Mosart to produce a clip.

NRCS with built-in integration

Some NRCSs (for example, Saga) provide built-in Story Recorder integration. They include a <mosExternalMetadata> block at the story level in the MOS message (roStorySend):

The schema URI http://www.vizrt.com/mosObj/storyPublisher is what Viz Mosart matches on. The block can be present on every story — stories with Record=false are parsed but ignored by the publishing pipeline.

If another NRCS wants to support this integration, it needs to provide the same <mosExternalMetadata> structure with the storyPublisher schema.

NRCS via Newsroom Settings mapping (iNEWS, other systems)

For an NRCS that does not use the storyPublisher schema, the same metadata can be delivered via MOS item variables. The fields are then mapped to Mosart through the Newsroom Settings (newsroomsettings.xml) Story External Metadata configuration:

The NRCS column names are mapped to the corresponding sr_ action values. Both paths — the storyPublisher MOS schema and the Newsroom Settings mapping — produce identical results in Mosart.
The following example shows how iNews columns (var-20, var-21, etc.) are mapped to Mosart item_variable actions with the corresponding sr_ action values:

Keyboard Shortcuts

Control commands

Several Story Recorder actions are available for keyboard assignment. They are configured as Control Command shortcuts with the command STORY_RECORDER and an Action parameter:

Pause Timeline shortcut

In addition to the control command actions, a dedicated Pause Timeline shortcut is available:

Failover

This step is optional and requires that Viz Mosart is already set up with redundancy as described in section Redundancy.
This means that:

• Both the Viz Mosart main and backup server have same configurations for at least Mosart Administrator, AV Automation, Media Administrator and Overlay Graphics Interface.

• AV Automation is configured for mirroring on both main and backup servers (with main pointing to backup and backup pointing to main):

  

• The Viz Mosart UI is configured to connect to the backup server:

  

For Story Recorder, there are additional steps:

• Story Recorder is configured on both main and back in the same way in Manus Settings.

• Backup host and port: Configure the Backup host and Backup port settings in Manus Settings (under Other Settings) on the primary adapter, and the Listener port on the backup adapter.

• Snippet clips folder (optional): If Snippet generation around the cut point has been set up for main, this should be set up in the same way for backup. Install Viz Coder on both main and backup server. The snippet folder configured in the Settings menu must point to the same shared location on both main and backup, so that the Viz Mosart UI has access to snippet files regardless of which system is active.

• Genlock calibration: The same calibration settings from AV Automation > Devices > Properties > Genlock tab must be configured on both main and backup to ensure frame-accurate timecodes are consistent across failover (see Frame Accurate System Operations).

Verification

• The video server is prepared for recording.

• Viz Mosart is prepared to run in Story Recorder mode.

• Snippet generation around the cut point is configured (optional).

• The integration is established between Viz Mosart and the NRCS (optional).

• Failover is setup as described above (optional).

• Ensure you have calibrated the system to frame accuracy, as described in section Frame Accurate System Operations.

The Viz Mosart operator instructions, for switching on and running Story Recorder are described in the Viz Mosart User Guide, in the Story Recorder section.

Troubleshooting

For Story Recorder to operate, it must always be switched On in the Viz Mosart UI.

Failure to Enable Story Recorder Session

When the user switches on SR in the UI, you see:

Check these scenarios, in this order:

• Viz Mosart Server and Mosart UI or Mosart Audio Player are on the same machine and the server was not installed last.
  If you installed the server before the UI or Mosart Audio Player, Mosart Log Service will incorrectly point to a copy of MMAsRunLogService.exe that is located in the Mosart UI or Mosart Audio Player folder installation. Instead, this should point to the MMAsRunLogService.exe located in Mosart Server installation folder:

  

To fix this, you should either stop the Mosart Log Service from Services and start it as console from Mosart Medialab\Mosart Server\ MMAsRunLogService.exe (although you will still have same problem after a machine restart) or reinstall the applications in this order: First the Mosart UI/Mosart Audio Player and lastly the Mosart server.

After Mosart Log Service is started, enable SR again.

• Verify that the (new) Story Recorder Log Adapter, and the config LogAdapterStoryRecorderConfig.xml are setup according to section above, Enabling the Story Recorder Log Adapter, around step (3).

A common oversight is that someone forgot to un-comment the lines for Enabling the Story Recorder Log Adapter for Story Replay functionality in AsRunLogRepository.xml.

For additional help, refer to the general topic Troubleshooting Log Adapters.

• If the Viz Mosart UI is connected to a Mosart server on another machine, make sure there is no VirtualBox or similar configured on the Mosart server machine.

  

Recording Ports not Found

If when you switch on SR, you get errors about No recorders configured for Story Recorder, this indicates that the connection to the video server that performs the recorder is faulty.

• Ensure you set up Viz Mosart, with correct configuration settings selected, as explained above in To configure video server recorder ports for Story Recorder.

Even if the configured recording ports are enabled for Story Recorder as described above, you may also get this error message after switching to a different video server salvo.

After switching to a different salvo, perform the following steps:

1. Check that there are recorder port(s) configured and enabled for Story Recorder as explained above in To configure video server recorder ports for Story Recorder.

2. Restart AV Automation or force a reconnect to the new video server (use Ctrl+ Shift + V).
   This step should be done regardless whether the previous step was necessary or not.

Failure to Start Recording or Story Items not Recorded in Story Recorder Panel

Recording does not start and no story items appear in the Story Recorder panel.

• Verify in Viz Mosart Manus Administrator that logging is enabled:
  Open Media Administrator and type settings.

  

• On the machine hosting the Viz Mosart server, check that service Viz Mosart Logging Service is up and running (as service or console).
  If running as a service, verify that it points to MMAsRunLogService.exe from the Viz Mosart server installation folder.

• If the Viz Mosart Logging Service is restarted while other applications are running OK, then an action in the Viz Mosart UI (for example, reloading the rundown) must be performed to reestablish the connection to the Viz Mosart Logging Service.
  Until a Viz Mosart UI action is made, no events are logged in the AsRunLog for the first story item taken on-air.
  This leads to Story Recorder not functioning correctly. For example, recording may appear to start OK, but no story items show up in Story Recorder panel.

• If the Viz Mosart Logging Service is restarted when the Overlay Graphic Interface is being used for controlling the graphics systems, it must be restarted in order to reestablish the connection.
  Until the Overlay Graphic Interface is restarted, no graphic-related log events are logged in AsRunLog for the first graphic encountered in the rundown, meaning Story Recorder will be unable to backtrack the graphic.

• Make sure Mosart Logging Service does not run both as service and console at the same time.
  To fix, stop both and then start either as a console or as a service.

Naming of Final Clip Show from NRCS not appearing in Story Recorder UI

You have set up your NRCS to provide Viz Mosart with automatic naming of the final clip produced with Story Recorder, but the naming is not displayed in the Story Recorder panel.

Viz Mosart parses the MOS object corresponding to a story, and on the first primary story item found in the rundown it will add the show final clip show given in NRCS.

• Examine the underlying XML:
  Do Ctrl + Shift + Alt + double click in the Viz Mosart UI on the first story item in the rundown to open this window and verify if the value given from NRCS is present:

  

If this is not present, here are possible causes:

• The name is read from the first story in the NRCS rundown. Check the status of the first story.
  If for example it has been set to float, and is not displayed in Viz Mosart, you will need to add the name to whatever story in the NRCS is now the first story.

• If another story is Set As Next from Mosart UI, then you will need to add the name to this story in the NRCS which is now the first story.

• If the Show Final Clip name was changed in NRCS during a Story Recorder session, this will be taken into consideration only at the next Story Recorder session (disable Story Recorder mode and enable again for a new show).

Unreliable genlock. See more details in AV Automation status bar

If this warning is shown in the Story Recorder panel while running a show or in pause mode, this means that Viz Mosart detected problems in the configured clock source (refer to Frame Accurate System Operations) and automatically fell-back to the internal clock source.

The AV Automation status bar will also indicate that there is an issue with the selected clock source:

If the warning is shown infrequently, then the message can be safely ignored and the show can continue as planned.

Viz Mosart has a built-in safety mechanism which takes care of intermittent or lost external genlock and/or timecode signal (refer to section Genlock and Timecode Reliability in the topic Frame Accurate System Operations).

If the warning appears frequently or it is persistent, the genlock signal and/or timecode signal have become unreliable and must be fixed.

Genlock is not enabled

In the Story Recorder panel, this warning means the genlock has not be activated for Viz Mosart. Refer to topic Frame Accurate System Operations for details on how to activate Genlock mode.

Story Recorder can be used without having proper genlock setup and a timecode reader card installed on the Mosart Server machine, but only for testing. In this case, the time of the day will be used.

However, in order for Story Recorder to generate high quality final clip shows, frame accuracy is a requirement. 

Retake position no longer valid. Please set retake point

• This is a user error, described in the Viz Mosart User Guide, under topic Operation > Story Recorder Mode.

Timeline can not be paused while pre-rolling

• This is a user error, described in the Viz Mosart User Guide, under topic Operation > Story Recorder Mode.

Housekeeping

Viz Mosart automatically performs regular maintenance tasks to archive or delete working folders. For Story Recorder operations, the following are important:

• No management of local EDL folder (EDL local folder, typically set to C:\MMLogs\EDL) and EDL transcoder folder (EDL watch folder ).
  See Enabling the Story Recorder Log Adapter.
  Whilst these files are not large, they will require an occasional purging.

• Viz Mosart can perform some management of the clips generated during a Story Recorder session.

  

  • Intermediate recording files, prefixed with the string specified in the setting Recording Clip Name Prefix (default SRVizrt) can be routinely purged from the video server,
    after a time lapse defined in Recording Retention DaysStory Recorder Setup#RecordingRetentionDays.

  • When enabled, this task is run every time the service Mosart Server Log Service is (re)started .

  • Default value for the number of days to keep files on the video server, Recording Retention Days is 'keep forever'.