Menu
What's new
By:
Filters

Kontakt Updates (current version: 7.10.1)

Per Boysen said:
Nice to hear that it works for you. Over here I can open Kontakt 6.6.1 in Cubase but when opening Kontakt in VEPro 7 Kontakt 6.5 opens up. Unfortunately, some of my latest patches were saved in 6.6.1 and can not be used now in VEPro. Frustrating show-stopper. Has someone else had this issue? Any ideas for a solution?
Click to expand...
I feel your pain as I have made this same error more than once. Always, always, always backup your Template and/or the Master DAW files before using any new version of Kontakt. Otherwise you will run into exactly the problem you are having when you try to move back in versions. The same goes for all manner of combination of DAW with VEPro and Kontakt.

Only consoltation is you will get more practice at building your templates and patches from scratch again. It is easy to forget the myriad of steps required to build a template using VEPro/DAW and Sampler VST of your choosing.

I give you permission to tell me to take a long walk off short pier because I know that the probability is that you have just lost many, many hours of work and inspiration.
 
Last edited:
heisenberg said:
I feel your pain as I have made this same error more than once. Always, always, always backup your Template and/or the Master DAW files before using any new version of Kontakt. Otherwise you will run into exactly the problem you are having when you try to move back in versions. The same goes for all manner of combination of DAW with VEPro and Kontakt.

Only consoltation is you will get more practice at building your templates and patches from scratch again. It is easy to forget the myriad of steps required to build a template using VEPro/DAW and Sampler VST of your choosing.

I give you permission to tell me to take a long walk off short pier because I know that the probability is that you have just lost many, many hours of work and inspiration.
Click to expand...
Thank you for your nice words. Luckily I found out where Kontakt 6.6.1 now puts the plugin file, so I could manually direct VEP 7 with the search path of the current version.
 
After the latest Reaktor update, it was blacklisted by Cubase too! In case of Kontakt, the VST3 version works ok (only VST2 was blacklisted), but there is no VST3 for Reaktor yet, so one must to reactivate it in the plugins manager. After a short test with a few ensembles, it work just fine after reactivation.
(I realize this thread dedicated to Kontakt updates, but looks like the problem is not exclusive to Kontakt, but all the latest VST2 maybe... dunno)

Edit: Win 10, Cubase 10.0.50
 
Last edited:
Thomas Kallweit said:
same here - takes loots of time unfortunately with 6.6.1. Re-Batching helped, but some annoyance to do that for all libraries : |
Would be really helpful to have the latest Kontakt-Versions as a download - I would downgrade then.

Seems also the installation crumbled one of the impulse responces.
When trying to open several libraries I get "Content missing" -> Auditorium A.wav
C:\Program Files\Common Files\Native Instruments\Kontakt\presets\Effects\Convolution\K4IR.nkx

The K4IR.nkx is at its place, but has 0KB. Tried to reinstall 6.6.1 and afterwards the same, still there, but 0 KB.
Any idea from where to get only this file?
Click to expand...
Just to inform (in case someone else should come into this problem):
I reinstalled Kontakt 5 - and now the missing K4IR.nkx was there at C:\Program Files\Common Files\Native Instruments\Kontakt 5\presets\Effects\Convolution\K4IR.nkx
Copied it to C:\Program Files\Common Files\Native Instruments\Kontakt\presets\Effects\Convolution\K4IR.nkx overwriting the 0 KB file and voila - now it works for Kontakt 6.
 
TSU said:
After the latest Reaktor update, it was blacklisted by Cubase too! In case of Kontakt, the VST3 version works ok (only VST2 was blacklisted), but there is no VST3 for Reaktor yet, so one must to reactivate it in the plugins manager. After a short test with a few ensembles, it work just fine after reactivation.
(I realize this thread dedicated to Kontakt updates, but looks like the problem is not exclusive to Kontakt, but all the latest VST2 maybe... dunno)
Click to expand...
Reaktor’s important. Glad you brought it up. Sometimes the blacklisting thing isn’t evident when you are launching apps.
 
  • Like
Reactions: TSU
Not over here... So maybe provide as much info about your system and hardware and MIDI device(s) as possible?
 
EvilDragon said:
Not over here... So maybe provide as much info about your system and hardware and MIDI device(s) as possible?
Click to expand...
Sorry, I had written an entire poem about the issue at hand, but I accidentally hit ctrl+enter!

I'll come back to this later, I have the creeping feeling it has something to do with the ext. midi clock synchronisation.
 
When is Kontakt going to be optimized for APFS formatted SSDs? Some libraries load quickly, but others that are more complex, take a bit longer to load.
 
Do I need to batch resave some old libraries made with Kontakt 5.7? I'm experiencing terribly slow sample load times with some of them...
 
You could, but you'd very likely end up with same slow load times after you power cycle your computer.
 
EvilDragon said:
You could, but you'd very likely end up with same slow load times after you power cycle your computer.
Click to expand...
Kontakt 6.6.1 is creating a loud spike (with cranked fx) when using the AU or VST in VE Pro, AND in AAX in Kontakt/Komplete for instruments using width control. I updated both for Box Factory, which they posted a nka to add to the sample folder that fixed it for Box Factory, but how many other instruments might this affect that use wide control? (apparently where the problem comes from in 6.6.1). I'm using Pro Tools 2021.3.1, but have been for a long while without issue. Is this a know issue for NI and Kontakt 6.6.1? I don't see any posts about it but Fracture Sounds says it's NI's issue. Good luck hearing from them. :D
 
There's an issue between the new "from script" modulator they're using and Stereo Modeller parameter modulation. Known and tracked.
 
Careful when updating!!!! Backups!!

I'm unable to update from 6.4.2 to any new version. I tried it with 6.5 (or one of the .x iterations, maybe 6.5.3) and now 6.6.1.

When loading a big project everything freezes (waited for 10 minutes).
Happened after getting this notification below. I did what was said, resolved a missing content message and afterwards the big freeze came for me. Perhaps unrelated but know knows...
Others had the same issue, even 2 experienced bigger composers.
The fact that this is still unsolved after many months makes me think NI has lost track of their code. At least when it comes to the "unlucky" circumstances of some users.

Using Cubase 10.5, Windows 10 Home.

ecveev.png
 
DarkestShadow said:
Careful when updating!!!! Backups!!

I'm unable to update from 6.4.2 to any new version. I tried it with 6.5 (or one of the .x iterations, maybe 6.5.3) and now 6.6.1.

When loading a big project everything freezes (waited for 10 minutes).
Happened after getting this notification below. I did what was said, resolved a missing content message and afterwards the big freeze came for me. Perhaps unrelated but know knows...
Others had the same issue, even 2 experienced bigger composers.
The fact that this is still unsolved after many months makes me think NI has lost track of their code. At least when it comes to the "unlucky" circumstances of some users.

Using Cubase 10.5, Windows 10 Home.

ecveev.png
Click to expand...
I have the same problem. The workaround, I believe, is to temporarily disable ASIO guard within Cubase.
 
well, I can't work without Asio Guard and I read someone else who had the issue still had it without.

Hope it's fine if I can turn it on in the project again. Otherwise I can't work.

Well, trying one more time to update...
 
It sort of works well now.

The new way of handling missing content is still pretty annoying because it still freezes for 1-2 minutes after resolving the window - and till then some Kontakt instances remain empty. But after that short freeze everything seems to be loaded propely.

Thanks for the tip!

I don't really consider it a fix, more a workaround so it's still up to be solved. Pretty annoying to change back and forth between Asio Guard / No Asio Guard like that. And I don't want to hear it's a Steinberg issue. IMO the plugin update has to be compatible with the host, not the other way around.
That kind of blame shifting makes me worried about the reliability and future of that plugin most of us depend on.
That's like getting replacement seats for your car and if they don't fit in the manufacturer blames the car company XD

EDIT: I just got a freeze after trying to open a Kontakt instance. Lasted for 5-10 minutes, then I force quit.
Never happened before. I didn't even get a missing content message, so it seems to be unrelated.
Asio Guard definitely disabled. So, it doesn't seem to fix the issue.
 
Last edited:
You must log in or register to reply here.
Top Bottom