Posts by kpahuitsing

    CC7 will not 'select rig'. it will do a volume change. Furthermore in the trace you posted, the actual parameter value which has been sent cannot be determined.


    please try to capture a trace when your controller is actually switching a rig.


    maybe your midibaby3 is sending superfluous CC7 (=volume pedal) messages or something which could result in unwanted volume changes (which could be interpreted as 'stutter')

    MIDI active sensing (0xFE) = a 'heartbeat' indication to a receiver that the KPP is 'still-active'. It can be used by a receiver to detect disconnection of the MIDI communication (i.e.: 'unplugging' a MIDI cable), and it is a standard MIDI mechanism.

    The Player does USB midi on BOTH USB ports !


    it is a very uncommon feature of an instrument to have USB-midi host capabilities, but which the Player has !


    Player usb A = host for others (footcontrollers etc.)


    Player usb B = device to PC / Mac / tablet etc.


    an USB A to USB A cable is highly suspicious, and unclear what that would be (connectiong two USB hosts? Do not use such a cable (ever)


    you need a simple USB A <-> B cable. If the HX isn't working that way, it is either not configured to send-out data through that port, or it doesn't behave as a proper USB midi device... or something else.

    Just don't have the correct "gender" and type available to do from my PC...just the captures above. I suspect it's an incompatibility with the HS USB out.

    ?? you don't have a cable to connect your HX to the PC, but you *do* have a cable to connect the HX to the Player? that puzzles me? (because that would be the exact same type of cable in both cases !)


    when the HX is a USB-class MIDI device, it should be able to connect the HX to the Player by using a standard USB A<->B cable (sometimes called a 'USB printer cable') In that case the Player should act as a USB-MIDI host to the HX.


    note: from the descriptor-dump you posted, it appears that the HX should do class-compliant MIDI, so it should work tm

    it's all in the Player's manual: https://www.kemper-amps.com/downloads


    Restoring Backups

    This option restores a backup from your USB flash-drive to the PROFILER Player. If multiple Player backups are stored on that stick, the latest backup found will be restored. Note that restoring a backup will overwrite all data and settings on your Player. To perform a restore of your latest backup, please plug USB flash drive into your PROFILER while it’s unpowered. Press and hold BANK, FX 1, and FX 2 buttons while powering on. The Player will restore and restart

    You can power the Lehle via USB by using the USB socket on the Lehle instead of the power socket.


    I’m powering my Lehle from my Stage via USB and it works flawlessly

    the Lehle pedal should even work solely connecting a USB A-B cable and using USB MIDI (so with a single cable, without a TRS (!))

    Unfortunately it seems the pedal only sends USB MIDI 'expression' control messages, which is not received on the Player. The Lehle pedal would have to send other controller numbers to make it work purely over MIDI.

    Wow, Thanks kpahuitsing
    Here is the USB device descriptor file.

    hmm... that USB descriptor looks OK, nothing strange going on there: this should work on the Player (as well as other models) Next thing would be to find out whether maybe the Ampero is causing a MIDI loop. This is tricky, we will discuss this internally and try to find a solution or work-around for this.

    maybe the problem is with Ampero's USB implementation. Could you provide us a so called USB device descriptor? This can be created easily on a Windows computer by using this tool :

    Thesycon - USB Descriptor Dumper Tool


    note : of course it is impossible for Kemper to solve issues with all external problematic USB midi devices, but we can try to investigate this a bit further.


    several external USB midi controllers have been reported to work fine, as well as several USB to DIN interfaces.. the Profiler's USB midi host function is functioning just fine for those.

    no!


    that might be true for your Airstep, but in this cause it is wrong advice!


    The ESI USB to MIDI interface is a *USB device*, so it has to be *hosted*, so it has to be connected to the 'A' port of the Player !

    This works.. it has been tested and verified with several MIDI interfaces. In this case maybe the DIN IN&OUT are swapped.


    Furthermore: the MC8 seems to have a 'B' port too... did you try to connect a USB A<->B cable (a.k.a 'printer cable'). From the specs I read that it even can be powered through that connector.... this should be the preferred way of connecting the MC8 anyway.


    Most of the recent control gear has a USB device port (=a USB B or a micro/mini port). The PROFILER can host those devices, and it is much more conveniant than DIN MIDI because IN&OUT cannot be swapped, and you don't need a seperate power cable.


    Because of these discussions people might get the impression USB midi is problematic, but in reality most of the time it will 'just work'

    OK.. so it seems Airstep you are using doesn't work. Other Airstep types seem to function OK, and other brands seem to function OK.


    again: there is a big chance that your Airstep is creating a MIDI loop !


    you didn't report back if your Airstep works when connecting 1 DIN cable only (and using a UM-ONE which you seem to have available ) When this doesn't work either.. the problem is definitely with the Airstep.


    again: we cannot debug or solve all external problematic non-Kemper products.


    maybe now the moment has arrived that you should try to contact the manufacturer of Airstep, and solve this.