Operations define a simple functionality. They take input, apply their function to it and return a result. Operations cannot hold state, meaning they cannot store any data between consecutive calls. This also means that you cannot use any Process nodes (e.g. LFO, Damper,…) in them as those are stateful and therefore can only be used in a stateful context which an operation does not provide.
There are two different types of operations in vl:
Definition vs. Application
Using the term "operation" alone can be ambiguous if not from the context it will be clear whether we actually mean an "operation definition" or an "application of the operation definition" which again is synonymous with "node".
Static operation definitions
Member operation definitions
Member operations are not surrounded by a rectangular definition region because they can interact with each other via pads and can in fact be quite distributed over a patch which would potentially result in many overlapping regions in a patch. Therefore instead member operations are distinguished by color.
Image:Adding a member operation via the PatchExplorer
Image:Assigning a selection of inputs to a new operation
Image:Signature of a static and a member operation
By default the order of pins is defined by their left-to-right placement in the patch. To override that behavior uncheck the "pin order" toggle and arrange the pins by drag-dropping them directly in the signature.