> For the complete documentation index, see [llms.txt](https://help.depence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.depence.com/depence-show-and-animation/depence-programmer/depence-panorama-alignment.md).

# Panorama Alignment

The Panorama Alignment defines how the selected fixtures will be arranged for Effects, Delays, or Fanning. A panorama in Depence is represented by a single percentage value stored on the selected fixture. Once you select e.g. 10 fixtures and align them from left to right (), the first fixture will have a panorama of 0%, the 5th fixture 50%, and the last fixture 100%. This panorama value will be later on multiplied with e.g. an effect phase or delays.

![](https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/GlW9Awaav1OxlUqaJepm/245071889.png)

Five different alignments are possible:

| \| | No Arrangement                 |
| -- | ------------------------------ |
| \\ | Aligns from left to right.     |
| /  | Aligns from right to left.     |
| >  | Aligns from outside to middle. |
| <  | Aligns from middle to outside. |
| X  | Aligns in a cross form.        |

The **|** will reset the alignment to 0%. Furthermore, the Alignment supports sorting options called Wings and Blocks. Wings are a multiplier factor on the Panorama and Blocks will repeat the same panorama for the given amount.

More advanced alignments can be created by using the Graphical Panorama Arranger.


---

# 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://help.depence.com/depence-show-and-animation/depence-programmer/depence-panorama-alignment.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.