colinbdclark
commented
9 years ago I just pushed a prototype of this UI component to the graphical-ioc branch, which will soon become the basis for Flocking 0.2.0. It works, but still has some rough edges:
- Rendering should be improved when no inputs are found (currently it renders an empty select element)
- Errors (such as the user not granting permissions) are not reported
- It only supports MIDI inputs, not outputs
- The demo is profoundly ugly
It can currently be awkward to set up Flocking's MIDI system, since you need to know ahead of time what the name, manufacturer, or ID of your MIDI controller is, based on how it is reported by the Web Audio API. Since there's also a lot of asynchrony, it can involve a lot of callbacks and nesting.
It would be nice to have a quick way to select MIDI inputs using a select box containing all of the system's current input ports, as well as a way to refresh this list when new devices are connected. A user should be able to specify their MIDI handlers to this UI component, and all the work of requesting access, presenting ports, etc. should be done by the component.