RM - ended unexpectedly ? - RM: 3.0.100 - KPA OS - 7.1.22 - Mac OS 10.14.6

  • Code
    1. Hello everyone, I have the Kemper and also the RM with the latest software. It has happened several times now that the rig manager has suddenly ended (error message see attachment). In all cases, the Kemper (Head) is connected to the MAC via USB. The last activities before the "crash" of the RM were editing Perfomances with the the Kemper Knobs and buttons<img src="https://www.kemper-amps.com/wbb_suite_3/index.php?attachment/11089-bildschirmfoto-2020-03-07-um-10-33-19-png/" class="woltlabAttachment" data-attachment-id="11089" id="wcfImgAttachment0">. Today I did nothing at the Kemper - only deleted via RM in the Kemper Profiles -> "last" crash of the RM. I had the crash of the rig manager with the KPAOS 7.1.20 - So after the update to 7.1.22 the problem is still there? Greetings Micha
  • Hello everyone, I have the Kemper and also the RM with the latest software. It has happened several times now that the rig manager has suddenly ended (error message see attachment). In all cases, the Kemper (Head) is connected to the MAC via USB. The last activities before the "crash" of the RM were editing Perfomances in the Kemper with the the Kemper Knobs and buttons. Today I did nothing at the Kemper - only deleted via RM in the Kemper Profiles -> "last" crash of the RM. I had the crash of the rig manager with the KPAOS 7.1.20 - So after the update to 7.1.22 the problem is still there? Greetings Micha

  • Hello everybody,
    just the same problem again. Games via Kemper and Remote - Kemper via USB connected to IMAC Rigmanager started and backed up about 30 minutes ago, nothing more on the RM since then. Now RM ended unexpectedly. Remote no longer responds - disconnect USB connection to IMAC - remote restarts, everything works again. What can you do to fix the bug? narrow down? SG

  • What can you do to fix the bug? narrow down? SG

    We need a crash report from you. Copy the entire text from the crash dialogue into a text document, contact support and reply to our questions with the document attached. This way we can have a look. And yes, more details are also necessary. Even if things looks the same like in other reports, the reason for the individual crash(es) can be very different and need different solutions.

  • We need a crash report from you. Copy the entire text from the crash dialogue into a text document, contact support and reply to our questions with the document attached. This way we can have a look. And yes, more details are also necessary. Even if things looks the same like in other reports, the reason for the individual crash(es) can be very different and need different solutions.

    email to support was send now ;-)