# Workflows Overview

This section provides end-to-end workflow guides for the most common Exaplay 3 use cases. Each guide walks through the full process from project creation to show delivery.

## Workflow Guides

| Guide                                                                        | Best for                                                                                |
| ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| [Live Events & Concerts](/v3/workflows/live-events.md)                       | Music concerts, festivals, touring shows — cue-driven with real-time flexibility        |
| [Theatre & Performing Arts](/v3/workflows/theatre.md)                        | Scripted shows with precise timecode, cuelist workflows, and operator control           |
| [Permanent Installations](/v3/workflows/installations.md)                    | Digital signage, museums, lobbies — unattended, scheduler-driven, auto-heal             |
| [Museum Installation with User Panels](/v3/workflows/museum-installation.md) | Interactive museum exhibits with visitor touchscreen kiosks and staff control           |
| [Corporate Events & Conferences](/v3/workflows/corporate.md)                 | Keynotes, product launches — presenter-paced slides and video playback                  |
| [Projection Mapping](/v3/workflows/projection-mapping-workflow.md)           | Multi-projector architectural and stage mapping setup from scratch                      |
| [Dome Projection](/v3/workflows/dome-projection.md)                          | Full-dome and immersive dome setups — fisheye single projector or multi-projector ring  |
| [Attraction Ride Control](/v3/workflows/attraction-ride.md)                  | Dark rides and themed experiences — timecode slave, Data Tracks, DMX/OSC/UDP automation |
| [External Show Control](/v3/workflows/show-control.md)                       | Connecting to ETC Eos, Qlab, Medialon, Crestron — OSC, REST, ArtNet, LTC in/out         |

## Choosing the Right Workflow

```
Is timing scripted and fixed?
  ├── YES → Is a lighting console the master clock?
  │           ├── YES → Show Control (timecode slave) or Theatre workflow
  │           └── NO  → Theatre or Corporate workflow
  └── NO  → Is it a live music / performance?
                ├── YES → Live Events workflow
                └── NO  → Is it running unattended 24/7?
                              ├── YES → Permanent Installations or Museum Installation
                              └── NO  → Is it a dome or special screen?
                                            ├── YES → Dome Projection workflow
                                            └── NO  → Corporate or Live Events

Is it a ride or attraction?
  └── Attraction Ride workflow

Need to integrate with show control hardware/software?
  └── External Show Control workflow
```

## Common Principles

Regardless of workflow, these Exaplay practices apply universally:

1. **Save early and often** — `Ctrl+S` saves the `.vpp` project file.
2. **Use HAP or HAP Q** for 4K and above — GPU decoding avoids CPU bottlenecks.
3. **Test on the show system** — preview on the actual output hardware before the event.
4. **Label everything** — give screens, cues, tracks, and compositions descriptive names.
5. **Use the Operator Control view** (`/control`) for running shows, not the Editor.
6. **Enable Auto-Heal** for any unattended or touring deployment.


---

# Agent Instructions: 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://docs.exaplay.one/v3/workflows/index.md?ask=<question>
```

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.