0.8.0 prerelease

[atsushieno]

I have published version 0.7.0 only a few weeks ago, but the next version will be 0.8.0 because there will be another breaking API change that would break ABI too. It is on MidiAccess API this time, and source code wise it would affect only a few people because it is about MIDI 2.0 connection support that basically has not landed to the platforms (our ALSA support is not quite done yet, and our access to CoreMIDI is only via RtMidi which does not support MIDI2 yet, and CoreMidiAccess is still WIP and not working).

In particular, our MidiPort does not have midiProtocol property anymore. It has moved to MidiPortDetails as midiTransportProtocol. It is to distinguish MIDI 1.0 bytestream and UMP, which is more and more likely pre-determined by each platform (Android and ALSA do so). Note that it is not to distinguish MIDI 1.0 protocol and MIDI 2.0 protocol in UMP (which affects which message types are allowed). The old property on MidiPort was ambiguous to identify which is which.

(We do not have the MIDI version information on each port, at least not yet. In the latest MIDI specification it is supposed to be done by each connection by exchanging UMP Stream Configuration messages. If we try to detect that, we will have to "inspect" the messages. If we do that, it is not going to be "stream content agnostic" anymore, unlike Web MIDI API or PortMIDI.)

I have not gone forward to implement platform MIDI access API because the only backend we could work on is ALSA. But now that we have Android 15 preview that offers MidiDeviceService for UMP, I think it's time to move on.

[atsushieno]

There is now ktmidi 0.8.0-pre version, available at Maven Central. I will most likely be using it in compose-audio-controls, resident-midi-keyboard, and perhaps aap-core (I do not need ktmidi to get AAP plugins ready for MidiUmpDeviceService, but we use it somewhere else).