No auto Mapping of my M32 knobs since the last KK update ?

guildem · August 1

After updating to the last Komplete Kontrol 3.3.0, I have no auto mapping of the knobs on Komplete Kontrol, and the Controller menu doesn't show my M32 anymore (visible but disabled). I rebooted my MacMini M2, but nothing changed. Reinstalling KK didn't change anything. Am I missing something ? All was working OTTB before the last update :/

Capture d’écran 2024-08-01 à 17.30.24.png

Matthew_NI · August 1

We have yet to be able to reproduce the issue, rather frustratingly (I believe that what you're seeing is very real). I have an M32 and an SMK2 both working with KK3.3 on my computer, and other internal setups as well.

Whilst we continue to diagnose, if it is in any way helpful, here is temporary access to the prior installers for KK 3.2.1:

https://drive.google.com/drive/folders/1dRk62GOAX2tQGeTVOSpTiJKpmtDhesGP?usp=sharing

Let us know if that resolves the issue temporarily. Thank you for your report and your patience.

Matthew_NI · August 2

What went wrong:

Komplete Kontrol 3.3.0 shipped on 2024-08-01.
Komplete Kontrol 3.3.0 broke connection for some A, M and S MK2 keyboards (MK3 was unaffected).

Why it went wrong:

In certain circumstances, Komplete Kontrol 3.3.0 was inadvertently ignoring NIHardwareAgent, a service used by A/M/SMK2 keyboards.
This service handles Komplete Kontrol's NKS integration for those keyboards, thus causing a failure to connect for affected users.

Severity and Symptoms:

The A/M/SMK2 keyboards for affected users would still have functioned as generic MIDI and DAW Controllers, but experienced a failure to connect to Komplete Kontrol 3.3.

Please accept my sincere apologies for the incident.

Komplete Kontrol 3.3 was in beta for weeks, and passed all of our own internal tests as well –both manual and automatic. The variable that had to exist for the above incident to be true didn't surface until we released en masse to a much larger audience.

Solution:

We deployed Komplete Kontrol 3.2.1 rollback installers via the Community Forum overnight, solving the issue for any user who we were able to reach and had prepared an email to send to all users today, had the issue not been properly solved.

The good news is… Komplete Kontrol 3.3.1 contains a fix, has been deployed worldwide and should appear in your Native Access 2 accounts already, or within minutes.

comone · August 1

Hi, me too my s49 mk2 keyboard is no longer detected in midi the plugs no longer appear on the screen and it's the same this morning it worked and after updating komplete kontrol nothing more so I uninstalled then reinstalled even the drivers but still nothing gets stuck! 😪

guildem · August 1

Thanks for your answer, something's wrong with KK then. I hope someone from NI will be informed quickly.

I also see another annoying behavior, if I set an instrument in KK, it shows its interface, and if I go on the browser and set another instrument, the sound is updated, but the interface isn't unless I close and open the plugin again. A bad and poorly tested update maybe ?

comone · August 1

I just downgraded an old version of komplete kontrol and it works fine again. How do I go back to just the previous version of komplete kontrol 3.2.1 because I reinstalled an older one?

Ps: I just bought the keyboard I received it yesterday :I

comone · August 1

I just downgraded an old version of komplete kontrol and it works fine again. How do I go back to just the previous version of komplete kontrol 3.2.1 because I reinstalled an older one?

Ps: I just bought the keyboard I received it yesterday :I

guildem · August 1

I have no idea how to do that unfortunately. But I'm sure there is serious people on NI taking this "small" issues in consideration and fix this bug in hours :) Right NI ?

comone · August 1

Yes please because my project has become hell I had to downgrade to an old version of komplete kontrol (2.9.6) and what's more my keyboard is still not detected correctly in ableton live I no longer have access to the DAW transport controls.

Matthew_NI · August 1

@guildem what are your full system and environment variables?

I ask because I am unable to reproduce the issue thus far, the Kontrol M32 is working well with KK 3.3 on my end.

Matthew_NI · August 1

@comone could you start a separate thread for the issue you're seeing? Thanks!

Matthew_NI · August 1

Also paging @Jeremy_NI to help with general Kontrol M32 connection and troubleshooting.

Perhaps something became unchecked or un-configured?

This was tested, and Kontrol M32 is fully functional for me with KK 3.3.

guildem · August 1

https://community.native-instruments.com/discussion/comment/169692#Comment_169692

How can I sens you those informations ? MacOS on a MacMini M2 Witt all updates done, KK updated to 3.3.0 from 3.2.1, nothing hacked un my mac, mac rebooted, KK reinstalled,... Of course the M32 works as a keyboard, ans I could map midi CC to KK, but that's not what I want. Browser button isn't enabled when I'm on KK, so this is a M32 detection issue I suppose.