Execute (call) a procedure defined by a procedure module. See procedures.

Name of the procedure to define or to call.
Defines if a suffix is added automatically at the end of the name to produce names like PROCEDURE-1, PROCEDURE-2,etc.
Custom suffix to append to the procedure name et when name suffix is set to user suffix.
Execution mode of the procedure.
Number of times the procedure is executed. For example, to fill an array it will be the size of the array.
Executes the procedure when a trigger is received.
Send a 1 value when the module is processing the operation (load, save, get etc).
A flow-from-1-to-0 must be used to trigger something when the operation is completed or canceled.
Useful only if processing mode=thread.
Sends a 1 value when the procedure has finished its execution.
Useful only if processing mode=thread.
Amount of time the procedure takes to execute in milliseconds.
Can be used to refresh the list of in/out parameters if the procedure definition has changed.
Error: "Procedure not found" The procedure name set in the Procedure Call does not match any existing Procedure module. This happens when the name is misspelled, the Procedure module has been deleted, or the Procedure module has not been created yet. Check that both names match exactly (names are case-insensitive).
Warning: "Some parameters of the procedure have the same name" Two or more input or output parameters (faders) inside the Procedure's patch share the same name. This causes ambiguity when the Procedure Call maps values to/from those parameters. Rename the duplicate parameters inside the Procedure's patch so each has a unique name.
No effect when triggering execute once in "always" mode When mode is set to always (infinite loop), the procedure runs continuously on every processing cycle. The execute once button and trigger have no additional effect in this mode — the procedure is already executing. Switch to manual mode if you want on-demand execution only.
Procedure still running (thread/exclusive mode) In thread or exclusive processing mode, if a new execute once trigger arrives while the procedure is still running from a previous call, the new trigger is silently ignored (in manual mode) or re-queued (in always mode). The processing LED stays lit while the procedure is busy. Wait for finished before triggering again, or use immediate mode if you need synchronous execution.
"Immediate" mode blocks the audio thread In immediate processing mode, the procedure runs synchronously inside the calling patch's process cycle. If the loop count is large or the procedure is computationally expensive, this will block the audio thread and cause audio dropouts. Use thread mode for heavy computations.
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