FAQ

STAGE 2.0 adds support for Smart Audio & Mixing Engine (SAME). This includes both new Configuration workflows as well as new Operational Interfaces, such as Audio Pilot. In addition, STAGE 2.0 introduces support of NMOS devices and a new concept called Jobs.

Yes. It adds the support of SAME DSP Engine as well as NMOS Devices.

A device that STAGE does not discover, control or monitor, but that provides AV I/Os. A User can tell STAGE that a Virtual Device exist (such as a Microphone or a 5.1 speaker array) so that it can represented in various STAGE UI (ex. Audio Mixer UI). A Virtual Device is connected to a Hardware Device (Ex. NSA).

This is necessary so that STAGE knows where the Virtual devices are connected so they can be properly represented in various Operational UI (ex. Audio Mixer UI).

A hardware host that STAGE does not discover or control. An Unmanaged host provides ST2110 / AES67 signals, which a User can tell STAGE exist so that these signals coming from an Unmanaged host can be routed to Riedel products, such as SAME.

This is the process of linking an Hardware Device to a Virtual Device.

Yes. NMOS is used to communicate with Riedel NSA box. It is also used to communicate with 3rd party NMOS devices. For instance, NMOS can be used to route SAME signals to/from 3rd party NMOS receivers/senders.

A job is the overarching configuration of an entire Production.

A job is needed to define all the elements required for a Live Production event inside STAGE. Jobs are required when using SAME.

Jobs are required when using SAME. However, VSP does not use Jobs.

This refers to the process by which system resources (e.g. hardware devices) are chosen for a Job. Multiple adoptions can be created for the same job. This can provide additional flexibility to the user (e.g. ability to run a production from various studios).

Activating Job allows a User to indicate that he is starting the Production event. Upon activation of a Job, STAGE will reserve the system resources defined in the Job adoption (if not already in use) so that no one else can use them while the job is active.

Before activating a Job, the User is presented with a Job activation summary UI that shows him if all the resources he needs are avaiable. If some resources are missing (e.g. I/O devices such as NSA, Processing blocks coming from SAME Engine), the User will know exactly which resource is missing. User will have the option to activate the job even if not all resources are available.

From STAGE UI (see System Management -> License Management), it is possible to see the license usage (or consumption) of all license options installed on a STAGE instance, including VSP and SAME licenses.

Yes. STAGE supports licenses with a Start Date and End Date, which are therefore only valid for a specific duration. These types of licenses are available for SAME.

Please refer to STAGE User Guide (-> Default Ports) for a complete list of all network ports.

Please refer to STAGE User Guide (-> System Requirements) for a detailed list of hardware requirements.