New Komplete Kontrol 3.3 Update
Answers
-
That’s very interesting - definitely shouldn’t be happening like that
0 -
Does he need to send the hardware link to everyone? I backdated to link above (3.2.1), and now it works fine. I can't get the link you posted to work.
0 -
It is still not the perfect solution since there is an error message
0 -
Hopefully they get it fixed soon.
0 -
Looks like it has
0 -
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.
2 -
I managed to remove the Hardware Connection Service and installed the new version and I can confirm everything is working beautifully now. Thanks for solving this problem before the weekend
1 -
I get the feeling that, in 99% of cases, issues in Native Access or other NI apps are caused when communicating with the backend, or with background tasks/services.
1 -
I live in a world surrounded by interdependencies
4 -
Does the latest, Komplete 3.3.1 work on OS Ventura? Is anyone using it with Ventura?
0 -
I'm sure it's gonna work just fine
0 -
Hi don't know if this is the right page to raise this issue. With KK 3.3, when I load an instrument for e.g. crosstalk piano, the first sound I use is ok but if I choose another sound, then the UI on the computer is frozen (UI on the KK 61 mk2 is ok and working). So the keyboard still works but the UI software on computer does not. Then if I choose another instrument, say melted vibes, the sound changes but the UI on computer stays on Crosstalk.
And if I try to access my favorites, then the UI is all over the place and I am not seeing the right instrument on the computer.
Any advice, solutions appreciated. Thanks.
KK 3.3.2; Keyboard Komplete S61 mk2
Macbook M1 Pro; Sonoma 14.6.1
0 -
Try minimising and restoring the window to force the graphics to refresh
Bug has been reported many times so hopefully will be fixed soon
1
Categories
- All Categories
- 19 Welcome
- 1.4K Hangout
- 60 NI News
- 761 Tech Talks
- 4K Native Access
- 16.2K Komplete
- 2K Komplete General
- 4.2K Komplete Kontrol
- 5.6K Kontakt
- 1.6K Reaktor
- 373 Battery 4
- 831 Guitar Rig & FX
- 423 Massive X & Synths
- 1.2K Other Software & Hardware
- 5.6K Maschine
- 7.1K Traktor
- 7.1K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators