Module to automatically receive or send global arrays with OSC messages. See global-array-tutorial to learn how to use global arrays.
If you define an OSC address /usine/ this module will catch all messages /usine/1..N/ ,f with 1..N the index of the global array value. For example /usine/1/ ,f for the first index (value 0), /usine/2/ ,f for the second index (value 1), etc.
But the module will also catch all messages with the typology /usine/ ,fffff, each value of the message corresponding to its respective index in the global array. A particular case is the message /usine/ ,f which affects the first value of the global array.
On emission (sending OSC), the module will send all values as separated OSC messages /usine/1/ ,f for the first value, /usine/2/ ,f for the second, etc.
Name of the global array.
Only one global-array module should be created with a given name, so each name has to be unique.
Defines if a suffix is added automatically at the end of the name to produce names like MYARRAY-1, MYARRAY-2,etc.
User defined suffix string appended to the global array name. Only visible when name suffix is set to user.
Osc address string of the message.
Be careful, the OSC address string is key sensitive.
It mean that /USINE/ is not equal to /usine/.
Type tag of the OSC messages.
Size (number of values) expected to fill the global array. For example if the global array is an X-Y-Z array the expected tag is ,fff so the osc-tag-size is 3.
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.
Enables the reception of OSC messages for the global array.
this inlet can be an array for multiple input values.
Global array start index which receives the OSC values.
Determines if the value received at the index is considered as a "pair", and so automatically fill the index+1 with the same value.
this inlet can be an array for multiple input values.
Sends 1 when a valid OSC message is received for the global array.
List of received values indexes as an array of integers.
List of received values as an array.
Enables the sending of OSC messages for the global array.
this inlet can be an array for multiple input values.
Forces resending all OSC messages (for all values) even if the send OSC active is OFF.
Forces resending OSC messages (for each values) only if the send OSC active is ON or if send OSC active is equal to 1 for the nth index.
Remember that the send OSC active can be an array.
The value is inverted on receive and send by a 1-VALUE operation. For example, if the value received is 0.3 the final value of the global array will be 1 - 0.3 = 0.7
Opens the web browser to display information or help about the selected object, if it exists.
For more details about information/help creation, see create-help-file.
Description of the module for internal help purposes only. The description is not displayed in the interface.
visible only in god mode, see setup-panel-tab-expert.
Current private ID for this control used to identify the object.
Current private preset ID for this control used for presets.
If you experience difficulties in Polyphonic mode, try to recreate new id(s) with this button.
Each Patch shared on the local network uses its own ID (identification number). If you experience issues of Patches that don't send information to the good target, this button will rebuild all these id's.
Absolute remote address. see objects-address.
Local to the current patch remote address. see objects-address.
User defined remote address. see objects-address.
version 7.0.250121
Edit All Pages