> For the complete documentation index, see [llms.txt](https://docs.holoplot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holoplot.com/holoplot-control/configuring-the-system/setting-up-holoplot-processors.md).
# Setting up HOLOPLOT Processors
This page guides on configuring HOLOPLOT Processors to integrate third-party speakers with a HOLOPLOT system.
### Assigning devices
To set up third-party speakers with HOLOPLOT Control, the Processors in the System Design must be assigned to a physical device. This involves matching the Processor defined in the System Design tool with the actual HOLOPLOT Processor device at the venue. Assigning a device to the Processor enables the controller to load beam configurations to the Processor outputs correctly.
1. Assigning a device to a Processor can be done either by navigating to **Settings** › **Processors** or from the **Device List** › **Processors**. Click the three-dot menu next to the Processor name and select **Assign Devices**. A dialog window displays the detected Processors in the drop-downs for Primary and Backup devices.
2. If needed, a backup device can also be assigned following the same step mentioned above.
Assigning devices to Processor in the Project
Device List - Main and backup devices assigned
### Failover mechanisms
The HOLOPLOT Processor will react accordingly to device failover scenarios reported by the management platform running on-site, such as a LAWO Home instance. That means that the HOLOPLOT Processor will switch from Main to Backup streams in the event of upstream device failure.
When a Backup device is assigned, both devices receive identical configuration settings, but only one actively streams audio at any given time. In the event of a device failure, the HOLOPLOT OS/Controllers trigger a device failover, replacing the active device with the backup one.
You can also perform a manual failover to switch devices. Click the three-dot menu next to the Processor name and choose 'Force failover.' The failover status indicators will update to reflect the change.
Manual failover
{% hint style="info" %}
From HOLOPLOT OS 2.6.3, automatic failover can switch in either direction. Failover occurs when a healthy Processor is available to switch to and the active Processor is unhealthy, stops streaming audio, or stops responding past the failover timeout.
{% endhint %}
***
### Third-party speaker delay compensation
The HOLOPLOT Processor and HOLOPLOT OS facilitate compensation for diverse network and processing latencies. This is accomplished through the manual adjustment of delay compensation, which allows users to synchronize HOLOPLOT Audio Modules with HOLOPLOT Processors.
Go to **Settings** › **Processors** and define in milliseconds (ms) the desired delay compensation value.
Settings – Third-party speaker delay compensation
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.holoplot.com/holoplot-control/configuring-the-system/setting-up-holoplot-processors.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
