Patrick Reisert
Patrick Reisert
... whatever that means. This is currently just a meta issue to collect information and ideas.
As identified in https://github.com/Boddlnagg/midir/issues/35#issuecomment-775381492, the implementation of `port_name` currently does not behave according to the documentation with regard to an error being returned when the port is no longer available:...
I'm not sure how easy that would be, and if it would give us any advantage. But if someone wants to try it, feel free! However, it's important that we...
Try to support all features needed by the Web MIDI API (https://www.w3.org/TR/webmidi/, currently in Working Draft status). This could potentially enable later use of midir within Servo :wink:
E.g. compile with support for both ALSA and JACK, and give the application the ability to dynamically select the backend. It is not clear how this interacts with the `jack`...
This is a follow-up to #32. See the WebMIDI spec for a neat description of a "persistent port ID" (https://www.w3.org/TR/webmidi/#attributes-1): > This can be used by developers to remember ports...
The WASM/Web MIDI backend (#47) disabled some tests that ensure `Send` is implemented for API structures, because those parts of the Web MIDI API only work on the main (browser...
Although related to #6, (semi-automatic) unit tests should be added regardless of CI. Some possibilities include (for all backends): - Sending and receiving very long (> 1 KB) sysex messages...
Since our backend implementations are mostly ported from RtMidi, some of the [issues](https://github.com/thestk/rtmidi/issues) there might be relevant to midir as well.
https://github.com/paholg/dimensioned is much more mature.