From c849aa9965efb5d8f6ac21bf097edc103d505a6f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?IOhannes=20m=20zm=C3=B6lnig?= Date: Thu, 4 Aug 2011 12:34:28 +0000 Subject: added short descriptions svn path=/trunk/externals/mrpeach/; revision=15202 --- osc/README.txt | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/osc/README.txt b/osc/README.txt index a03f6a5..92763c9 100644 --- a/osc/README.txt +++ b/osc/README.txt @@ -7,3 +7,32 @@ so you will need a separate set of objects that implement the transport (OSI-Layer 4), for instance [udpsend]/[udpreceive] for sending OSC over UDP. Author: Martin Peach + +objectclasses + +- [packOSC] + convert a Pd-message to an OSC (binary) message + (useful if you want to transmit OSC over UDP or other protocols that + have the concept of variable length packets) + +- [unpackOSC] + convert an OSC (binary) message to a Pd-message + (useful if you want to transmit OSC over UDP or other protocols that + have the concept of variable length packets) + +- [routeOSC] + route OSC-like Pd-messages according to the first element in the path + +- [pipelist] + delay lists + (useful if you want to respect timestamps) + +- [packOSCstream] + convert a Pd-message to an OSC (binary) message suitable for streaming transport + (useful if you want to transmit OSC over TCP/IP or a serial line) + +- [unpackOSCstream] + convert an OSC (binary) message suitable for streaming transport to a Pd-message + (useful if you want to transmit OSC over TCP/IP or a serial line) + + -- cgit v1.2.1