Working with the Web MIDI API can be awkward, since it provides an asynchronous, Promise-based API that requires access requests to be made prior to being able to access basic information about the user's MIDI system (for good reason, of course).
Although there are plans in a future release of Flocking to provide a simple dropdown menu for selecting MIDI devices in the Flocking Playground (and which can be embedded in other applications), it would be helpful to have an easy way to grab access to the connected MIDI ports and log them to the console.
Working with the Web MIDI API can be awkward, since it provides an asynchronous, Promise-based API that requires access requests to be made prior to being able to access basic information about the user's MIDI system (for good reason, of course).
Although there are plans in a future release of Flocking to provide a simple dropdown menu for selecting MIDI devices in the Flocking Playground (and which can be embedded in other applications), it would be helpful to have an easy way to grab access to the connected MIDI ports and log them to the console.