bazzmaka

... update II: an interaction with the support of Keith McMillen and some further diagnosis let me assume that the problem is related to a missing/faulty implementation of the so-called "running status" in Deluge's MIDI implementation. "Running status" is part of the MIDI specification and omits the status byte of MIDI messages if it is following a message with the same status byte. Both the Windows Midi Driver and the KMUH seem to re-insert the status byte into the MIDI stream. This is why the SS2 works in host mode and through the KMUH, but not directly connected to the Deluge's USB. The missing/faulty implementation of the "running status" might be the reason why other usb-controllers don't want to team up with the deluge ====> if my analysis is true: please fix this!

... update: the Soft Step 2 works perfectly well if connected through a Kenton Midi Usb Host (KMUH) to the Deluge: The SS2 is connected via USB to the KMUH. The KMUH is connected via a 5-pin cable to Deluge's Midi in. The KMUH is powered from the Deluge's USB-Port. Connecting The SS2 directly with USB to the Deluge doesn't seem to work :-((

@oHn: I've used an adaptor that converts the A-Type plug of the white BSP cable to the B-Type plug of the Deluge. I assume you did the same to connect the KeyStep?! Once connected, the BSP powers up and you can switch it into in controller mode (dedicated key in the uppermost grey area). In controller mode, all the pots and pads of the BSP send midi messages. The detailed configuration (which control sends which message on which channel) is configured in the Arturia Midi Control Center. Does this help?