MIDI Unpack

Splits a MIDI flow so that there's only one message per execution block, similar to unpack on the input-midi module, and also like the module the separate parts of the message have their own outputs.

Use this to treat MIDI messages like other Usine control values: apply math, logic etc.

Settings

midi in

MIDI input flow(s).

midi out

Midi output flow(s).

channel

Channel of the MIDI message.

msg

Type of the the MIDI message.

See MIDI implementation

  • NOTE ON
  • NOTE OFF
  • KEY AFTERTOUCH
  • CONTROL CHANGE
  • PROGRAM CHANGE
  • CHAN AFTER TOUCH
  • PITCH BEND
  • BEGIN SYSEX
  • MTC QUARTER FRAME
  • SONG POS PTR
  • SONG SELECT
  • END SYSEX
  • TIMING CLOCK
  • START
  • CONTINUE
  • STOP
  • ACTIVE SENSING
  • SYSTEM RESET

code

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.

wait cycles

Minimun number of calculation blocs between two MIDI messages are sent to the output.

Can be used to thinning transmission to external midi devices to avoid potential skipped messages or MIDI port overload when sending bursts of many messages at once. A calculation bloc (128 samples) last around 3 milliseconds, see setup-audio

trigger

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

See also

version 4.1.201021 GWPD birthday

Edit All Pages