Komplete Kontrol/Kontakt freezes Mac display (and sometimes mouse)

kirkhamilton

I've had this issue with Komplete Kontrol for a year or two, through several different software versions and several versions of Mac OS. I'm curious if anyone else has run into something like this. I'm currently running Sonoma 14.6.1 and Komplete Kontrol 3.3.4, controlled by an S61 mkII.

Komplete Kontrol intermittently freezes my Mac's displays - this happens in standalone and when I'm running it in Logic. (I keep an instance of KK/Kontakt running standalone just to have a piano sound, and also use it a lot in Logic.) When I have the app minimized, it runs and sounds just fine, but when I open the window or open it in the DAW, it often freezes the entire display on my Mac. That used to include the mouse - I had to use keyboard commands to escape the freeze - but as of the latest version it just seems to freeze the display until I move the mouse again. (Who knows how it'll manifest tomorrow.)

Over the months/years I've trashed prefs, reinstalled, and checked the required permissions that automated support often suggests. That will sometimes temporarily fix the problem, but it always returns. I've bought a lot of Native packs and instruments over the years and generally like their sounds, so I make do, but it's far from ideal.

I recorded a video of the issue as it currently manifests, but am unable to post the link because my account is new. I'll post it when I'm allowed.

It's a system-wide display freeze, as far as I can tell; no processes are actually disrupted. It's just the display. This only happens with Komplete Kontrol, and only when the window is active. I'm not sure if it's isolated to Kontakt or not, though it's definitely manifested with both Kontakt 6 and Kontakt 7. It's difficult to do a lot of testing, since it often freezes my mouse.

Has anyone here run into something similar to this? I've contacted Native support and am happy to share info about my setup in more detail, but I really just wanted to see if anyone here has run into a similar problem. It strikes me as one of those issues that's hyper-specific to something in my setup, but you never know.