Uno4Kemper gets confused

  • Not sure if this is a UNO or a KPA issue but I seem to get the following error quite often.


    Using 2.01 and UNO for KPA


    In performance mode, I switch to a different rig.


    I then switch back to the original rig and one of my fx is enabled (that wasn't enabled before)


    No amount of pushing on the associated FCB1010 switch will disable the fx


    Everything else works ok


    I then enable a different fx in the same rig, disable it again, then I can disable the fx that was "stuck on"


    Seems odd.


    I've had it about 10 times.