Input MIDI Global

Gets all incoming MIDI flow into Usine regardless of the source device.

See input-midi module for description.

Gets the incoming MIDI flow.

Settings

midi in

Received MIDI flow.

channel

Channel of the MIDI message.

msg

Type of the MIDI message.

See MIDI implementation

data

Data 1 and data 2: first and second data of the MIDI message. Depends of the message type.
For example data 1 = CONTROL-CHANGE number.

See MIDI implementation for more info.

trigger out

Sends a 1 value each time a new Data or MIDI message is generated or received.

trigger

Sends a 1 value each time a new Data or MIDI message is generated or received.

chan filter

Let passes only messages witch correspond to the channel filter. all channels: no channel filter, chan 1: only from channel 1, chan 2: only from channel 2

  • etc.

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

Time stamp of the MIDI message.

device name

Name of the device where the MIDI message comes from.

device ID

ID of the device where the MIDI message comes from. It's the order index in the setup-panel-tab-midi.

unpack

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

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.

single in poly

Determines if the module inlet/outlet appears only once in the polyphonic sub-patche, or if it is duplicated according the polyphony value.

Available only when the module is in a sub-patch.

Example with a knob. First single in poly is OFF,(a polyphony of 6 creates 6 inlets) then option single in poly is ON and creates only 1 inlet.

The actual data type of a single 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, single in poly disguises it's data representation and only addresses the first index by masking as a single-data node.

in outlet visible

Determines if the module is visible as an in/outlet in the sub-patch.

Common Settings

info

show manual

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

Description of the module for internal help purposes only. The description is not displayed in the interface.

ID's

visible only in god mode, see setup-panel-tab-expert.

unique ID

Current private ID for this control used to identify the object.

preset ID

Current private preset ID for this control used for presets.

recreate ID

If you experience difficulties in Polyphonic mode, try to recreate new id(s) with this button.

repair ID s

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.

Object Remote Address

absolute

Absolute remote address. see objects-address.

local

Local to the current patch remote address. see objects-address.

user addr

User defined remote address. see objects-address.

See also

version 7.0.250121

Edit All Pages