This could act as a warning if you are pumping lots of midi data out, perhaps as part of your show, and your Kemper may be open to receive some "illegal" midi data.
I am also curious to know what protection there is in regard to any kemper (let's use the player for this example) when receiving too much or "bad" midi data.
What i mean by "bad" midi data is midi that is corrupt, not by hardware fault but perhaps the wrong messages are being sent. I recall fixes being put in place (ages ago) that prevented midi buffer overload, which used to cause similar issues.
i recently tried to change an FX slot using midi NRPN data. Much control of all kempers can be done this way. However, i got one value wrong and every time i sent this "bad" mid data it crashed the Kemper and made a loud whining noise. Believe me, you wouldn't want this to happen during a live show.
Here is an example that crashes my player:
BAD midi that crashed the unit:
CC#99 50 (module A)
CC#98 0
CC#50 0 WRONG CC NUMBER (should be CC6 not cc50)
CC#38 100
Correct Midi is
CC#99 50 (module A)
CC#98 0
CC#06 0 (effect type acoustic simulator)
CC#38 100
If you are relying on midi control from external sources (some people have sequencers controlling their KPAs) and this kind of midi data gets sent you need to be sure it wont mess things up.
Should the Kemper detect and reject this bad midi data?