![]() ![]() Kemper support blames end users for these crashes In ideal condidions, depending on the CPU spike, you may get uninterrupted playback, and not even notice the temporary overload.) the crashes are expected behaviour, Kemper support does not acknowledge that DSP overload should not result in a hard crash (if you get DSP overload in a DAW, you do not have to reboot the computer because if freezes completely. if you use ‘DSP hungry effects’ - like one mono Transpose, one mono Delay, two stereo Delays in a Rig, and engage the Looper, you can get the described crashes, due to 'DSP overload' Here’s what I learned from the interaction with Kemper support: I have been in touch with Kemper support, after much back and forth, they were able to reproduce the crashes. The crashes occur on average maybe once per hour at minimum - no way to get through a rehearsal or a gig crash free at this stage. The crashes occur seemingly at random, in different Rigs, different Performances, when hitting different buttons on the Kemper Remote. ![]() ![]() I have seen that after switching the Kemper back on, it sometimes confuses Rigs in a Performance - so you have to reboot a second time to get it to work correctly. ‘Hard crashes’ means that any sound from the Kemper stops, the user interface becomes completely unresponsive, no buttons on the Kemper or Remote have any effect, the only way to recover is to switch off the Kemper, and switch it on again. Recently, I have been getting hard crashes on the Kemper, either when switching Rigs in Performance mode, or, more frequently, when engaging the Looper to start or stop a loop. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |