> For the complete documentation index, see [llms.txt](https://dorreal-art.gitbook.io/dorreal_art_docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dorreal-art.gitbook.io/dorreal_art_docs/documentation/explore/core-concepts.md). # Core Concepts ### It All Starts With Beat Timing Echoluma runs on a steady pulse defined by **BPM (Beats Per Minute)**. Every change in the system listens to that pulse. * A beat is a unit of time * A Step Pattern is a collection of beats * A light show is a structure built on those patterns

> **Echoluma Insight:**\ > **If timing feels right, everything feels right.** ### The System Thinks in Steps Echoluma doesn’t animate lights by repeating the same pattern and a few parameters.\ It thinks in **Step Sequences**. Each step is a moment in time that stores its own specific pattern, intensity, visual identity, motion and effects. A Step Sequence is simply: > Step 0→ Step 1→ Step 2→ Loop This creates structure, predictability, and natural feeling rhythm. ### Each Step Is Built in Layers A step is not a single action.\ It’s a stack of behaviors working together. Each step contains five core layers: 1. Pattern → When to activate a beat? Controls active and inactive beats 2. Envelope → How does the intensity behave? Controls how intensity evolves over time. 3. Light Look → What does this step look like? Defines color, brightness, and visual identity. 4. Movement → What is the motion throughout the step? Controls spatial behavior. 5. Light FX → What does the shape of light looks like? Adds variations through strobe and masking. > **Echoluma Insight:**\ > **Strong results come from combining simple layers, not overdriving one.** ### Step Sequences Loop As A Whole Echoluma is designed around seamless repetition. After the last step, the system can return to the first. **This creates:** * Continuous light shows * Predictable timing * Seamless rhythm But inside that loop, variation can exist, making the loop seamless. ### One Controller, Many Lights The controller doesn’t just affect one light. It can control **multiple lights at once with order**, applying the same logic across them and making offsets predictable. **This allows:** * Build synchronized rigs * Create patterns across space * Scale complexity without chaos ### Lights Aim Through Fixtures Lights are **aimed through a structured system**. Echoluma uses fixture style rotation built on three axes: * **Pan → Where does the light turn horizontally?**\ Controls left and right rotation * **Tilt → Where does the light point vertically?**\ Controls up and down aiming * **Roll → How is the light oriented around itself?**\ Controls axial rotation These axes work together to define where the light is pointing. Fixtures can use custom meshes, or be left empty.\ In both cases, the rotation system continues to function.

### From Simple to Complex At its core, Echoluma is simple: * A pulse (BPM) * A variable set (Steps) But these combine into complex behavior. Small changes create big differences. ### View the Full Documentation {% content-ref url="/pages/eVKSvw7B3r3bH4x5HjkV" %} [Documentation](/dorreal_art_docs/documentation/documentation.md) {% endcontent-ref %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://dorreal-art.gitbook.io/dorreal_art_docs/documentation/explore/core-concepts.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.