Artyom Nikolaev

Oh, got it. I'm using simple text editors, so no built-in debugger for me. Not sure if it will work this (https://github.com/iRet/Dekrispator/blob/62ecff120d248c21b7c607226f0fd81d7e94268d/USB/MIDIstream_class/usbh_midi_core.c#L95-L153) way still no luck in novation and simple...

Nice, thanks! I've just added debug led messages. It looks like this method called few times. And first runs works and receive my current values. But then it switched to...

That's probably few interfaces that's determine this conditions: ``` if((pphost->device_prop.Itf_Desc[iface].bInterfaceClass == USB_AUDIO_CLASS) && \ (pphost->device_prop.Itf_Desc[iface].bInterfaceSubClass == USB_MIDISTREAMING_SubCLASS)) ``` Looking for how-to determine which one is right by additional attributes. DAWs...

Yep, but anyway it knows what is audio and what is midi. I'm describing ableton live behaviour. What about to allow switching by blue button in normal not demo mode?...

Gather midi input messages all sounds good. Behaviour you described in previous message it exactly what I did in my commit. We have a loop and break as soon as...

I think we should move searching code outside of USBH_MIDI_InterfaceInit. Just leave a variable here which was defined after USB init (device was connected). But not sure where to place...

@tomassch you meant you was getting same with an usbmidi cable when in code was hardcoded interface number? If yes this is weird, it means problem not in search interface...