> 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/auto-gain-and-delay-alignment/gain-alignment.md).
# Gain alignment
### Gain Alignment
The objective of gain alignment is to ensure consistent sound pressure levels across the entire audience, regardless of whether coverage comes from main or fill function groups. The algorithm works by:
1. Making each beam in each function group equally loud across its respective target area.
2. Summing the levels of each beam within function groups.
3. Matching the summed levels of fill and LFE function groups with the main groups.
The alignment uses the following SPL frequency ranges:
* Main and Fill groups: average SPL between 350 Hz and 3000 Hz
* LFE groups: average SPL between 45 Hz and 90 Hz
#### EQ and Gain Alignment
EQ settings are taken into account during gain alignment. If you change your EQ settings after running alignment, you should re-run gain alignment to ensure the results remain accurate.
You can also run gain alignment without EQ active. Note that gain alignment is independent from the coverage beam target curve — the target curve does not influence the gain values calculated by the algorithm.
#### Headroom
The power headroom indicator shows the available headroom across the entire system. Exceeding available power headroom increases the risk of system clipping. If your headroom is exceeded after alignment, press the **Normalize** button to reduce levels and restore 0 dB power headroom.
---
# 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/auto-gain-and-delay-alignment/gain-alignment.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.
