> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/spikemark-6/show-control/osc/input-triggers/osc-input-messages.md).

# OSC Input Messages

There are two types of responses that Spikemark will send back status messages and data messages. When OSC responses are turned on status messages will be sent back to the sender at the address `/spikemark/reply` with a JSON string parameter as follows:

```json
{
    "Address": "invoking address",
    "Success": true or false,
    "Message": "additional information if needed",
    "Data": additional decimal data if needed 
}
```

Some commands send back data, these data messages get sent back to the sender at the address `/reply/{invoking address}` with the relevant data passed as arguments. For example if `/cue/1/playback/1/step/1/totaltime` was sent to Spikemark it would respond with `/reply/cue/1/playback/1/step/1/totaltime 12.89`

When an OSC message needs a string as part of its address like `/motor/{motor_name}/position` the string in Spikemark can not contain any of the following characters.

| Character | Name                 |
| --------- | -------------------- |
| #         | number sign          |
| \*        | asterisk             |
| ,         | comma                |
| /         | forward slash        |
| ?         | question mark        |
| \[        | open bracket         |
| ]         | close bracket        |
| {         | open curly bracket   |
| }         | closed curly bracket |

Additionally, spaces aren't allowed in OSC address so if your motor name has any spaces then in the OSC address replace them with and underscore(\_). As an example if in Spikemark you had a motor with a name of `Pushstick V2` and you wanted to get its position you would send the OSC message with the address `/motor/Pushstick_V2/position`


---

# 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://docs.creativeconners.com/docs/spikemark-6/show-control/osc/input-triggers/osc-input-messages.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.