In Studio One Komplete Kontrol keeps saying Update Required

@Jonas Denolf

"Everytime i reopen my project this window pops up but when i open native access it doesn't show an update, what can i do?"

What version of Native Access are you running?

And what version of Komplete Kontrol?

VP

Fair enough. That dialog box does not look like a Studio One dialog tho.

And Studio One would have no knowledge (or care) whether or not Komplete Kontrol is updated.

What exactly is in this S1 project?

Also - what OS you are using and what version of Studio One? That would be helpful.

VP

Hi, I am facing similar issues with Studio One 6.5.2.97444 and my S61 MK3 Keyboard using Komplete Kontrol. My Specs are below. The exact Issue is as follows:

• I can load a Project containing Komplete Kontrol Instruments without a problem.
• After opening the project, a regular VST3-Instrument is automatically selected (because it was saved like that). Still, the MK3 Keyboard will show a random Komplete Kontrol Instrument from the project instead of the DAW-View.
• When browsing through the tracks of the project (either by hand or by using the big MK3-Encoder), some Komplete-Kontrol-Instances will work fine, others will display the exact same error message that @Jonas Denolf posted originally.
• I already found out this is NOT an issue with the instruments. I literally spent days investigating this, testing different instruments and different projects. In one project, the affected Instrument might be "Analog Dreams" while "Ethereal Earth" is working fine. In another project, it might be the other way around. In another project, both work fine and "Kinetic Treats" is affected. It seems to be completely random.
• If I get the errormessage on an Instrument and click OK, the Instrument will open fine and can be played, but it does not detect the MK3 keyboard (it only shows "MIDI" instead of the 61-Icon) and of course all MK3 functions like control-knobs, lightguide, etc. are not available then. The MK3 will show the default midi template.
• Sometimes, I even get the same error message in Kontakt 7, but I did not find a reliable way to reproduce this with Kontakt.
• I created a video documenting these issues: https://1drv.ms/v/s!Aq4Sj2dM3Q5vki-SD8siPAB9GUS7?e=Eawuaf

For the record:

• I did contact the NI support about this issue (#4093646), but after some back and forth I was told to wait for Presonus to release an update which fixes this.
• I then contacted Presonus, and after some more back and forth they told me the error is more likely to be on Native Instruments side and I should come back here.
• I tried to get this running on both an existing Windows 10 drive and a freshly installed Windows 11 drive
• I reinstalled Hardware connection Service
• I installed every update since october
• The S61MK3 is connected to the PC using a USB-C to USB-A cable, goint into a powered USB-3-Hub
• The S61MK3 gets its power from an official power supply of the Nintendo Switch Game Console.
• The cubase user @FilmCompos3r reported a similar issue when using Kontakt 7 in Cubase 13 on february 1 2024 here: https://community.native-instruments.com/discussion/comment/130193/#Comment_130193

Current Versions:

• Native Access: 3.8.1
• Komplete Kontrol: 3.1.2
• Kontakt: 7.8.1

My PC Specs:

• Windows 11 Home 23H2 (22631.3155)
• CPU: AMD Ryzen 9 5950X
• Mainboard: Gigabyte x470 Aorus Ultra Gaming
• RAM: 64 GB GSkill FlareX 3200 (4x16 GB)
• GPU: AMD Radeon 6800XT
• SSD: WD Black SN850P
• Audio Interface: Universal Audio Volt 476

Sorry for the wall of text, I really hope it helps.

Hi folks, I've been having this problem, and now I know I'm not alone! Same as @Megatim I've raised support calls with both PreSonus and Native Instruments. The call with PreSonus has come to an end - they reported that logs showed up problems with a 'ucrtbase.dll' - C runtime, used by Visual C++ and others. Have tried reinstalling VC++ versions, and lots of other things. PreSonus said that NI are aware, and they cannot help any more.

The call with NI is still open, but no information for over a week now except that they are discussing the issue in the team (which is not a bad thing, good to talk it out). I will nudge them again today, and add a link to this forum page.

I've tried so many things - uninstalling / reinstalling KK, Hardware Connection Service, Studio One etc etc. Have run in admin mode. Have tried with keyboard switched off. Have tried with different or no audio devices...

...and there's a clue, because with my usual Focusrite Scarlet 2i4, I get the usual 'update required' followed by crash. With Realtek, no crash, which enables me to put the cursor on a non-KK track and save (that's important to avoid crash upon next startup). As others have said, the KK instrument seems irrelevent. I've tried to isolate it - NI products, Fracture Sounds, Spitfire etc etc - no pattern emerging there.

I've also tried with Kontakt 7, which seems to 'mostly' behave itself (some bugs but nothing showstopping), so that's a workaround.

So, definitely a problem, Studio One and KK are unworkable. If more people have this then NI devs will prioritise it. I appreciate this is new tech / software, and am happy to work on this forum and with devs to solve the problems. I will update this forum with any findings from my support call.