Patrick Reisert

Since neither `midir` nor `coremidi` lock to a specific version, `cargo update` should be able to update to the latest (compatible) version. And indeed when I do `cargo update` I...

@chris-zen Maybe you can increase the version requirement of `coremidi-sys` for the next release, so everybody gets the fix then.

Have you tried to refresh the browser cache (reload the page with Ctrl+F5)?

This is the same issue as https://github.com/chris-zen/coremidi/issues/49 (the backtrace location in the coremidi-0.8.0 example there is also `packets.rs:91:35`). So this is a bug in the coremidi crate.

On the other hand, the `Packet` based APIs have been deprecated in CoreMIDI in favor of the `Event` based APIs, so maybe `midir` should migrate ...

I opened a PR for coremidi-sys (https://github.com/jonas-k/coremidi-sys/pull/18).

This has been confirmed as fixed after `cargo update` updates to `coremidi-sys` 3.1.1.

Thanks for sharing your thoughts! It's definitely helpful to know where you're heading 👍

https://github.com/rust-lang/crates.io/issues/7250 is also related to this (see point 2.)

The winmm backend uses `midiOutShortMsg` unless the message is a sysex message (first byte is` 0xF0`). According to https://www.recordingblogs.com/wiki/midi-meta-messages, meta messages are not sysex messages and should not be sent...