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.
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.