Send a byte array directly (without any OSC tag).
Can be used to send text or binary data on a network.
This module can be added directly to the grid with a drag&drop from the browser.

It's not really recommended but, if we consider that an audio flow is no more no less than an array of data, you can use OSC to send audio to another computer. ...don't expect miracles...
Proceed exactly as for a data array.
source computer and target computer
Source and target computers must have the same BLOC size. See setup-audio.
IP address of the remote computer (to send data).
Active only if the broadcast option is OFF.
Remote Port destination number of the message.
broadcast or not ?
In OSC when you want to send a data to another computer you normally have to know the network (IP) address of the destination. Something like
192.168.1.5.The problem is that, by default, routers are configured to allocate IP addresses dynamically. In other word their IP aren't fixed and can change if, for example, you have to reboot one of your computer or your router. When broadcast is ON data's are sent to all the computers of the network at the same time whatever their IP address. So you don't have to deal with IP addresses and you're sure that all the computers will receive the message.
The main drawback is that if you have 20 computers connected you'll probably overload the network.
So if we resume broadcast ON is cool for small networks, let say, less than 10 computers. For larger networks, disable this option (OFF) and use the IP address field to set the destination of the message.
Target host of the OSC message.
Sends the message when it receives a 1 trigger.
Byte array to send.
Button. Opens the manual page of the selected object (or of its parent module for a control) in the web browser. If no page exists for this object, an error is traced in the trace panel.
For more details about information/help creation, see create-help-file.
Free multi-line text attached to the module, saved with the patch. It is only meant as an internal note for the patch designer: it is not displayed in the interface.
visible only in god mode, see setup-panel-tab-expert.
Read-only, not saved. Current private numeric ID of the object, used internally to identify it (for example as the target of a bind ID).
Read-only, not saved. Private ID used to store and recall the values of this control in presets.
Button. Generates a new unique ID, original ID and preset ID for the object. Use it if you experience difficulties in Polyphonic mode or if two objects share the same ID. Preset values and binds referring to the old IDs are lost.
Read-only, not saved. Absolute address of the object in the Usine objects tree, built from the workspace root. This is the address to use to reach the object from scripts, the objects panel or remote messages. Only shown for objects that are registered in the objects list. See objects-address.
Read-only, not saved. Address of the object relative to the current patch, valid inside that patch only. See objects-address.
Free user-defined address for the object (empty by default). When set, the object is also registered in the objects tree under this name, so it can be reached independently of its position in the workspace (the value is also reported in the mouse-over and mouse-down chunks). Changing it rebuilds the objects list. Only available on objects that support a user address. See objects-address.
version 7.0.250121
Edit All Pages