We've worked a bit on it. I got confirmation from HQ on 4th of Dec 2015 that the cracking was reproduced and developers' team will apply fix in next Operating System. Let's hope we'll see fresh OS close to NAMM which is in 7 days
Thanks for keeping us posted 
I get this crackling too, occasionally but far too often.
This is the Gundy-Gilmourish factory rig, headphone space is *not* ticked, Space 0.0, Purecabinet at 3.9
Make a back up and sent that to support explaining exactly what happens and how to make it happen. I'm sure they will help you and like to know about this issue
... and you will be helping us all
Oh wow, I thought this was going to be crackling as an effect. Like the first sound in this video:
I loved that out of the Mobius, but I sold it when I got the Kemper. I sometimes miss that feature, though.
I've had this problem as well though, but without headphone space, as I never use headphones with my Kemper. Weird.
Make a back up and sent that to support explaining exactly what happens and how to make it happen. I'm sure they will help you and like to know about this issue
Yes, I could raise a ticket. Support has been stellar so far.
Except I don't have any hard data, only the fact that this occurs whenever the planets happen to be in conjunction.
Can not reproduce on purpose.
Like yesterday I made a change to Pure Blues factory rig, adding a delay.
It behaved well all day long. But today, maybe after 10mins after selecting that rig, Kemper throws a fit that lasts a couple of minutes.
It clears up by itself and after that all is well for many hours.
The KPA team will have ways of forcing this to happen so a back up is always a good thing to send them
For what its worth, I turned on "constant latency" and my cracking stopped... not sure why though since that is clearly not what it is for.
Cheers,
Constant latency set the latency to the highest possible value. so your symptoms may relate to what you experience when a converter's buffer is set to too low a value.
There must be some reset that fixes this, since the Profiler is of course designed to run a rig at its "lowest" latency.
So disappointed that this still exists in the 3.3 beta!
