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
It would be excellent if we could get MIDI support for input and output, as well as device enumeration and routing, etc.
Even just simple pipe to each would be OK as we can make our own stuff to handle the protocols. But, if we were going to do this it would be great to have like:
_MIDI_DEVICE_IN_PORTS$ (return name, port numbers)
_MIDI_DEVICE_OUT_PORTS$ (return name, port numbers)
_MIDI_SEND_CC port, data
_MIDI_SEND_NRPN port, data
_MIDI_SYSEX_SEND port, data
_MIDI_SYSEX_RECEIVE port, data
_MIDI_CONNECT port, listener_func_callback
_MIDI_STREAM_IN port, listener_func_callback
_MIDI_STREAM_OUT port, data
_MIDI_FILTER port, flags
_MIDI_STATUS_IN port
_MIDI_STATUS_OUT port
' where data could be ARRAY of type _MIDI_DATA: channel, etc.
It would be excellent if we could get MIDI support for input and output, as well as device enumeration and routing, etc.
Even just simple pipe to each would be OK as we can make our own stuff to handle the protocols. But, if we were going to do this it would be great to have like:
MIDI specs:
The text was updated successfully, but these errors were encountered: