Send signals without patch cords The send~ object lets you send a signal to another patcher window or to another location within the same patcher window without using a patch cord. A send~ object can be instantiated simply by typing into an object box the short-form letter "s~". Cycling '74 MSP MSP Routing Send to receive~ a TEXT_HERE Send to receive~ a TEXT_HERE Name of the send~ object Sets the name of the send~ object. Clear all receive~ buffers associated with this object The clear message clears all of the receive~ buffers associated with the send~ object. This message is only used with patchers which are being muted inside a subpatch loaded by the poly~ object. Double-click to find matching receive~ objects Double-clicking on a send~ object opens all windows containing receive~ objects with the same name, and also lists the instance numbers of patches hosted in a poly~ object that share named receive~ objects. Change the name of the send~ object The word set, followed by a symbol, changes the name of the send~ so that it connects to different receive~ objects that have the symbol as a name. (If no receive~ objects with the same name exist, send~ does nothing.) Send a signal to all receive~ objects sharing its name The send~ object sends its input signal to all receive~ objects that share its name. The send~ object need not be in the same patch as the corresponding receive~ object(s). Name Name the send~ object. All send~ objects that share the same name will send data to any receive~ objects that share their name.

If you want a named send~/ receive~ object in a Max for Live device to be unique to the device, use three dashes (---) to start the name of your send~/ receive~ destination (e.g. s ---filtercutoff).

When your patch is initialized, it will replace the three dashes with a unique-to-Live number (e.g. s 024filtercutoff); The destination of the signal can be changed on the fly using the set message. A receive~ object with the same name receives the output of send~. When two or more send~ objects are aimed at the same receive~ object, the signals add together.

Note: The use of a send~ object can introduce a delay of varying lengths. This delay is dependent on a large number of factors including, but not limited to, how many send~ and receive~ objects are involved, if a feedback loop is detected, and the use of different top-level patchers with multiprocessing enabled. Signals are routed remotely (i.e., sans patch-cord-connection).