Custom OSC
Looking for Custom OSC Examples? Take a look at Custom OSC Examples - Eos
The Custom OSC Connection links to a Custom OSC Widget allowing for display of OSC information.
Status
The detected status of the connection. The two options are:
Connected (Green)
Disconnected (Red)
Name
The name of the connection
Port
The port to listen on for incoming OSC information
Method
The method to use for Custom OSC. Options are:
TCP ClientTCP ServerUDP
IP/Host
The IP address of the OSC server to connect to
Port
The port to use to connect to the remote server
Version
The OSC version to use to to connect to the remote server. Options are:
1.0 (PLH)(Default)1.1 (SLIP)
Ignore Bundle Timing
Whether or not to process and display messages based on OSC bundle timing. Unless there is a compelling reason to turn this off, leave it on.
Screenshot
Actions
OSC Messages ingested by the OSC Connection are passed to the OSC Actions handler so that no further port configuration is necessary to control Vor.
For more information about controlling Vor from a connected device, check out Actions
OSC Addresses
The OSC addresses to listen to for incoming data
Supported OSC Arguments
Vor supports all required argument types as specified in OSC v1.1.
| OSC Type Tag | Type of Corresponding Argument |
|---|---|
i | Integer: two’s complement int32 |
f | Float: IEEE float32 |
s | NULL-terminated ASCII string |
b | Blob, (aka byte array) with size |
T | True: No bytes are allocated in the argument data |
F | False: No bytes are allocated in the argument data |
N | Null: (aka nil, None, etc). No bytes are allocated in the argument data |
i | Impulse: (aka “bang”), used for event triggers. No bytes are allocated in the argument data |
t | Timetag: an OSC timetag in NTP format, encoded in the data section |
Screenshot
Last updated
