So I perused the 'net for a minute as regards Kontak 6 & 7 vis a vis Cubase. I saw K8 problems with Cubase 14, 6 or 7 with Cubase generally incl. C13 & 14, and I got no sense these were limited to Mac vs Windows OSes. Others are experiencing crashes, with various culprits or inconclusive.
I can say I used both 6 & 7 in Cubase 13 projects under Mac OSes 13.x & 14.x with no issues but again I have not had issues historically at all.
No idea how older or third party libraries would even be a factor. The libraries I used were not very new, particularly and they were third party.
As to NI more generally being 'usable', I have two use cases where answer is not really: Kontakt 7 (incl .10.7 the final v) as AU in VE Pro (output cfg bug) and Reaktor 6 in VE Pro period, where the same thing including all my automation in Cubase performs nicely, in VE Pro brings the system to its knees. I've gotten the sense that AU in VEP is zero priority, ie., not tested.
So I'm using K7 as VST 3, it's fine. Reaktor is kaput either way. The OS compatibiliy list for Sequoia OS (OS 15) now includes "Komplete Effects": Replika XT has a peculiar bug in that it mixes up the names of parameters in what it exposes to VEP and that VEP exposes to Cubase (13).
Absynth 5, EOL 2022 works fine under OS 15. Take these lists with a grain of salt.
Can Kontakt be trusted?
-
- KVRAF
- 26033 posts since 20 Oct, 2007 from gonesville
So today I see a new post under the thread [at VI Control] Kontakt 7 updates by one Evil Dragon, my source for 'final version {7.10.7}': 'Kontakt 7.10.8'. and this is so totally the final version this time that the thread is locked.jancivil wrote: Sat Aug 02, 2025 8:43 pm Kontakt 7 (incl .10.7 the final v) as AU in VE Pro (output cfg bug)
the bug is still there, however.
-
- KVRAF
- 24402 posts since 7 Jan, 2009 from Croatia
Yes because that release focused on backporting just one specific bug regarding filepath constructing that NA2 exposed in Kontakt's codebase. Which is something that affected way more users than there are users which use the AU+VEP combo.
-
- KVRAF
- 26033 posts since 20 Oct, 2007 from gonesville
my point quotes me asserting that, covering my ass. and 'final version again' is meant as some levity rather than a diss. Should signaled with a emoji, i guess. and now here's 10.9.
I'm not even using that combo. I did instantiate as AU at this version number to see if 1) it fared better than Reakor as AU in there, & 1b) any performance diff, which might be if NI had signed on to Apple Audio Group AU protocol. I don't think it has. Didn't get around to it as I was trying the fix, delete output configuration to make it rebuild such, got tired.
AFAIK the number of people that care about this went from one to zero after that.
BFD3.4 AU in VEP (at one juncture, for me siince 2023) was worse than Reaktor, the worst performing thing in the known universe. which had me in Cubase Rosetta 2 mode a couple years more than I shoulda needed to because only since Feb. this year exists an Apple Silicon VST3. And during the last stage of the beta I uncover that 3.5 has a bug that some report Kontakt 7 has, albeit not fatal like BFD's (GUI blank unless undocked).
I'm not even using that combo. I did instantiate as AU at this version number to see if 1) it fared better than Reakor as AU in there, & 1b) any performance diff, which might be if NI had signed on to Apple Audio Group AU protocol. I don't think it has. Didn't get around to it as I was trying the fix, delete output configuration to make it rebuild such, got tired.
AFAIK the number of people that care about this went from one to zero after that.
BFD3.4 AU in VEP (at one juncture, for me siince 2023) was worse than Reaktor, the worst performing thing in the known universe. which had me in Cubase Rosetta 2 mode a couple years more than I shoulda needed to because only since Feb. this year exists an Apple Silicon VST3. And during the last stage of the beta I uncover that 3.5 has a bug that some report Kontakt 7 has, albeit not fatal like BFD's (GUI blank unless undocked).