[1] Its disadvantages include inefficient coding of information, increased load on embedded processors,[2] and lack of standardized messages/interoperability.
OSC is a content format developed at CNMAT by Adrian Freed and Matt Wright comparable to XML, WDDX, or JSON.
OSC messages between gestural controllers are usually transmitted over serial endpoints of USB wrapped in the SLIP protocol.
[citation needed] OSC's main features, compared to MIDI, include:[1] There are dozens of OSC applications, including real-time sound and media processing environments, web interactivity tools, software synthesizers, programming languages and hardware devices.
[8] Address patterns form a hierarchical name space, reminiscent of a Unix filesystem path, or a URL, and refer to "Methods" inside the server, which are invoked with the attached arguments.
The core types supported are An example message is included in the spec (with null padding bytes represented by ␀): /oscillator/4/frequency␀,f␀␀, Followed by the 4-byte float32 representation of 440.0: 0x43dc0000.