> 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-plan/adding-3rd-party-speakers.md).

# Adding 3rd Party Speakers

In most real-world venues, third-party loudspeakers are part of the sound system design—typically used as fills or delays in areas where the main HOLOPLOT array coverage may be supplemented. HOLOPLOT Plan now allows you to incorporate these speakers directly into your project, simulate them, and route them through HOLOPLOT Processors.

### When to use third-party speakers

Use third-party speaker templates when:

* You need **front fills**, **under-balcony delays**, or **off-axis support** in your venue
* You're working in an existing venue that already has non-HOLOPLOT hardware
* You want to simulate and plan for the complete sound system, not just the HOLOPLOT array

By incorporating third-party speakers into HOLOPLOT Plan, you can now model full venue coverage more comprehensively, making informed design decisions that consider the entire acoustic environment.


---

# 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-plan/adding-3rd-party-speakers.md?ask=<question>&goal=<user_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.