It does seem, however, that one would be forced to create the appropriate responder function (
MIDIdef is far more versatile than
MIDIFunc) and then set the control bus from there… which should be extremely straightforward, nonetheless.
I’ve been working in MIDI for years, and everything above should serve as a decent primer, or reference point… it encapsulates nearly everything one would need.
I can tell you, as straightforward as I can, that the particular style of method that you’re looking for, doesn’t exist, at any rate… and so to map the incoming MIDI data to a control bus, requires some sort of responder (MIDIFunc or MIDIdef).
The only difference between the two, is all MIDIdef’s are accessible globally via
MIDIdef.all, using the value passed as the
key: argument… whereas for MIDIFunc, there is no such global list of definitions, and this requires one to first assign a variable to the response definition in order make the
MIDIFunc object available in the future… otherwise, it will be rendered inaccessible the moment it is created.
Aside from this caveat, both interfaces are nearly identical. They both inherit a working list of instance methods from
AbstractResponderFunc, a number of 14 in total, so be sure not to overlook those.