Dimi i know that problem well but, have you seen the advices ? At this point i thing there is no denying that this problem exists. a sticky thread would be important i think ... more will come with the same problem
I'm not sure how long this problem has been around actually. It may have been present since the beginning. I heard it in a lot of clips over the years as I was watching the evolution of the KPA. It was one of my main concerns but I thought either it was some kind of user oversight or it could probably be worked around via tweaks inside the KPA. However this does not seem to be the case. Thus far I haven't been able to decipher any methodology within the KPA to deal with this. And frankly for a device so expensive we really shouldn't be having to struggle. IMO either the device should handle it properly or we should be given some kind of guidance as to how to profile and/or post-tweak inside the KPA to correct things.