> 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/working-with-beams/routing-beams.md).

# Routing Beams

HOLOPLOT Plan uses routing matrices to define how signals flow through a system at different stages of the design process. These matrices allow you to control signal distribution, processing requirements, and relationships between beams.

There are three routing matrices in Plan:

* **Input → Beam Routing Matrix** – used to route inputs to beams and define which signals will feed which beams.
* **Delay Downmix Matrix** – used to route signals from main beams to fill and LF beams, with gain and delay applied at each crosspoint.
* **Processor Matrix** – used to define processor channel requirements when working with third-party speakers. This matrix ensures the correct processor channels are assigned before exporting to Control.

If routing is missing from any of the matrices, the preset will be marked **orange** in the top status bar and will not be ready for export, see [Saving & exporting](/holoplot-plan/saving-and-exporting.md#exporting-presets)


---

# 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/working-with-beams/routing-beams.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.