KK 3.3 broke MK2 keyboard connection (Already fixed 2024/08/02)

MyStudioOne
MyStudioOne Member Posts: 283 Pro
edited October 22 in Komplete Kontrol

Hi All, I tried to give KK 3.3 a test drive just for the heck of it and it broke the keyboard connection to my S88 MK2. It also crashed KK standalone app. I rebooted and tried again. Still no keyboard connection whatsoever.

Reverted back to 3.2.1 and it worked fine again. 3.3 didn't like my PC at all.

Windows 11 pro

AMD Ryzen 9 5950X 16-Core Processor

Best Answer

  • Matthew_NI
    Matthew_NI Product Team Posts: 1,372 mod
    Answer ✓

    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.

Answers

  • Matthew_NI
    Matthew_NI Product Team Posts: 1,372 mod
    Answer ✓

    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.

  • MyStudioOne
    MyStudioOne Member Posts: 283 Pro
    edited August 3

    I confirm that I reinstalled and 3.3.1 works as expected. Thanks for following up.

    From what I can see, midi control on the MK3 is much improved compared to the MK2. I am especially impressed the importing and exporting/sharing templates feature. Nicely done, NI Team.

    I look forward to hearing feedback from MK3 users.

This discussion has been closed.
Back To Top