> 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/troubleshooting/medialon-manager-config.md).

# Medialon Manager Configuration

Sending OSC from Medialon Manager to Spikemark is the special case where you have to manually do the [null padding](https://docs.creativeconners.com/docs/spikemark-6/show-control/osc/troubleshooting.md).

Medialon Manager has OSC Output Device, but the OSC Output Device adds in additional information into the command that Spikemark isn't expecting which causes Spikemark not to take the OSC action.

Do Not Use the OSC Output Device to send OSC commands to Spikemark. It will not work.

Instead, use a Medialon Low Level Communicator Device instead of an OSC Output Device.

Configure the Medialon Low Level Communicator Device as a UDP Output, and assign the port to match the listening port of Spikemark.

<figure><img src="https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-d48ad2dcaecb9c4d0e3a4d5513bdd5688c8bf7cb%2Fmedialon-manager-setup.png?alt=media" alt="Medialon Manager LLC Config"><figcaption></figcaption></figure>

Then setup your Output Command with the correct Spikemark IP Address and Listening Port, and use the above structure to format the command using 4-bye null padding.

<figure><img src="https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-3db6f720c3d142573d51d1d8c019da3fc462e9e7%2Fmedialon-manager-output-command.png?alt=media" alt="Medialon Manager Output Command"><figcaption></figcaption></figure>


---

# 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-6/show-control/osc/troubleshooting/medialon-manager-config.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.
