Posts by mikel311

    I too have been dealing with this issue on my kemper as well. I've seen it with previous OS versions in addition to the current version I have loaded on the kemper rack (8.0.6.24597). Does only appear to occur when the remote is connected. I am using reaper to automate live shows and have it controlling the kemper. It looks like reaper does midi CC chasing on play where it sends out the last state of all the previously modified CC's. So as the setlist progresses, I have modified more and more CC's and the probability that the kemper will lock up increases. Here's a sample of one blast of midi CC data that has a high probability of causing the Kemper to hang:


    0: B0 11 00 [CC17 GP Slider 2 MSB] chan 1 val 0

    1: B0 14 00 [CC20 MSB] chan 1 val 0

    2: B0 16 7F [CC22 MSB] chan 1 val 127

    3: B0 32 00 [CC50 GP Slider 3 LSB] chan 1 val 0

    4: B0 33 00 [CC51 GP Slider 4 LSB] chan 1 val 0

    5: B0 34 7F [CC52 LSB] chan 1 val 127

    6: B0 35 7F [CC53 LSB] chan 1 val 127

    7: B0 36 7E [CC54 LSB] chan 1 val 126

    8: B1 32 01 [CC50 GP Slider 3 LSB] chan 2 val 1

    9: B1 34 01 [CC52 LSB] chan 2 val 1

    10: B1 35 01 [CC53 LSB] chan 2 val 1


    One other thing to note (something I just noticed as I'm typing this)....Even though in my example here, reaper is sending out channels 1 and 2, I have a remapper on this data which remaps all channels to 2 so those chan 1 messages are going out the HW to the kemper as channel 2 (kemper is setup to rx on channel 2)...So not sure if the kemper doesn't like the fact that it's being blasted with all these commands at once, or the fact that there's a command for CC's 50, 52, and 53 immediately followed by another value for those commands, or a combination of both.


    EDIT: another thought that occurred to me after reading through the manual again, since in performance mode the CC50-54 are simulating the button presses on the remote, and the way I am interpreting the manual is values 1-127 is button press, value 0 is button release....is the kemper not liking the fact that it's seeing 2 button presses but no button release for 50, 52, and 53.

    Anyone have issues with the Kemper connecting to Rig Manager (3.0.124) after updating to 7.4.1 release build? My PC is recognizing the profiler, when I turn it on/connect it shows up in device manager. When I open rig manager it never connects, never had this problem before....Is there a setting or something in Rig Manager or the profiler I'm missing?

    PROBLEM SOLVED.


    Thanks kpahuitsing for clarifying the system settings for the MIDI configurations. I went back and made sure that MIDI THRU was not set for either midi devices (I was previously trying to set this to the address of my target helix device to the THRU port). After I made sure that THRU wasn't set to a device it works as you described and as I was expecting. I went back through the manual again after your explanation of the midi configurations and found the secret I was missing was on the first line of page 264.

    Ok, So I'm pretty sure my understanding of MIDI THRU is correct......I've tried multiple configurations for my midi connections as follows:


    PC [Midi OUT] --> Kemper [Midi IN] --> Kemper [Midi THRU] --> Helix [Midi IN]

    :thumbdown:- Doesn't work, Kemper gets MIDI from PC, Helix doesn't, but helix gets MIDI clock from Kemper


    PC [Midi OUT] --> Helix [Midi IN]--> Helix [Midi OUT/THRU] --> Kemper [Midi IN]

    :thumbup: - Everything works as expected, Helix gets commands from PC and Kemper gets commands from PC that are forwarded thru the helix. I don't want to use this configuration because it adds more cable routing for live setup...preferred connection is PC-->Kemper-->Helix




    enabling UI to Midi and Pedals to Midi in the Kemper I tried the following configurations (using ReaControlMIDI in reaper to monitor incoming midi messages from the kemper):


    PC [Midi OUT] --> Kemper [Midi IN] --> Kemper [Midi THRU] --> PC [Midi IN]

    :thumbdown:- Doesn't work, messages sent from PC get processed by the kemper, but I don't see any messages coming back to the PC....but If I move an expression pedal I get commands back to the PC from the kemper



    I don't want to merge MIDI data....I just want MIDI THRU to work....Is there a system setting that I'm missing somewhere in the Kemper? I see 3 pages pertaining to MIDI configurations (pages 13-15) and I feel like I've tried everything to make MIDI THRU work. Is it possible there's a bug in the latest firmware? Does MIDI THRU work as expected for others using the latest firmware (7.13)?

    ajbsmirnoff, I have tried the Helix first just to make sure the cables and audio interface end is working properly and that works fine...data is received by the helix, it processes it's commands and forwards the commands OUT/THRU to the kemper and the kemper receives it's commands. That works as expected, but for live setup the preference for cable routing would be PC-->Kemper-->Helix.


    kpahuitsing, how do you change the midi modes in the kemper to pass incoming data thru? I've tried setting both A and B midi devices to THRU (channel 1 for the helix) as well as just midi device B as THRU (channel 1) but I cannot figure out how to get MIDI IN data to route THRU the kemper.

    Thanks Hoki, I've also already confirmed that the MIDI cables are good. Using the same set of cables swapping the order of devices so the helix is first, then the kemper everything works fine. Also confirmed that if I enabled the UI and pedals to MIDI in the kemper and feed that back to the PC and monitor the messages using the same cables that those midi commands generated from the kemper gets output on both the OUT and THRU ports. So it seems I just can't get messages coming in the IN port to pass through the kemper.

    I'm having issues with my Midi THRU port on my kemper rack. Running the latest firmware 7.13. I am using a PC audio interface to send midi out to my kemper and a line 6 helix. connected as follows:


    PC (sending CC messages on channels 1 and 2) --> Kemper MIDI IN (Kemper global set to 2, have also tried OMNI) --> Kemper MIDI THRU (set to channel 1) --> Line 6 Helix MIDI IN(set to channel 1)


    With this configuration the line 6 helix is not receiving the MIDI CC messages from the PC (but it does receive the MIDI clock so I know the port is working). The Kemper receives the commands for channel 2 and processes them as I expect as well so I know the PC is sending out the commands. I have also tried flipping the order of my devices (PC-->Helix-->Kemper) and this works fine, both devices receive their messages as I would expect. Ideally, I'd like to have the Kemper connected to the PC directly and use the THRU as this will save in live midi cable routing.


    Any help would be appreciated.