OSCDispatch [Help Patch]

Route OSC Messages to OSW variables that match address pattern.

Syntax

OSCMessage options

Arguments

Inlets

Comments

When an OSC message is received, its address pattern (which may include valid OSC wildcard characters) is matched against all currently active OSW variables. Each variable is set to the value of the argument(s) of the message. If the message contains more than one argument, it is converted to a list (thus any matched variables must be of type List or Any).

Consult the chapter on OpenSound Control support for more information OSC addresses.

If you are not using OSC packets for network or inter-process communication, consider Put*, which matches variables against OSC-style wildcards, but is a little more efficient when only matching state variables and also allows relative path names to variables (relative paths are disallowed in OSC). However, Put* only matches and sets state variables; it does not handle other kinds of OSC messages (e.g., queries, special methods, root methods, documentation). If you wish to use these other types of OSC messages on OSW objects, OSCDispatch is required.

Known Issues

OSCDispatch currently only accepts wildcard addresses for setting states. Special object methods, root methods, documentation queries, etc., do not match wildcards.

See Also

Put*
OSCBundle
OSCMessage
OSCDispatch
OSCRoute
OpenSound Control support in OSW
The OpenSound Control home page