> 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-matrix-arrays/acoustic-screens.md).

# Acoustic Screens

In many projects, loudspeaker arrays are integrated invisibly into the venue architecture — placed behind LED walls, projection surfaces, fabric, or custom-designed panels. These are referred to as **acoustic screens**, and they play a critical role in both the aesthetics and acoustic performance of a HOLOPLOT system.

#### What is an acoustic screen?

An acoustic screen is any physical surface that is placed directly in front of a HOLOPLOT array. Examples include:

* LED video walls
* Fabric coverings
* Acoustically transparent panels
* Custom venue-specific installations

While screens allow for clean visual integration, they can affect sound transmission depending on the material, thickness, and angle. Without compensation, this can lead to changes in frequency response and sound level across the beam.

#### Screen-aware beam optimization

HOLOPLOT Plan takes screens into account during the **beam optimization process**. Once a screen is placed in the design, every beam emitted from the array behind it is automatically optimized with compensation tailored to that screen’s acoustic characteristics.

Each screen type has its own defined effect on sound transmission. These effects are measured and accounted for by the optimization algorithms, ensuring that **system performance remains consistent and reliable**, even when arrays are fully concealed.

No manual EQing or filter adjustment is required — the compensation is built into the beam’s design itself.

#### How to use acoustic screens in Plan

Available from Plan 2.3 and onwards.

**Add a screen to an array**

Screens are added directly to arrays in your HOLOPLOT Plan project. This tells the optimization engine that the array is placed behind a physical screen and that compensation should be applied automatically to all beams from that array.

**Select a screen type**

In order for screens to appear in your HOLOPLOT Plan project, their corresponding `.json` file must be loaded into Plan. Custom screens are loaded from the user folder.

#### Import a custom screen

From Plan 2.6.4, you can import custom screens from within Plan:

1. In the toolbar, select **File > Import Acoustic Screens**.
2. Select your screen’s `.json` file. You can import one file at a time.

The imported screen appears in the screen selection menu straight away. You don’t need to restart Plan.


---

# 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-matrix-arrays/acoustic-screens.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.
