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

Matthew_NI

Could you open Activity Monitor (macOS) or Task Manager (Windows) and see if NIHardwareAgent or NIHostIntegrationAgent are running?

guildem

Sorry for the delay, time to lunch here :)

I took the screenshot from the VST, this is the one from the standalone app.

guildem

https://community.native-instruments.com/discussion/comment/169714#Comment_169714

Didn't see the page 2. There is the Activity Monitor with the 2 services running.

Matthew_NI

Also - a dumb question: have you restarted your machine?

guildem

I restaReed all I can restart, including macos, my hub and the m32. Before 3.3.0 all was working ok

guildem

*restarted (smartphone keyboard doesn't like english)

guildem

My turn. Dumb question : can we install an older version of KK, like after checking a specific checkbox ?

Matthew_NI

KK 2.9.6 is available, but I assume you are asking for KK 3.2.1?

We are unable to reproduce this in-house thus far. We have just quickly again tested Kontrol S MK2, and A and M series keyboards, and found all are functioning correctly.

However - there have been around 5 reports in the last two hours such as your own report. So clearly something is going on. We will continue to investigate. Meanwhile - PM me and I'll get you an installer for KK 3.2.1.

San Holo

I have the same problem. In the MIDI Studio the M32 is highlighted. I've restored the old version of KO and the new in parallel. 3.3.0 shows in the Menu bar "MIDI" and the older version shows "M32". On the same computer everything identically.

Matthew_NI

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.

guildem

Thanks @Matthew_NI the 3.2.1 version saw my M32 right after the first start of the standalone version. This works into the DAW too. I don't think anything changed in the preferences between 3.2.1 and 3.3.0.

Matthew_NI

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.

guildem

Thank you for the details, and for the new fixed version, I appreciate the precise explanations and the time you took to help.