> 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-messenger.md).

# OSC Messenger

A new OSC Messenger can be added in one of two ways. The first is from the menu bar at the top click Stagehand and then Add OSC Stagehand.

![](/files/-MhFRtAMkPkYbCwqi-e2)

The second way to add a OSC Messenger is to right click on the empty space in the Jog Workspace and click Add OSC Messenger.

![](/files/-MhFRtAG0eFTHaJjiB22)

Once an OSC Messenger has been added click it to bring up its three editable properties. Target Address, Port and Active. Target Address is the OSC Server address, Port is the UDP port the OSC Server is listening for commands on, and Active is whether or not the movements will be loaded and executed.

![](/files/-MhFRtADUbeWm7efcMSw)

## OSC Movement

Spikemark supports sending OSC UDP messages and the OSC movement is where all the parts of an OSC message are put together.

![](/files/-MiSb_Tfjri1fhO5ryKD)

### **Message Format**

An OSC message is made up of an address and any number of arguments where the arguments are any combination of strings, integers, and floats. This is represented in Spikemark as a comma separated list.

The first item in the list is the OSC address which always starts with a forward slash (/) and then the arguments. For example, the command for adjusting the faders for a QLab cue is “/cue/1/sliderLevel,1,0”. The OSC address is /cue/1/sliderLevel and the two arguments channel and decibel level are respectively 1 and 0.

### **Command Library**

The command library is a collection of xml files that have OSC messages already defined. This makes it quick and easy to add OSC messages. The command library can be expanded which is covered in the next section.

To use the command library click the + button on an OSC movement.

![](/files/-MhFRtAIONHEPNrKuCnH)

By default Spikemark tries to load the QLab command library but using the Browse button, any OSC command library can be opened. Then using the Commands Dropdown a command can be picked and its parameters and arguments will become editable.

![](/files/-MhFRtAJ1-gnCVP0z-O0)

Once all the values have been changed clicking the Insert button will close the OSC Library dialog and update the OSC movement.

![](/files/-MhFRtACxKYkA95mpwZm)

You can even [create your own OSC Library](/docs/spikemark/show-control/osc/osc-messenger/expanding-the-command-library.md) for commands that will be sent to different software other than QLab or Eos.


---

# 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/show-control/osc/osc-messenger.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.