HOLOPLOT OS
HOLOPLOT OS 2.0 is the intelligent software engine for any HOLOPLOT system. It coordinates Audio Modules to work together, creating Matrix Array systems of any size, and is enabled by both HOLOPLOT Plan and HOLOPLOT Control. This integration ensures a seamless process from planning to implementation, streamlining your tasks and enhancing overall efficiency.
Key concepts
The following chart provides an overview of key concepts in HOLOPLOT OS. As you will see in more detail in the next section, some of these concepts are defined within HOLOPLOT Plan during the system design phase, while others are defined in HOLOPLOT Control during the operational stage.
System
A system is the overall encompassing entity that holds all the information for operating a HOLOPLOT sound system. It is associated with HOLOPLOT Controller(s). HOLOPLOT Audio Modules connect via network to a single system at a time. A system has an operational state, settings, and projects.
Operational state
As the name suggests, this reflects the system's current operational status, including the active project, system gain, and mute statuses.
Learn more at Operating the system
Settings
Those settings are shared throughout the system. For example, the chosen audio over IP standard – Dante or Ravenna, available network audio streams, and network settings.
Learn more at Configuring the system
Projects
Projects contain most of the information on how Audio Modules should behave. We will delve into more detail in the next section.
Project components
The structure of a project significantly impacts both the system design and system operation stages. To illustrate this, we will examine a fictional and simplified system design of a concert venue.
A project has:
Arrays and Audio Modules
Physical representation of HOLOPLOT Audio Modules. Multiple Audio Modules are grouped into arrays.
Learn more at Arrays and modules and Device health
Beams
Learn more at Working with beams
At this level, the basic properties of beams, including beam type, optimization parameters, Parametric Beam parameters, and connection to Audio Modules and arrays are defined.
In the example above, we have 05 distinct beams. If we examine left coverage, it would be a Coverage Beam that is connected to the left array.
Learn more at Working with beams and Tuning beams
Audio inputs
These are the interfaces between the Dante or Ravenna channels and streams to the beams. Each beam can have different audio input mappings based on the preset layer.
In the example above, we have 03 audio inputs that reflect how the signal will flow into the system.
Environmental conditions
Those are defined and used for the optimization of beams. This is combined at the preset layer level.
Preset layers
Preset layers serve as the foundational elements of a preset, grouping together beams that function in unison. This layer also handles the mapping of beams to audio inputs, as well as EQ, gain, and delay alignments and is associated with environmental conditions.
A Beam's tuning is linked to the Preset Layer and environmental conditions. This means each Beam will have different Gain, Delay, and EQ values for each associated Preset Layer and Environmental Condition.
Main system
The main system preset layer in the above project consists of 03 beams connected to two audio inputs and two environmental conditions. The front fill beam receives its audio signal from both the left (01) and right (02) inputs.
Bar downmix
With this preset layer, we can independently activate a different set of beams to receive a downmix from the left (01) and right (02) inputs.
Bar independent
This preset layer takes the same beam as the previous one but assigns it to a different audio input. It can be used to send independent audio.
Balcony downmix
This preset layer exemplifies an optional venue occupancy. Perhaps the under-balconies are not used in some concerts.
Learn more at Routing audio and streams
Presets
Presets are groups of preset layers that form a functional system state that users can switch during operation. Let's look at some of the examples. We have four presets on the project:
Full system: All beams are engaged
Main system w/o under balcony: All beams without the under balcony
Main system & independent bar: The main system operates independently from the bar
Main system w/o under balcony & independent bar: Main system without under balcony, and bar operating independently
From an overview, they are presented like this:
When active in the system, this is a more accurate representation of what they are doing:
This approach simplifies operations for a front-of-house or system technician. Only two iudio Inputs (left and right) are needed to drive the entire system. A HOLOPLOT system handles EQ, gain, and delay settings.
Another example with the main system & independent bar preset:
The preset consists of 03 preset layers, with one key difference from the previous example: the "bar downmix" and "bar" in this one. The main distinction between the two presets is that the "bar coverage" beam now has an independent audio input (bar).
HOLOPLOT Plan checks the total number of available and used beam slots per Audio Module at two stages: first on the preset layer and then at the preset level.
Preset layers and presets are considered valid only if the count of beams per array does not exceed the specified limits. In the case of a preset, all beams in the assigned preset layers are considered.
Learn more at Working with presets and Changing a preset
Last updated
