> 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/readme.md).

# MOVIN TRACIN Stage

Get started with MOVIN TRACIN for Stage: multi-performer markerless tracking for live shows, with real-time data streams for stage visuals.

MOVIN TRACIN Stage scans the people on your stage with LiDAR sensors and turns them into a live point cloud and motion data. Both stream over OSC to VJ software, Unreal Engine, lighting consoles, and other show software.

**First installation** — start at [What you need](/movin-tracin-stage/install-the-hardware/whats-included.md) and follow the pages in order. **Already set up** — use the [show checklist](/movin-tracin-stage/reference/quick-reference.md).

The software comes pre-installed on the server, and everything is operated from the workspace screen. Update it only when your MOVIN support team asks you to.

## The flow

Set up the system once, then run the show. The workspace guides you through three stages in order.

| Stage               | What you do                                                                                                        |
| ------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **1 · Calibration** | Connect the sensors and align them into one shared 3D scene.                                                       |
| **2 · Settings**    | Set the tracking zones, configure post-processing, and specify the OSC destination while viewing live sensor data. |
| **3 · Live**        | Go on air, then monitor the show while it broadcasts.                                                              |

## First installation: follow these pages in order

1. [What you need](/movin-tracin-stage/install-the-hardware/whats-included.md) — check the kit and prepare peripherals.
2. [Mounting the sensors](/movin-tracin-stage/install-the-hardware/sensor-mounting.md) — install and cable the sensors.
3. [Connect and power on](/movin-tracin-stage/install-the-hardware/server-back.md) — connect the monitor and open the workspace.
4. [The workspace screen](/movin-tracin-stage/setup/the-workspace.md) — find the next action.
5. [Calibration](/movin-tracin-stage/setup/calibration.md) — align the sensors and verify the floor and stage direction.
6. [Settings](/movin-tracin-stage/setup/live-settings.md) — set the zones, learn the empty stage, and configure output.
7. [Stage 3 · Live](/movin-tracin-stage/running-a-show/running-a-show.md) — go live and check the first output.

If a step fails, use [Troubleshooting](/movin-tracin-stage/reference/troubleshooting.md).


---

# 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.movin3d.com/movin-tracin-stage/readme.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.