NI Kontakt 8

[James Steele]

Well... may not be the idea forum for this, but I'll start the ball rolling with a very small observation:

I did install Kontakt 8.0.0, and so far things seem okay. One thing I wanted to share: I saw on some forums how people had said that instruments seem to load faster in Kontakt 8 than in Kontakt 7. I haven't tested it scientifically, but that does seem to be my impression as well. Seems "snappier"... at least on Apple Silicon.

[James Steele]

Okay... more piecemeal observations...

I'm using Komplete Kontrol 2.9.6. Just ran it in standalone and if you open a Kontakt library (NI or 3rd party) it seems to seamlessly open up in Kontakt 8 instead of 7.

Also... switching between different third party instruments... yes... load time feels MUCH faster in Kontakt 8.

[James Steele]

Okay... here's a quirk: my Quick Load menu that I built in Kontakt 7 does not appear in Kontakt 8. Luckily if I launch Kontakt 7 (standalone) my Quick Load menu is still there, but launch Kontakt 8, it is empty. I guess it doesn't carry over. I may have to launch both Kontakt 7 and Kontakt 8 side by side and rebuild it in Kontakt 8.

[hammerman]

HI James - I have been perusing various forums and have found this:

- NI plans one more update to Kontakt 7 to improve loading times

- There is a way to transfer your Quickload from 7 to 8 here:

https://support.native-instruments.com/ ... %20Desktop.

[labman]

Okay... here's a quirk: my Quick Load menu that I built in Kontakt 7 does not appear in Kontakt 8. Luckily if I launch Kontakt 7 (standalone) my Quick Load menu is still there, but launch Kontakt 8, it is empty. I guess it doesn't carry over. I may have to launch both Kontakt 7 and Kontakt 8 side by side and rebuild it in Kontakt 8.

Usually for us James, when we go up a full Kontakt version, we would need to copy the quick load folder from within the Kontakt 6 app support folder in user library, and copy it into the app support folder for K7 etc. So gladly we dont need to rebuild them.

Here be the hierarchy.

Users/Library/App support / native instruments/ K5/ quickload

[James Steele]

Okay... here's a quirk: my Quick Load menu that I built in Kontakt 7 does not appear in Kontakt 8. Luckily if I launch Kontakt 7 (standalone) my Quick Load menu is still there, but launch Kontakt 8, it is empty. I guess it doesn't carry over. I may have to launch both Kontakt 7 and Kontakt 8 side by side and rebuild it in Kontakt 8.

Usually for us James, when we go up a full Kontakt version, we would need to copy the quick load folder from within the Kontakt 6 app support folder in user library, and copy it into the app support folder for K7 etc. So gladly we dont need to rebuild them.

Here be the hierarchy.

Users/Library/App support / native instruments/ K5/ quickload

Thanks so much!! I had no idea there even was a Quick Load folder!! I could have saved myself a LOT of time last night. I’m a very “surface level” Kontakt user and don’t know that much about the inner workings of it. I’m not sure why new versions can’t share the same Quick Load folder? To prevent you from trying to open incompatible libraries perhaps?

[zounds]

VST3 version failed DP plugin evaluation. Had to load AU version instead

[James Steele]

VST3 version failed DP plugin evaluation. Had to load AU version instead

Are you using VST3 for any particular reason? Windows compatibility or anything like that? I use AU by default. I didn’t get any notice of VST3 failing in my case. Did you attempt to have DP re-evaluate it?

[zounds]

VST3 version failed DP plugin evaluation. Had to load AU version instead

Are you using VST3 for any particular reason?

In one of the DP webinars, Matt LaPoint suggested that people tend to be moving to VST3. Also, Melodyne ARA only works in VST I think.

Windows compatibility or anything like that? I use AU by default. I didn’t get any notice of VST3 failing in my case. Did you attempt to have DP re-evaluate it?

Yes, but I didn't restart my computer after updating to Komplete 15. After I did that, Kontakt 8 loaded as VST3. Sorry to muddy up the responses a bit, but probably a good reminder...

Also, Ozone 11 and the Neutron plugins passed inspections for both VST3 and AU, but crash DP when I instantiate them in VST3. They seem to work ok instantiated as AU.

[mikehalloran]

…
Also, Ozone 11 and the Neutron plugins passed inspections for both VST3 and AU, but crash DP when I instantiate them in VST3. They seem to work ok instantiated as AU.

Same experience here.

One of the Ozone 11 Advanced modules, Clarity VST3, failed examination the first time around but passed on re-examination.

I only tried the basic versions of the Ozone 11 and Neutron 4 VST3s. Although all of the Advanced modules passed eventually, I'm too busy this morning to see if any or all of them crash DP, also. The AUs are fine.

[mikehalloran]

Running the Ozone Standard installers from inside Native Access always hoses my Advanced installations. Today is no exception.

Screenshot 2024-09-25 at 12.27.22 PM.png (260.75 KiB) Viewed 2789 times

Edit:

Okay, this is new. Rerunning the iZotope Product Portal, Ozone 10 & 11 Standard as well as Neutron 4 Standard now all show up as Installed in Native Access. Previously, re-running the Advanced installer put Ozone 10 Standard back into Available status. It's about time they fixed this.! My Neutron 4 Advanced install was unaffected by the Komplete 15 upgrade and did not need to be re-run..

Screenshot 2024-09-25 at 12.47.37 PM.png (525.22 KiB) Viewed 2783 times