> 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.md).
# Working with beams
Beams are the means to output sound from a Matrix Array. Each beam type has unique properties and are used for different types of content and use cases.
Beams are the means to output sound from a Matrix Array. Each beam type has unique properties and are used for different types of content and use cases.
An array can have up to a total of 13 beams per array: up to 5 Coverage Beams and up to 8 Parametric Beams or Virtual Sources.
Beam Type
No. Beams available per array
Coverage Beams
5
5
Parametric Beams Virtual Source (front and back)
8
8
To create a beam, you will need to first add an array. When an array is added, the contextual menu appears in the viewport where beams can be added.
Here, you will find the number of beam slots available for each beam type of the selected array. If slots are available, the beam that you add will be visible in the active preset panel.
If the beam slots are full, the beam will be added to the library. Think of this as an 'overflow' mechanism. Navigate to your selected array in the library to see the beam. If you want to use the beam in another preset, you can add it from the library. You can use this beam in the current active preset by swapping it out for another beam.
---
# 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.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.