I had some chance to try ktmidi-ci-tool with KORG keystage, multipoly, wavestate, and modwave. KS and MP worked if I remove the CI "version and format" check and the message size check (because the incoming message size is not sufficient for DiscoveryReply in v1.1). WS and MW did not reply to my DiscoveryInquiry but not sure if they have different MIDI-CI implementation (might be just due to their machine states).
I thought we don't have to support MIDI-CI 1.1, but there are still few MIDI-CI devices out in the world. It is rather likely that those KORG devices are the ones. And they don't connect if we limit the target version to 1.2. Maybe we can make some minor changes in code and support v1.1, partially. Not sure how much work is needed to make things rationally comformant to the specification though.
I had some chance to try ktmidi-ci-tool with KORG keystage, multipoly, wavestate, and modwave. KS and MP worked if I remove the CI "version and format" check and the message size check (because the incoming message size is not sufficient for DiscoveryReply in v1.1). WS and MW did not reply to my DiscoveryInquiry but not sure if they have different MIDI-CI implementation (might be just due to their machine states).
I thought we don't have to support MIDI-CI 1.1, but there are still few MIDI-CI devices out in the world. It is rather likely that those KORG devices are the ones. And they don't connect if we limit the target version to 1.2. Maybe we can make some minor changes in code and support v1.1, partially. Not sure how much work is needed to make things rationally comformant to the specification though.