Boscop

@Boddlnagg Do you know which windows API calls would be used to send MIDI 2.0 messages? E.g. I want to use CCs with 32-bit resolution, they are 64-bit messages: https://www.soundonsound.com/music-business/introducing-midi-20...

Hm, I would already be happy if this only worked on windows (8.1+), maybe with an extension trait? Btw, any idea how portmidi does it? https://github.com/whentze/launch-rs/blob/master/lib/src/mk2.rs#L198

I think it makes sense to change the implementation of `port_name` to check if the port of that name still exists. So that we have a way to check for...

@Boddlnagg I'm using this function to open a midi port: ```rust pub fn open_input( port_name: &str, idx: Option, ) -> Result { let midi = MidiInput::new("")?; let port = midi...

Yes, I'm using midir on Windows.

@Deewiant I'm trying to build my project for linux and running into this issue with alsa, did you find a workaround? @Boddlnagg Or do you have an idea for a...

@Deewiant But doesn't that lose information about the error? The details?

Windows only supports sending msgs "right now", not "at some point `t` in the future": https://docs.microsoft.com/en-us/previous-versions/dd798475(v%3Dvs.85) https://docs.microsoft.com/en-us/previous-versions/dd798481(v%3Dvs.85) https://docs.microsoft.com/en-us/previous-versions/dd798474(v%3Dvs.85) So this feature would have to be built on top of `midir`...

I wasn't aware of the stream functions and I'm not sure if they can be easily unified with the coremidi way, [e.g.](http://midi.teragonaudio.com/tech/stream.htm): > Before playing queued MIDIEVENTs, you'll want to...

Well, I only use midir on Windows thus far.. Btw, how difficult would it be to implement a virtual port driver in Rust for Windows?