> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stagemic.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# OSC Dictionary

StageMic accepts OSC messages over **UDP** to select or advance the current scene.

The default destination is:

| Setting | Default |
| :- | :- |
| Address | `127.0.0.1` |
| UDP port | `9000` |

The address above applies when the controller runs on the same computer. For another computer, use StageMic’s reachable network address and configure its OSC interface accordingly.

## Message summary

| OSC address | Arguments | Action |
| :- | :- | :- |
| `/stagemic/scene/go/next` | None | Advance one scene. |
| `/stagemic/scene/{scene-id}` | None | Select a scene by its stable identifier. |
| `/stagemic/scene` | One integer | Select a scene by its position, starting at 1. |
| `/stagemic/scene` | One string containing a scene ID | Select a scene by its stable identifier. |

Replace `{scene-id}` with an actual identifier. Do not include the braces.

## Advance one scene

```text theme={null}
/stagemic/scene/go/next
```

Send without arguments.

* If no scene is selected, StageMic selects the first scene.
* Otherwise, it advances one scene in production order.
* At the final scene, it does not advance further.
* If the show contains no scenes, it cannot advance.

Each received message advances once. Sending the message twice advances twice where enough scenes remain.

## Select a scene by stable identifier

```text theme={null}
/stagemic/scene/{scene-id}
```

Send without arguments.

To obtain the exact message:

1. Select the required scene in StageMic.
2. Open **Network setup**.
3. Copy **Reference point for the current scene**.

Scene identifiers remain attached to scenes when renamed or reordered.

Deleting a scene and creating a replacement produces a different identifier. Use the message from the show file you intend to run.

### Alternative argument form

You can also send:

```text theme={null}
/stagemic/scene
```

with one OSC string argument containing the scene identifier.

Both forms select the scene directly.

## Select a scene by position

Send:

```text theme={null}
/stagemic/scene 3
```

Here, `/stagemic/scene` is the address and `3` is an OSC **integer** argument.

This selects the third scene in production order, regardless of its displayed name.

Scene numbering starts at **1**.

Reordering, inserting or removing scenes can change which scene a numeric message selects. Stable scene identifiers are preferable for programmed reference cues.

A string such as `"3"` is treated as a scene identifier, rather than converted to the third scene. Use an integer argument for positional selection.

## Scene names

Displayed scene names are not OSC identifiers.

For example, naming a scene `Opening` does not create an address of `/stagemic/scene/Opening`.

Copy the generated reference message from Network setup.

## Timing and bundles

StageMic accepts individual OSC messages and immediate OSC bundles.

Scheduled bundles with future timetags are not supported. Schedule the cue in your controller and send the message when it should take effect.

Messages within an immediate bundle are processed in order. Avoid placing duplicate next-scene messages in the same bundle.

## Errors

An unknown identifier, out-of-range scene number or invalid message does not select a new scene.

StageMic records OSC activity and errors in its network status information. It does not send an OSC acknowledgement or scene-status reply to the controller.

Check the current scene in StageMic or on a connected display when testing.

## Completion and alerts

OSC scene selection does not mark handovers completed or reset completion tracking.

If incomplete-handover alerts are enabled, an OSC change moving forward exactly one scene checks the scene being left. Jumps, backward moves, repeated selection and initial selection do not trigger that check.

## Transport and access

Send properly encoded OSC packets over UDP. Plain text sent to the UDP port is not an OSC message.

OSC control has no password or authentication. Restrict access through your chosen interface and trusted network.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.