User guide

Viz Engine Administrator’s Guide

Preview Server 54000 Used when connecting over http using the REST

interface.

2.5.2 Multiplexing Ports

Ports Viz Engine

All other ports

Still Preview Port

MUX Isolated Port

MUX Shared Port

MUX Fixed Port

The multiplexer functionality is an integral part of Viz Engine. When using Viz Engine

a session management takes place internally, with one default session for the GUI

and internal/external commands, and additional sessions created on-demand for the

multiplexing ports or the preview port.

With multiplex ports, other than the MUX Still Preview port, the Viz Engine state is only

switched when a command is received, which means a new session is created; hence,

ten consecutive commands from a client will only result in one state switch on the first

command.

With the MUX Still Preview port the state is switched when a command is received and

immediately switched back to the main session such that on air rendering will not be

hindered in any way.

The MUX Fixed port is traditionally used by Viz Content Pilot 4’s Newsroom Component,

and is the same as the MUX Shared Port, except that allocated resources are never

cleared from memory. To avoid memory overload, it is recommended to clean up the

Viz Engine regularly when this port is used.

The MUX Shared Port is a shared port where all connections from one single host

shares one session. It is most often used by Viz Trio and the Newsroom Component to

display preview frames.

The MUX Isolated Port is an isolated port where all connections get their own session.

It is used, for example in an NLE setup, to deliver frames to the host NLE-system when

rendering or scrubbing video clips with graphics. Using this port will also suppress

bounding box commands.

Note: The MUX Isolated Port cannot be used by the Newsroom Component.

Note: All multiplexing ports are supported by all Viz Engine versions