OSC Reference: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
This reference applies to all different OS | This reference applies to all different OS. | ||
<div class="noprint"> | <div class="noprint"> | ||
| Line 16: | Line 16: | ||
* Allowed data formats including numeric, symbolic, and “blob” arguments | * Allowed data formats including numeric, symbolic, and “blob” arguments | ||
* Open-ended, dynamic, URL-style naming scheme for the receivers' address | * Open-ended, dynamic, URL-style naming scheme for the receivers' address | ||
== Contents == | == Contents == | ||
{| | {| | ||
Latest revision as of 21:13, 8 August 2026
This reference applies to all different OS.
This document describes the MXWendler (MXW) OSC Command Interface through an overview of the command structure and practical examples of integration with external controlling software.
What is OSC?
OSC or „Open Sound Control“ is a Network-based protocol that commonly utilizes the UDP transport mechanism. Originally developed as a successor of the MIDI control protocol, it used nowadays as a practical communication method between platforms.
OSC Features:
- Connectionless communication architecture
- Broadcast-type messages
- High resolution time tag
- Allowed data formats including numeric, symbolic, and “blob” arguments
- Open-ended, dynamic, URL-style naming scheme for the receivers' address
Contents
| Controlling MXW through OSC |
| MXW OSC command structure |
| OSC command reference |
| Troubleshooting |