Chris Zen

@Boddlnagg you might be interested in this PR where I add support for the MIDI 2.0 protocol in CoreMIDI: https://github.com/chris-zen/coremidi/pull/36

I've investigated the problem, and it seems that it is a limitation of [CoreMIDI](https://developer.apple.com/documentation/coremidi/1495335-midiclientdispose). https://github.com/chris-zen/coremidi/issues/32#issuecomment-855202032

It seems that you already have a solution that re-uses the clients, but I think that if you need a robust solution, either midir implements some mechanism to scan ports,...

@Boddlnagg I got some PRs last year targeting several bugs for client notifications and some other things. I released them with 0.5.0. I'm wondering if updating to that last version...

I guess that one first step for that to happen would be to exploit rust traits for the backends. Specifically ```common.rs``` should define traits for ```MidiInput```, ```MidiOutput```, ```MidiInputConnection``` and ```MidiOutputConnection```....

Thanks for the answers, it seems it won't be a feature :-( thanks anyway, best.

@Boscop @Boddlnagg I am reopening to explore another possibility. Would you consider `midir` providing an internal scheduler for those backends not supporting it natively, but use the native features in...

> Do I understand you correctly that what you need is a variation of MidiOutputConnection::send with a timestamp parameter? Exactly that. > I remember that I once had a look...

@Boscop by the way, I just took a look to the Windows APIs and saw a set of functions for working with streams of MIDI data, which seemed to support...

@Boscop every backend will have a different MIDI clock system (with the main characteristics of being monotonic with high resolution), for example, in the case of CoreMIDI it is the...