Gets the incoming MIDI flow.
Received MIDI flow.
Channel of the MIDI message.
Type of the the MIDI message.
Code1 and code2: first and second data of the MIDI message.
Depending of the message type.
For example code1 = ControlChange number).
See MIDI implementation for more info.
Sends a 1 value each time a new Data or MIDI message is generated or received.
Let passes only messages witch correspond to the channel filter:
Message name to let pass.
-No filter-: all MIDI messages pass. NOTE ON/OFF/BEND: passes NOTE_ON, NOTE_OFF, PITCH_BEND, KEY_AFTERTOUCH, CHANNEL_AFTERTOUCH messages.
Useful to connect a MIDI keyboard to a VST/AU instrument, and filter Control Changes messages.
Time stamp of the MIDI message.
Name of the device where le MIDI message comes from.
The Unpack option transforms a polyphonic flow to monophonic.
For example, if two MIDI Notes arrive at the same time, Usine delays the second note a little to always create monophonic signal.
With this new MIDI flow, you can apply any math transformations you want because the MIDI flow become almost like a normal data flow.
Sysex array data received from the external MIDI device.
Usine removes automatically the BEGINSYSEX at the beginning and the ENDSYSEX at the end of the byte array.
Determines if the module inlet/outlet appears only once in polyphonic sub-patches, or if it is duplicated according the polyphony value.
Available only when the module is in a sub-patch.
Example with a knob. First once in poly is OFF,(a polyphony of 6 creates 6 inlets) then option once in poly is ON and creates only 1 inlet.
The actual data type of a once in poly node is similar to an array. Once inspected you can see that it is an array the length of the nb of polyphony selected for that specific sub-patch. Although an array in data-type, once in poly disguises it's data representation and only addresses the first index by masking as a single-data node.
Determines if the module is visible as an in/outlet in the subpatch.
version 4.0.200329Edit All Pages