OSC In DAT
The OSC In DAT receives and parses full Open Sound Control packets using UDP. Each packet is parsed and appended as a row in the DAT's table. The table is FIFO "fisrt-in first-out" and limited to parameter-set number of lines. An optional script may be run for each packet received. Each packet/row represents either one OSC message, or an entire OSC bundle. Each argument is translated into readable ASCII text.
The supported argument tag types are:
- i int32
- f float32
- s OSC-string
- b OSC-blob
- h 64 bit big-endian two's complement integer
- t OSC-timetag
- d 64 bit ("double") IEEE 754 floating point number
- S alternate type represented as an OSC-string
- c ASCII character
- r 32 bit RGBA color
- m 4 byte MIDI message
- T True
- F False
- N Nil
- I Infinitum
- [ Beginning of an array
- ] End of an array
In the case of multi-vectored arguments (example "blob", "midi", "rgb", etc), the list of values is enclosed in double quotes. In the case of unknown argument types, a quoted list of decimal values representing the bytes of that argument are included instead.
Parameters - OSC In Page
Messaging (UDP) -
Multi-Cast Messaging -
/address - The network address of the server computer. This address is a standard WWW address, such as 'foo' or 'foo.bar.com'. You can put an IP address (e.g. 100.123.45.78). If you put "localhost", it means the other end of the pipe is on the same computer.
/port - The port which OSC-In will accept packets on.
/active - While on, the DAT receives information sent to the network port. While Off, no updating occurs. Data sent to the port is lost.
/addscope - To reduce which channels are generated, you can use channel name patterns to include or exclude channels. For example,
^*accel* will exclude accelerometer channels coming in from an Apple iPod Touch or iPhone app like mrmr. See Pattern Matching for the syntax of the possible channel name patterns.
Include Type Tag
/typetag - Includes the argument list type tag in each message. It includes the parameter type keywords (in case the parsing application needs to identify parmameter types).
Parameters - Received Messages Page
/script - the Script DAT will execute once for each message coming in. The first argument ($arg1) is the message, the second argument ($arg2) is the line number (index starting at 0) in the DAT of the message.
/executeloc - Determines the location the script is run from.
- Current Node
/current- The script is executed from the current node location (for example, where 'cc' points to).
- Script DAT
/script- The script is executed from the location of the DAT specified in the Script DAT parameter.
- Specified Component
/comp- The script is executed from the component specified in the Component parameter below.
/component - The component who's state change will trigger the DAT to execute its script when Execute is set to On Panel Change. This component is also the path that the script will be executed from if the Execute From parameter is set to Specified Component .
/clamp - The DAT is limited to 100 messages by default but with Clamp Output, this can be set to anything including unlimited.
/maxlines - Limits the number of messages, older messages are removed from the list first.
/clear - Deletes all lines except the heading. To clear with a script command, here is an example:
opparm -c /serial1 clear
/valcol - Outputs the raw decimal value of the message in a separate column. Use this when the incoming data is binary, and not readable ASCII.