> 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-response-window.md).

# OSC Response Window

Sometimes OSC messages respond back and other times OSC messages can be used to query information. In either of these cases Spikemark has the ability to receive these messages and display them. To access the response window in the menu bar click Show Control and then OSC Response...

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

This brings up the response dialog. In this dialog the Listening Port is the UDP port Spikemark will listen for messages on. It can be any integer and it must correspond to the port number of an OSC client sending messages. Spikemark only listens for OSC messages when this dialog is open and the Listen button is pressed.

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-3ffe675406516de00a066d106794409473c6e218%2Fimage2.png?alt=media)

When a OSC message is received it is added to the messages list on the left. To view the contents of the OSC message click it. There are several ways to decode the message and this can be changed by selecting either Text, JSON, or ByteArray in the Decode As dropdown.

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-b351a18503a3cf18d0fc22b5d49974300666dc2e%2Fimage4.png?alt=media)


---

# 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-response-window.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.