Known Limitations

A Bug in the User Interface of STAGE prevents the user from filtering for the "Unassigned Location". When the "Unassigned Location" is selected in the filter section, the result in the Event List will not be updated. Filter for the name of the Host instead or move Hosts to a different Location.

When the network interfaces of an NMOS Host in STAGE are assigned to at least two Network Scopes that have are marked as Main and Redundant, STAGE will only use senders and receivers on the Host that have redundant network interface bindings. Make sure to correctly configure NMOS Senders and Receivers if 2022-7 redundancy is required.

In some circumstances, a user may be presented with a blank screen instead of a Login page. This can be resolved by refreshing the browser window (pressing F5 or clicking the refresh button). This can happen in cases where a user is logged in via an external Identity Provider and changes are done to the user in the Identity Provider system while the user is logged in. After a manual logout or a session timeout, the user will be navigated back to the login screen, which in some cases can appear empty.

When connecting to large Active Directory instances with 1000+ users, the initial synchronization process might take longer than indicated in the UI. On first synchronization, allow a few minutes for the process to complete.

When loading a different Adoption in a Job while the Job is active, the changes are not applied immediately. To apply the changes, load the Adoption before activating the Job or deactivate and activate the Job after loading a different Adoption.

In some cases, when editing the Location structure, Locations can get duplicated. This occurs more often when moving locations that are already part of a parent Location to another parent Location. To avoid duplicate Locations, consider creating a new Location in the desired position, move Hosts and Devices to this new Location and then delete the previous Location.

When activating a new sender on Job Activation or Job Configuration changes, STAGE will temporarily consume a new address from the multicast address ranges configured in the assigned network scope of the interface, even if the sender is already configured with a valid multicast address. This can lead to an exhaustion of the multicast address pool if the size of the pool does not provide enough headroom. When using a custom configuration for the multicast address ranges on a network scope, make sure the number of addresses is at least twice the number of active senders across all jobs in STAGE.

When a Host is unregistered, while still having senders that are using multicast addresses from the configured ranges of the assigned network scopes, these addresses are only released on the next STAGE reboot. This can lead to an exhaustion of the multicast address pool if the ranges are very small and large hosts are registered and unregistered multiple times. When using a custom configuration for the multicast address ranges on a network scope, make sure the number of addresses is sufficient.

If a volume evaluation fails due to PCM overload, subsequent evaluations may also fail. If this happens, restart the engine and reevaluate the volumes manually.

No Audio when remapping virtual Device to the same Audio Producer again.

When closing the Audio Pilot, the adopted Monitoring DSP-Process and associated PROCs do net get freed-up. To release these resources, open the Audio Pilot again, select "No Audio".

When adding Shuffler Super Tools to a Job, their UIs are not selectable to be displayed and manged in Audio Pilot. Channel alignment can be configured by selecting them in the Job's "Resource Configuration" tab.

The Reply key allows talk to conference, even if it is configured as listen-only.

The VSP does not show or indicate that someone is already talking to the IFB-output.