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, Flocking's MIDI subsystem tightly couples the process of parsing raw MIDI events from the Web MIDI API with the logic required to dispatch to different higher-level events. As discussed in a recent thread on the Flocking mailing list, users who want to provide custom filters (e.g. to only fire MIDI events for a particular channel, etc.) need to be able to control when (and probably how) MIDI events are dispatched after they've been parsed.
The text was updated successfully, but these errors were encountered:
colinbdclark
changed the title
Flocking's MIDI event dispatch should be refactored so that it can be called and customized by users
Flocking's MIDI event dispatcher should be refactored so that it can be called and customized by users
Aug 10, 2019
Currently, Flocking's MIDI subsystem tightly couples the process of parsing raw MIDI events from the Web MIDI API with the logic required to dispatch to different higher-level events. As discussed in a recent thread on the Flocking mailing list, users who want to provide custom filters (e.g. to only fire MIDI events for a particular channel, etc.) need to be able to control when (and probably how) MIDI events are dispatched after they've been parsed.
The text was updated successfully, but these errors were encountered: