K-Mix as USB midi device, not working

[Makrotulpa]

Below is what I get when connect the KMI K-Mix.
I imagine it is problematic because there are 3 ports - the instruction manual it states that port three is the port for sending MIDI values.

USB Device Attached
PID: 23h
VID: 1F38h
Address (#1) assigned.
cfg desc: num interfaces 3
interface: interface 0, num 0, numep 0, class 1 , sub class 1
interface: interface 1, num 1, numep 0, class 1 , sub class 2
interface: interface 2, num 1, numep 2, class 1 , sub class 2
endpoint: interface 2, ep num 0, addr 1
endpoint: interface 2, ep num 1, addr 81
interface: interface 3, num 2, numep 0, class 1 , sub class 2
interface: more interfaces described, that config detailed, use actual number
interface: interface 4, num 2, numep 1, class 1 , sub class 2
interface: more interfaces described, that config detailed, use actual number
endpoint: interface 4, ep num 0, addr 82
Manufacturer : Keith McMillen Instruments
Product : K-Mix
Serial Number : N/A
Enumeration done.
This device has only 1 configuration.
Default configuration set.
MID class failed to init

[thetechnobear]

no, we handle multiple interface, multiple endpoints, and multiple midi ports

the issue here is the midi port is not defined
http://www.usb.org/developers/docs/devclass_docs/audio10.pdf
p99, MIDIStreaming subclass code = 0x03,
0x1 and 0x2 are audio streaming/control

so according to this, the k-mix does not have a usb class compliant midi interface.

however, perhaps there is something you need to do on it to 'activate' the midi interface.

what we would really need to see , is a full USB device tree from a computer that does not have any K-Mix driver/software loaded on it. (since this might 'activate' usb mode in the driver, like the Virus TI does)

[Makrotulpa]

so according to this, the k-mix does not have a usb class compliant midi interface.

It certainly advertises that it is. It works with an iPad Air.

The manual is quite detailed - section 4.3 focuses on MIDI.
Within this section it states...

"4.3.1.3 – PORT 3: K-MIX CONTROL SURFACE
The K-Mix Control Surface port is used for receiving MIDI from and sending MIDI to K-Mix’s MIDI banks. This is the port that audio applications should listen to in order to receive MIDI coming directly from K-Mix."

Port 2 is for the external MIDI expander if it is connected and Port 1 is for the Mackie Control type setup.

When using Lemur on the iPad the three separate ports show up as three devices.
I've noticed they show up in different orders on the iPad compared to the Mac.
The correct port needs to be selected to enable MIDI control - not sure who that is done on the AXO

what we would really need to see , is a full USB device tree from a computer that does not have any K-Mix driver/software

K-Mix doesn't have a driver on OSX - only an editor.
How can I generate a USB device tree?

Certainly think this "should" work.

cheers
Lloyd

[thetechnobear]

do you by chance have access to a linux box to connect it too?
if so, its simply

lsusb -v

(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...

[Makrotulpa]

do you by chance have access to a linux box to connect it too?
if so, its simply

lsusb -v

(you might need to sudo to do this)

I have a Raspberry Pi but it's currently lacking an OS.

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?)

On my Macs and iPad it just shows the three MIDI devices.

The switch to midi mode is a hardware thing - changing the controllers from controlling the onboard DSP to sending MIDI from one of three banks. I've seen the ports listed on Mac and OSX without having to change to the MIDI banks.

Interesting the midi ports don't show up in MIDI studio even though the Audio does. (Yes i've rescanned)