Komplete Kontrol UI Issues In Logic Pro With Third-Party Plugins

Pasted from another thread:

Perhaps this helps shed some light on why not everything can, or should, be so soon as you'd think or like.

Though a new OS is in beta prior to release, it has often been the case that breaking changes continue right up until the final public version, and that beginning work on fixes for products so highly interdependent prior to this point is often inefficient and wasted effort, as the goalposts can and do shift out from under us.

Only once a final public version, with no further changes, of an OS has arrived, does it make sense to begin the the effort to migrate to official support for that OS.

In this case, Sonoma released on September 26th. We began our efforts, which are ongoing, and as mentioned, expected to land in Q1. The effort is twofold.

Firstly, it's not just our own software (Komplete Kontrol 3) at play here. As you know, KK3 is itself a host, so we also have to consider the impact of any OS level changes on thousands of plug-ins that could be hosted in KK. This leads to an infinite number of variables, and takes time to sensibly and methodically approach as wide a number of scenarios as possible. Sometimes, we may identify a problem, but even if it affects us as a host, the fix is specific to that plug-in manufacturer's implementation rather than being anything we can fix. And so the feedback loop continues as we talk to that partner and help them report and diagnose on their end.

Secondly, when adding official support, oftentimes we find issues have been introduced by a new OS. Sometimes, as is the case now, those issues are inadvertent and present in the OS itself, and therefore must be reported to the manufacturer of that OS, in order that they may fix them so that those fixes are not passed on to our users after we claim official support.