Learn how to add and manage RAVENNA and AES67 audio streams. OS 2.3 brings significant updates to stream management, enabling the creation of Sender streams using HOLOPLOT Processor and improving monitoring features.
You must subscribe to streams before routing them to audio inputs. This is done through the Settings › Audio I/O › Receiver Streams section, or on the Routing › Audio Inputs page.
There are two methods for discovering and subscribing to streams. They are both available through the Add Stream button.
Automatic discovery: If the HOLOPLOT Controller is part of the same real-time audio network, we can automatically discover audio streams based on mDNS and SAP announcements.
Manual subscription: If no streams are discovered automatically, you can manually input an SDP (Stream Definition Protocol) generated by your audio device.
HOLOPLOT Audio Modules comply with ST 2110-30 stream formats, specifically under the following specifications:
Linear 24-bit PCM encoding (L24)
48 kHz sampling frequency (media clock)
We recommend using Level A for AES67 compliance among the three SMPTE Conformance Levels.
You can un-route audio inputs mapped to a stream or unsubscribe from streams using the contextual menu available in each stream. When you unsubscribe from a stream, its existing routings will be automatically deleted.
With this feature, you can configure a HOLOPLOT system to monitor and automatically switch Audio Modules between primary and backup stream sources using a pilot-tone detection or network package monitoring.
Click the Receiver stream's contextual menu and select Stream Settings.
Click Backup Stream and select the stream you want to add as a backup. Only Receiver streams with the same payload (including channel count) and that are not routed to any audio inputs can be assigned as backups.
Select a monitoring mode. There are two options for monitoring the stream's integrity:
Pilot-tone detection:
When the system detects an issue with the main Receiver stream and switches to the backup stream, the transition is nearly seamless for the modules and audio output. The detection interval is every half-second.
The subscribed streams table provides various details regarding stream failover:
Whether the stream has a backup stream or an analog input.
Which stream is currently active?
Status of the main and backup streams.
Main stream with backup stream (and Analog fallback) assigned
Single streams
Toggle Test Mode to check the integrity of the streams without executing the failover.
You must create sender streams before routing them from the Processor outputs. This is done through the Settings › Audio I/O › Sender Streams section, or on the Routing › Processor_Name page.
There are two methods for creating Sender streams. They are both available through the Add Stream button.
Using the Stream Assistant (recommended): Use the Stream Assistant for a quick and guided setup.
Manually creating Streams: If an advanced setup is preferred, you can manually define the Stream settings and their primary and secondary network interface ports.
After creating a Sender Stream, assign it to the project's Processor(s) to ensure the streams are created on the correct devices. You can do this via the Audio I/O or Routing by clicking the three-dot menu on the stream and choosing 'Assign Processor.' A dialog box will then appear, displaying available Processors in a drop-down menu for your selection. To unassign a Processor, use the same three-dot menu and select 'Unassign Processor'.
Network package monitoring: The controllers continuously monitor the RTP packages in the stream, and if a certain threshold of failed packages is exceeded, the stream is considered insufficient.
(Optional) Toggle Fallback to Analog Mode on. This functionality is available only in projects with Analog Presets and hardware that supports analog inputs.
A (AES67 compliant)
1-8 channels
Packet times of 1ms
B
1-8 Channels
Packet times of 0.125ms
C
1-64 Channels
Packet times of 0.125ms










