> For the complete documentation index, see [llms.txt](https://help.movin3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.movin3d.com/movin-tracin-stage/running-a-show/running-a-show.md).
# Running a show
After setup is complete, use the following sequence to run the show: open **Settings** (the preview starts), **GO LIVE**, monitor, and then **END LIVE**.
## Preview, then go live
Preview mode (off-air) starts the sensors streaming so you can see live data, while nothing is broadcast yet. There is no separate start button — entering **Settings** starts the preview automatically, unless the pipeline is already running. (Re-entering while it is running does nothing.)
Starting the pipeline locks Calibration (🔒). Allow 5–15 seconds for the system to warm up while the sensors begin streaming; the view may appear empty for a moment.
**GO LIVE** then starts broadcasting: it shows the readiness list, and confirming starts the OSC output right away and switches to the **Live** stage.
## The Live stage
Once you go live, the workspace switches to **Live** — a monitoring screen for the running show. **Source** and **Recording** remain available on this screen.
The Live stage while broadcasting.
The top bar shows **LIVE**, elapsed time, sensor status, tracked people, the OSC destination, and recording status. The center viewport remains a live visual reference. The numbered controls are:
1. **OSC output** — the active destination. The target and port are set back in Settings; **Source** can be changed here and applies immediately.
2. **Recording** — capture the show to a file (see below).
## If a sensor drops out mid-show
If a LiDAR stops sending during a show, the show keeps running on the remaining sensors — with reduced coverage where the lost sensor was looking.
* An alert appears in the viewport: *LiDAR 204 offline — running on 4 of 5*.
* The **Sensors** indicator in the top bar changes to the same fraction.
Check the sensor's power and network cable. If the sensor cannot be brought back right now, select **Acknowledge** on the alert — the warning goes quiet for the rest of the run, while the sensor list and the fraction keep showing the fact.
## What you can change while live
You can return to **Settings** at any time to adjust settings. What happens depends on the setting:
| Setting | When it applies |
| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Capture zones | Immediately for **zone** and **human**; **all** remains the full fused cloud |
| Background removal | Immediately for **human** and motion capture (learning needs the pipeline running); no effect on **all** or **zone** |
| Point cloud voxelization | Immediately |
| Motion smoothing | Immediately |
| Source (**all** / **zone** / **human**) | Immediately — full fused / cyan zone / amber motion branch with background removal |
| World orientation | On **Apply** — immediately, no restart. The zones turn with the stage; the background must be learned again |
| OSC Target IP or port | On the **Apply** button that appears next to the edited target — output pauses for a moment, and you stay on air |
| Max tracked people | On the next **Restart** |
| Calibration | Not while live — requires stopping the pipeline |
{% hint style="warning" %}
Calibration is locked while you are live. If a sensor is moved and you need to recalibrate, stop the pipeline first: select the locked Calibration stage (🔒) and confirm.
{% endhint %}
## Recording for diagnosis
If something appears wrong, record the issue so the MOVIN team can reproduce and diagnose it. In the Live stage, select **Recording → Record**, let it run while the problem is visible, then select **Stop**. **Open folder** opens the folder containing the saved recording. While recording, the **Rec** indicator in the top bar shows a running clock.
A recording is an MCAP (`.mcap`) file containing the raw point-cloud data from each sensor. It does not contain camera images or mocap skeleton data. It still contains movement and spatial data, so handle and share recordings according to your organization's privacy and data-retention policies.
## Ending the show
Select **END LIVE** in the top bar and confirm. OSC output stops immediately — the show target stops receiving — and you return to **Settings**. Tracking and the point cloud keep running, so you can go back on air right away with **GO LIVE**.
After the show, select **Stop pipeline** in the top bar — sensors, tracking, and OSC output all stop. It does not turn the machine off.
---
# 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, and the optional `goal` query parameter:
```
GET https://help.movin3d.com/movin-tracin-stage/running-a-show/running-a-show.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.