meta: remaining MIDI-CI tasks

[atsushieno]

Here is the list of missing features in dev.atsushieno.ktmidi.ci package:

• property message chunking. It would result in separation of Message and the actual message packets in SysEx message units
• support for zlib+Mcoded7 (we need zlib implementation for KMP) -> works on desktop now
• apply property body binary conversion based on mutualEncoding
• initiator: ChannelList app developer should provide it
• initiator: Schema app developer should provide it
• ASCII validation of strings (product instance ID)
• initiator: Profile Details Inquiry
• initiator: Property subscription and subscription management
• move logging facility from midi-ci-tool (app) to ktmidi (library) module
• responder: overall UI
• responder: partial property update by RFC6901 (needs to parse the expressions and apply patching updates)
• initiator: partial property update by RFC6901 for subscription updates
• overall message buffer size verification
• Process Inquiry
• MIDI message report implementation (entrypoints are already implemented in ktmidi-ci)
• probably define Muid type that only contains an Int value but ensures that its data content is 28 bit and supports appropriate conversion -> so far it is visible as 28bit on UI
• save/load local configuration
• initiator UI: there should be device info configuration (currently it is only for responder)
• overall MUID validation
• take out muid from SavedSettings (it must be always uniquely created)
• end subscription
• support "group" in Message and everywhere applicable
• timeout manager (adds some threading complication)
• app startup/terminate lifecycle support (we can kinda skip that; the specification anticipates InvalidateMUID may not be sent)
• property pagination

[atsushieno]

For zlib compression, it would be best that we wait for ktor-utils 3.0.0 release (which contains DeflateEncoder).

[atsushieno]

For MIDI Message Report we would need to make some fundamental changes to Midi1Machine and Midi2Machine to preserve assigned state (make them tristates) and provide "catalog" on which CCs, RPNs, NRPNS, and per-note of those are "supported".

[atsushieno]

Group support is implemented, but we need MIDI 2.0 I/O support at device level in ktmidi in the first place. Currently it is supported only in AlsaMidiAccess virtual I/O.

[atsushieno]

Those remaining issues are split into individual tasks. Closing this long-running issue.