> 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/setup/live-settings.md).

# Stage 2 · Settings

Entering Settings starts the pipeline in preview mode (off-air): the sensors stream, but no OSC output is sent yet. Allow 5–15 seconds for the system to warm up — the view may appear empty for a moment. This stage lets you configure everything while viewing live sensor data, then select **GO LIVE** to broadcast.

Complete three sub-steps in order: **Set capture zones**, **Post processing**, and **OSC output**.

## Set capture zones

<figure><img src="/files/792hpcXoF1uTYX8idJdF" alt="Capture zones over the live point cloud"><figcaption><p>The two zones over the live scene: cyan (outer) and amber (inner).</p></figcaption></figure>

1. **Point cloud capture zone** *(cyan, outer)* — the volume used when **Source** is **zone**. Set the minimum and maximum values for each axis, or drag the box in the viewport. **all** sends the full fused cloud without this crop.
2. **Motion capture zone** *(amber, inner)* — the smaller volume used by the **human** source and motion-capture tracking. It must remain inside the cyan zone.
3. **Zone presets** — save the current layout under a name and reload it for the next show.

{% hint style="info" %}
If the two zones are exactly the same size, only one box is visible in the viewport. A note appears with a **Pad capture zone** button that expands the outer zone so both boxes can be seen and edited.
{% endhint %}

## Post processing

<figure><img src="/files/mflRem7a4HpFwX8GAcKB" alt="Post processing — orientation, background removal, voxelization, and smoothing"><figcaption><p>World orientation, background removal, voxelization, and motion smoothing.</p></figcaption></figure>

1. **World orientation** — rotate the stage (**Yaw** 0, 90, 180, or 270 degrees) or select **Mirror X** so that forward matches your content, then select **Apply**. It applies immediately; the capture zones turn with the stage, but the background must be learned again afterward.
2. **Background removal** — learns and removes static points from the **human** source and motion-capture input. It does not change **all** or **zone**. Select **Learn now** (or **Re-learn**) with the stage clear of people and moving objects — fixed set pieces that belong to the background can stay. The status shows the learning progress, then **learned**. This is required before you can go live.
3. **Point cloud voxelization** — downsample the point cloud to reduce the amount of transmitted data. Turn it on and set the **Voxel size**; the change applies immediately.
4. **Motion smoothing** — smooths the tracked motion. Drag the **Strength** slider (0–100%); the change applies immediately.

## OSC output

<figure><img src="/files/YZztgGeCvYhbsgbzyZAY" alt="OSC output — target, source, and mocap settings"><figcaption><p>The streaming destination and source, configured before you go live.</p></figcaption></figure>

1. **OSC output** — set the **Target IP**, **Target port**, and point-cloud **Source**, then select **Apply**. **Test connection** only checks that the address can be reached.
2. **Mocap on start** — set **Max tracked people (slots)**. The host's slot limit appears below it; the change applies on the next pipeline start or restart.

**Source: all** sends the full fused cloud, **zone** sends the cloud inside the cyan zone, and **human** sends the background-removed branch inside the amber zone. Skeleton data is a separate mocap output.

{% hint style="info" %}
Only a shape large enough to be a person is tracked. Small props — a ball, a stand, a case — stay in the point cloud and never take a tracked-people slot. For the same reason, a person standing very far from the sensors, or mostly hidden behind scenery, may not be picked up. Contact your MOVIN support team if that happens on your stage.
{% endhint %}

## Go live

<figure><img src="/files/EzpJ0kdoX1iwTgfmaoO3" alt="Go Live readiness panel"><figcaption><p>The readiness check verifies every requirement before broadcasting starts.</p></figcaption></figure>

Select **GO LIVE** in the top bar. A panel checks Connect sensors, Calibrate sensors, Set capture zones, Post processing, and OSC output. When it shows **READY**, select **GO LIVE** in the panel. Broadcasting starts and the workspace switches to **Live**.

{% hint style="warning" %}
If the panel shows **NOT READY**, it names the incomplete step. Most often this is background removal, which has not yet been learned — select **Learn now** first.
{% endhint %}

## After going live

The workspace switches to **Live**, primarily a monitoring screen for the running show. **Source** and **Recording** remain available there. See [Running a show](/movin-tracin-stage/running-a-show/running-a-show.md).

{% hint style="info" %}
Settings remains editable while you are live — return to it any time to adjust the zones, post-processing, or OSC output. Most changes apply immediately; see [What you can change while live](/movin-tracin-stage/running-a-show/running-a-show.md#what-you-can-change-while-live). Only Calibration is locked.
{% endhint %}


---

# 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/setup/live-settings.md?ask=<question>&goal=<endgoal>
```

`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.
