You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the flock.midi.controller component provides a (still somewhat awkward) means for declaratively mapping incoming MIDI control and note on/off messages. However, it doesn't support other types of messages such as pitchbend, aftertouch, etc.
This should be remedied by restructuring the component's options to have a "mappings" object at top level that can contain keys for each MIDI message type (i.e. control, noteOn, etc.).
The text was updated successfully, but these errors were encountered:
Currently, the
flock.midi.controller
component provides a (still somewhat awkward) means for declaratively mapping incoming MIDI control and note on/off messages. However, it doesn't support other types of messages such as pitchbend, aftertouch, etc.This should be remedied by restructuring the component's options to have a "mappings" object at top level that can contain keys for each MIDI message type (i.e.
control
,noteOn
, etc.).The text was updated successfully, but these errors were encountered: