GitHub

This is a lisp implementation of the Open Sound Control protocol (or more accurately “data transport specification” or “encoding”). The code should be close to ANSI standard common lisp and provides self contained code for encoding and decoding of OSC data, messages, and bundles. Since OSC describes a transport independent encoding (and does not specify a transport layer) messages can be send using TCP, UDP or other network protocols (e.g. RFC 2549). It seems UDP is more common amongst programmes that communicate using OSC and. the osc-examples.lisp file contains a few simple examples of how to send and receive OSC via UDP. The examples are reasonably compatible with the packets send from/to max-msp, pd, supercollider and liblo. more details about OSC can be found at https://OpenSoundControl.org

The current version of this code is available from github

git clone https://github.com/zzkt/osc

or via quicklisp.. .

(ql:quickload "osc")

or guix

guix install cl-osc

Testing

The file osc-test.lisp contains a test suite which should cover as much as possible of the OSC protocol. Tests can be run from the REPL via ASDF or command line.

(asdf:test-system "osc")

or from a shell…

sbcl --non-interactive --eval '(asdf:test-system "osc")'

or, load the tests directly and run synchroscope (which contains all sub-tests)

(ql:quickload "osc/tests")
(fiveam:run! 'osc/tests::synchroscope)

OSC v1.0 and v1.1 protocol support

This implementation supports the OpenSoundControl Specification 1.0 and the required typetags listed in the OpenSoundControl Specification 1.1 (as described in an NIME 2009 paper). Some optional types are supported.

Type tagtypedescriptionv1.0v1.1cl-osc
iint3232-bit big-endian two’s complement integerRRY
ffloat3232-bit big-endian IEEE 754 floating point numberRRY
sOSC-stringA sequence of non-null ASCII characters followed by a null…RY
followed by 0-3 additional null characters. Total bits is a multiple of 32.RNY
bOSC-blobAn int32 size count, followed by that many 8-bit bytes of arbitrary binary data…RY
followed by 0-3 additional zero bytes. Total bits is a multiple of 32.RNY
TTrueNo bytes are allocated in the argument data.ORY
FFalseNo bytes are allocated in the argument data.ORY
NNull(aka nil, None, etc). No bytes are allocated in the argument data.ORY
IImpulse(aka “bang”), used for event triggers. No bytes are allocated in the argument data.ORY
tOSC-timetagan OSC timetag in NTP format, encoded in the data sectionORY
hint6464 bit big-endian two’s complement integerOOY
dfloat6464 bit (“double”) IEEE 754 floating point numberOOY
SOSC-stringAlternate type represented as an OSC-string (e.g to differentiate “symbols” from “strings”)OOY
can ascii character, sent as 32 bitsOOY
r32 bit RGBA colorOOY
m4 byte MIDI message. Bytes from MSB to LSB are: port id, status byte, data1, data2OOY
[Indicates the beginning of an array. The tags following are for data in the Array.OO?
]Indicates the end of an array.OO?
  • Required, Optional and Not supported (or Not required)
  • type S is encoded as a UTF-8 string by cl-osc
  • data is encoded as (vector (unsigned 8)) by cl-osc

Platform support

currently supported and/or tested OS and CL platforms (platform names from github CI & roswell)

macos-latestubuntu-latestwindows-latest
sbcl🟢🟢🟢
ccl-bin🟡 (x86_64 only)🟢🟢
ecl🟢🟢?
allegro?🟡?
other????

Read the original on github.com ↗