Classes | External Control > OSC

OSCresponderNode : OSCresponder : Object

client side network responder


NOTE: This class is deprecated and will be removed in a future version of SC. Use OSCFunc and OSCdef instead. They are faster, safer, and have more logical argument order than the old responder classes, and they support pattern matching and custom listening ports. Use of the older classes OSCresponder, OSCresponderNode, and OSCpathResponder can be unsafe, since responders in user and class code can override each other unintentionally.

Register a function to be called upon receiving a specific command from a specific OSC address. Same interface like OSCresponder, but allows multiple responders to the same command.

Note that OSCresponderNode evaluates its function in the system process. In order to access the application process (e.g. for GUI access ) use { ... }.defer;

Other applications sending messages to SuperCollider should distinguish between sending messages to the server or the language. Server messages are documented in the Server Command Reference and should be sent to the server's port - s.addr.port - which is 57110 by default. Messages sent to the server will not be processed by any OSCresponder in the language.

Messages from external clients that should be processed by OSCresponders must be sent to the language port, 57120 by default. Use NetAddr.langPort to confirm which port the SuperCollider language is listening on.

See OSC Communication for more details.

Class Methods

Inherited class methods

Instance Methods

Inherited instance methods

Undocumented instance methods





.value(time, msg, addr)


Setting up OSCresponderNode for listening to a remote application

Listening to data from _any_ client

Listening to data from _any_ client, but from a specific host

Listening to data from the server

Watching for something specific

Watching for errors