Signals can be received from any loaded patcher, without patch cords Use the receive~ object to grab signals put out by send~ objects and outputs them out its signal outlet. A receive~ object can be instantiated simply by typing into an object box the short-form letter "r~". Cycling '74 MSP MSP Routing set Changes Source TEXT_HERE set Changes Source TEXT_HERE Output TEXT_HERE Name of the receive~ object Sets the name of the receive~ object. Find matching send~ objects Double-clicking on a receive~ object looks for and opens a loaded patcher window containing a send~ object with the same name. Repeatedly double-clicking on the receive~ object looks for and opens more such windows. Change the name of the receive~ object The word set, followed by a symbol, changes the name of the receive~ so that it connects to different send~ objects that have the symbol as a name. If no send~ objects exist with the name, the output of receive~ is 0. Receive a signal from all send~ objects sharing its name The receive~ object receives signals from all send~ objects that share its name. It adds them together and sends the sum out its outlet. If no send~ objects share the current name, the output of receive~ is 0. The send~ objects need not be in the same patch as the corresponding receive~. Output Channels The chans attribute is disabled in the receive~ object. It is available in mc.receive~. Name Name the receive~ object. If there is no argument, receive~ has one inlet, and a name must be provided by a set message before anything can be received. All receive~ objects that share the same name will receive data from any send~ 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); You can switch between all current receive~ objects using the set message. To turn off the audio coming from a receive~, use set with the name of a send~ that doesn't currently exist.

Note: The use of a receive~ 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. The combination of all signals coming into all send~ objects with the same name as the receive~.