> 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-presets/creating-a-preset.md). # Creating a preset To create a preset, click the **Presets** button in the header and click the **+** icon. The newly added preset will then be displayed in the Active Preset panel. The **Active** label will also be shown next to the preset in the Preset Panel.

#### Adding beams to presets To add a beam to a preset, you must first add an array using the **Create Array**

option in the toolbar. Next, create a beam using the the **Add Beam** menu. The only entities that are relevant to a preset are beams. This is why, when you create an array, this does not immediately appear in the Active Preset panel and is only shown in the Library. When a beam is assigned to an array, both the array and beam will be shown in the Active Preset panel. (Arrays are shown in the Active Preset panel in order to show which array the beam is coming from.) #### Understanding beam slot limits The number of beams that can be added to an array within a preset is limited to up to 5 Coverage Beams and 8 Parametric Beams and Virtual Sources. The remaining slots are displayed in the floating **Add Beam** menu. If all the slots in the array are full, when you add a beam it will no longer appear in the Active Preset panel, and will only be added to the Library. Select an array to view all of the beams added in the properties panel. In the Beams List, the active label is added to all of the beams currently being used in the active preset layer. This functionality enables you to add an unlimited number of beams to an array, and select the ones you would like to play by adding them to the active preset.

#### Adding beams from the library to the preset If slots are available, beams can be added from the Library to any of the preset layers you have created. The layer you are currently working in in the active preset will be marked with the **Active** label. To add a beam from the library, navigate to the beam and right click, then select **Add to Layer**. The beam will be added to the layer, and the array the beam belongs to will also be displayed if it's not already shown. You can also add the beam to any preset layer that exists in your project using the **right click** functionality in the Library.

{% hint style="info" %} More information on working with presets in the Working with Preset Layers section. {% endhint %} #### Checking preset status The preset status icon at the top of the viewport shows whether the active preset is ready to export. It's green when the preset is ready to export and orange when it isn't. Click the icon to open the Preset status dialog. It lists what still needs attention, grouped into four categories: 1. **Input-Beam Routing:** some beams have no input connected. Create the connection in the Input to Beam Routing Matrix. 2. **Beam Variants:** the preset has no beams, or its beams haven't been optimized. 3. **Processor:** the project contains third-party speakers, but no processor has been created. 4. **Processor Output Routing:** the processor outputs aren't routed. Create the routing connections in the processor matrix. See Routing through HOLOPLOT processors. --- # 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-presets/creating-a-preset.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.