Studio

The template for a typical studio camera is based on the CAMERA type. The example below defines a standard camera 1 variant. An entry named CAM 1 in the video setup is selected at the PP bus cross point. Transition duration is 0 frames (hard cut) and E-mem recall is disabled. There is only one studio microphone, which fader is called "A Mic 1" in this template. Audio level is set to 0 dB, and the input device is a microphone. The input device type is important for the handling of audio in an ad lib sequence of full camera, DVE and full external source.

For our standard camera 2 variant, the only difference in the above setup is the PP bus cross point which is called CAM 2.

Video Clip with Full Sound

As crosspoint on the vision mixer, we use a source called S_RIP, which means Viz Mosart uses the A/B roll and roll between the sources defined in the AV setup as videoserverA and videoserverB. We chose RIP_C1 as the audio source, but as long as A/B roll is enabled, any source defined as Video server follows the video source. The default transition is a three frame mix. The video channel control is also enabled and controls the clip. The server channel is automatically assigned within the automation.

Voice-over

In this example, the variant VO is defined. Notice the difference from the two last examples and the two fader setups. A Mic 1 is microphone input type and RIP_C1 is video server type.

A second sound level can be set for each fader by using the SHIFT key over the fader to set the second level. This second sound level for all faders is used as the start level for the voice over sound bite type. The same special variant logic for video clip with full sound applies for the voice-over type.

Live External Source

Live external source variants are typically defined by their corresponding vision and audio mixer inputs. In the example below, we define variant 1 as source MW 1 on both PP bus cross point and audio fader.

Additional variants 2 to 9 would typically use MW 2 to MW 9 as sources for both video and audio.

DVE

The example below describes four setup steps necessary to create a template that recalls a predefined E-mem (emem number 10) defining a split screen DVE on M/E 1 on the vision mixer.

Full Screen Graphics

The graphics controller in the Template Editor is vendor-specific, due to the lack of a generic control API. As a general feature, it can control multiple graphic engines. A typical controlled cluster could for example be, one for full screen graphics, one for studio wall graphics and additionally, an overlay CG engine. For DVE effects, this can be a fixed element, while for telephone graphics or maps the element name and data are provided in the NCS story.

The controller's task is to cue graphics when taken to preview and run them when taken to program.

Accessory Templates

In this example you create an accessory template for driving content to a video wall driven by the Template Router feature in Viz Mosart. this feature merges new template-based instructions onto an existing one, enabling, as in this example, an asset to be diverted to the video wall. You need a separate accessory template for each wall that will be controlled. The accessory template can contain settings for cross points, video server port, graphics engine and aux.

Switcher Plugin

These are advanced configurations to a standard switcher where functionality is extended. The example in this section refers to extending Viz Engine functionality.

A Switcher plugin option is available in the list of devices to be enabled on the template.

The Switcher plugin view introduces two new configurable features, top scenes and presets.

Static values can be specified directly on the template. Newsroom tags can also be configured, enabling control from within the NRCS.