> 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/show-control/osc/osc-input-tirgger.md).

# OSC Input Trigger

OSC Input triggers allow you to control Spikemark from some other software.

{% hint style="danger" %}
It can be dangerous to trigger motion automatically, the other computer won't be able to know if there is a person in the way. We **strongly encourage** the use of [hold to run](/docs/showstopper/legacy/showstopper-consolette/connecting-the-consolette-to-spikemark.md).
{% endhint %}

## Configuration

To open the OSC Input configuration window from the **Show Control** menu select **OSC Input Trigger...**

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-b2244f771d35abe773a61c9ad89faa0ab46b0076%2FOSC%20Input%20trigger%20show%20control.png?alt=media)

### Options

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-9a9105799d15c32657dde921ef16e5ecb9d4f16c%2FOSC%20input%20trigger%20configuration.png?alt=media)

**1. Listen Port -** The port that Spikemark will start listening on for incoming OSC messages.

**2. Respond Port -** The port that Spikemark sends response and data messages back to.

**3. Send Status Messages -** Toggle on or off Spikemark's response messages.

**4. Is Enabled -** Indicates whether or not Spikemark is listening for OSC messages.

**5. Disable -** Stop listening for OSC messages.

**6. Enable -** Start listening for OSC messages


---

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