do you by chance have access to a linux box to connect it too?
if so, its simply
(you might need to sudo to do this)
I gave some more info on this thread for others, but honestly its difficult to get the detailed information that I need... I need to see the full details, for all interfaces/endpoints, and particular the class and subclass.
(as you can see from the other thread, this is just not usually included)
up till Ive not found a program which gives the full information, a surprise, as its not that hard to write a program that does it.(but I dont have time to do this at the moment)
even so, unfortunately the axoloti logs do appear to be pretty clear, that its not supporting midi streaming.
the reason you get MID class failed to init, is it tries each of the interface looking for class=0x1 subclass=0x3 which is midi... it doesn't find it so it fails.
please bare in mind, we have lots of class compliant devices that work perfectly, so we know we are searching for the correct thing, this includes a number of other KMI devices (e.g. softstep)
given its a modern device I assumed it would support class compliant which is why I asked if it had to be activated some how...
the only thing I can think of is we only scan the interfaces when the device is connected, so if you have to activate midi AFTER its connected, it may be, we don't see the new midi interface... though this is not something ive seen before.
... this is something that you may be able to see on a computer.
(e.g. I seem to remember from a product video, you switch k-mix to midi mode... does mac osx/windows only see the midi device when you do this, or does it appear as a midi device, the moment you plug it in?)
of course, without a k-mix to connect, I cant really do any debugging/troubleshooting...