Viz Mosart Administrator Guide

Mosart EDL Setup

This output makes Viz Mosart write the edit decisions from a Story Recorder session to disk as JSON files. No external transcoder or renderer takes part: Viz Mosart records the program output on the video server, logs every on-air event with a frame-accurate timecode, and writes the resulting in and out points to a folder you configure.

Enable it alongside one of the other Story Recorder outputs. The Mosart EDL produces no clips of its own, so it never replaces the output that produces your media. Its main purpose is troubleshooting: it gives you, and Vizrt support, a readable record of what a session recorded. The same files can also feed a third-party system that cuts or catalogues the recording, or a converter that turns the timings into another EDL format, but that is not a finished workflow yet. If you are considering it, contact Vizrt to learn how the output works and to develop it further together.

This page covers the Mosart EDL half of step 19 of the Story Recorder Setup Checklist. Work through steps 1 to 18 first: they cover the license, the installation order, the frame accuracy setup, the show design, and the video server.

Story Recorder needs frame accuracy in production. You can configure and test this output without genlock, but the timings in the files will not be frame accurate: the in and out points no longer match the recording frame for frame. See steps 8 to 13 of the Setup Checklist.

What this workflow is for

The intent. Viz Mosart writes the Edit Decision List to disk as JSON. It produces timing information only: it renders no clip and it moves no media. The files tell you, item by item, which recording each part of the show is in and which frames it covers.

What you get. JSON files in a folder you configure. Each file names the recorded media, the point where that recording starts, and the frame range of every item that was recorded.

When to use it: troubleshooting. This is what the output is for today. Use it to check what a session actually recorded, or when Vizrt asks for the files while investigating a timing question. Enable it at the same time as the Mimir, TriCaster or Vantage output. It runs independently of them and does not interfere with them.

Third-party integrations. The files also carry what another system would need to cut, stitch or catalogue the recording itself. The most likely case is a converter of your own: read the JSON and write out the EDL or playlist format that your transcoder, editing system or MAM expects. This is not a finished workflow, and the format is still developing. Contact Vizrt before you build on it, so you learn how the output behaves today and your requirements can shape where it goes next.

Scope and limits

This output is still under development, and the format is not final. It carries no version number and no published schema, and it can change from one Viz Mosart release to the next. Use it for troubleshooting. Before any third-party system depends on these files, contact Vizrt, so that what you need is taken into account as the output develops.

Viz Mosart writes the files and does nothing more. It does not send them anywhere, it does not tell any system that a new file has appeared, and it does not delete them later. Whatever consumes the files has to look in the folder itself.
The files describe timings, not media. No clip is produced and nothing is rendered. The recording stays on the video server.
One file per item, per story or per show, depending on the output levels you select. The files go into Item\, Story\ and Show\ sub-folders of the folder you configure.
Show level files are written only when the operator presses Deliver in the Story Recorder tool window. A session that runs without a Deliver press produces no Show level file.
A pause and retake is reflected in the files: the discarded part of the show is removed, and the item recorded again carries a higher take number. Cut from the item entries rather than the story ones, because a story's own start and end timecodes still span the discarded material and the pause. And where a story was written to disk before the retake, its earlier file stays behind, so the newest file for a story is the valid one.
Graphics are only partly covered. Only overlay graphics appear, and their timings come from the clock rather than from genlock, so they are not frame accurate the way the item timings are. Fullscreen graphics appear as ordinary items, with nothing marking them as graphics. Graphics channel, type and description are not included.
Several things are not in the files at all: audio, transitions and transition types, item types, switcher crosspoints, accessories, control commands, and clip in and out points. A converter can only pass on what the files contain, so anything in this list has to come from elsewhere.
JSON only. This output never produces the Vantage .tsedl file. That format belongs to the show clip production workflow.

What you need

On top of the general Story Recorder setup, this output needs:

Component	Requirement
Output path	A local path or a network share for the JSON files.
Extra software	None. Viz Coder is not used, because this workflow produces no snippet clips.
Other Story Recorder output	Recommended. This output produces no media of its own, so enable it next to the Mimir, TriCaster or Vantage output that produces your clips.

For the validated combination of NRCS, recorder and transcoder, and the product versions, see Supported Configurations in Story Recorder Setup.

Settings

Open the Manus Settings menu and set Enable Story Recorder to true. The remaining Story Recorder settings sections then become available.

Save while Story Recorder is off, and restart the Mosart Logging Service after changing the Clip Outputs devices. See step 25 of the Setup Checklist.

EDL File Outputs > Mosart

Produces JSON-format EDL files for local inspection of a recorded session.

Setting	Default	Description
Output Level	Story	Mosart supports Item, Story, and Show level EDL output. Select one or more levels; a file is written at each level you select, into the matching sub-folder. If you clear the selection, no files are written.
EDL local folder	`C:\MMLogs\EDL`	Folder where JSON EDL files are written. Files are organized into `Item/`, `Story/`, and `Show/` sub-folders based on the selected output level. Can be a local path or a network share.

Output levels

The levels you select determine which files Viz Mosart writes, and which sub-folder they go to.

Level	Subfolder	What it produces
Item	`Item/`	One EDL per rundown item recorded during the session. The finest granularity available.
Story	`Story/`	One EDL per story in the rundown.
Show	`Show/`	One EDL per show, covering the whole session.

Selecting several levels writes a file at each of them, from the same session. An empty selection writes nothing.

Show level. Show level files are written only when the operator presses Deliver in the Story Recorder tool window. Disabling Story Recorder does not write a Show level file, so a session that runs without a Deliver press produces no Show level output, and the file cannot be created after the session ends.

Reading the frame ranges. The out point is the first frame after an item, not its last frame. The duration of an item is therefore its out point minus its in point, and items follow each other with no gap and no overlap.

Related settings

These settings are shared by all Story Recorder workflows and live on Story Recorder Setup:

Recordings Housekeeping and Related General Setting: the recording clip name prefix, the retention days, and Use local time.
Keyboard Shortcuts and Clip naming pattern of temporary recordings.

Viz Mosart does not clean up the EDL local folder. The JSON files are small, but they need occasional purging. Recorded clips on the video server are a different matter: they can be very large files, easily filling the disk space.

Procedure

Configure the video server recorder ports

See Configuring the Video Server in Story Recorder Setup. With TriCaster as recorder, also work through Preparing TriCaster on the same page.

Configure the Mosart EDL output

In the Manus Settings menu, enable Enable Story Recorder.
Under EDL File Outputs, open the Mosart section.
In Output Level, select the levels you need: Item, Story or Show. Selecting several writes a file at each of them. If you leave the selection empty, no files are written.
Set EDL local folder. Keep C:\MMLogs\EDL or choose another local path or network share. Grant the Mosart Logging Service account read and write permission on it. Viz Mosart creates a sub-folder for each level you selected.
Save the settings while Story Recorder is off. They take effect when the next session is enabled.

Verification

Switch Story Recorder on in the Viz Mosart UI. The session must start without errors. Otherwise, check Story Recorder Troubleshooting.
Load a rundown and check that the story items appear in the Story Recorder panel.
Check that the Story Recorder panel shows no genlock warning. Unreliable genlock or Genlock is not enabled means Viz Mosart fell back to the internal clock. The session still runs and the files are still written, but their timings are not frame accurate.
Check that the EDL local folder contains a sub-folder for each output level you selected, and none for the levels you did not select.
Run a short session, then confirm that JSON EDL files land in the sub-folder of every level you selected: one per item in Item/, one per story in Story/, one per show in Show/. At Show level, the operator must press Deliver when in Pause mode for a file to appear. A message such as Delivered to Mosart EDL (6 items, 4 stories, 1 show) confirms what was written.
If your setup uses pause and retake, retake an item and then confirm that the story file lists that item once, with its take number counted up, and not twice.
Open one of the JSON files and confirm that the timecodes match the recordings on the video server. A systematic offset points to a mismatch between Use local time and the AV Automation setting External Clock Is Local Time.

Operator instructions for switching on and running Story Recorder are in Working with Story Recorder.