> 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/tuning-beams-in-plan.md).

# Tuning Beams in Plan

**System Designer EQs** offer powerful EQ capabilities directly within the tuning workflow. EQing in Plan help users create beams that sound good before stepping on site.

#### Adding EQ

You can now add **beam-specific EQs** from within the *Tuning* tab of Plan. Simply click the EQ icon to open the EQ panel, where you can configure up to **6 bands per beam**.

Each EQ band gives you full control over:

* **Type** – such as bell, high pass, low shelf, etc.
* **Frequency**
* **Gain**
* **Q factor**

You can choose from predefined filter shapes or tailor the parameters to meet your specific acoustic goals. This gives System Designers more control over the tonal balance of each beam, allowing you to address artistic requirements, environmental challenges, or project-specific tuning preferences early in the design process.

#### Export-ready via IFIR

Behind the scenes, each beam's EQ configuration is distilled into a single **IFIR (Interpolated Finite Impulse Response)** filter when the project is exported to HOLOPLOT Control.

#### Visual feedback in simulation

Changes made via System Designer EQs are reflected in Plan’s simulation results. This gives you immediate visual confirmation of how your EQ choices impact system performance.


---

# 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/tuning-beams-in-plan.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.