Some NI Libraries now updated to require Kontakt 7.6?
-
- KVRAF
- Topic Starter
- 3153 posts since 10 Jan, 2005
Ok, let's see where we are now.
Many Kontakt libraries are being updated so that they now need a fairly new version (>= 7.something) to be loaded.
Legacy Native Access 1.14 - needed for older OS and Linux/Wine - seems no longer mantained and does not allow to install latest versions, for example supports Kontakt 7 up to version 7.6.1, which is not new enough to load these updated libraries in new projects (Kontakt is now at 7.10.6).
So, you *need* Native Access 2 in order to get the latest versions, but Native Access 2 only runs on "current" systems.
And, Kontakt 8 is around the corner, that means that Native Access Legacy is going to be left totally behind soon in my book.
If you ask me, that's quite a mess. I'm seriously considering moving to Linux, and at the current state of things that means for me saying goodbye to Native Instruments...
- Mario
Many Kontakt libraries are being updated so that they now need a fairly new version (>= 7.something) to be loaded.
Legacy Native Access 1.14 - needed for older OS and Linux/Wine - seems no longer mantained and does not allow to install latest versions, for example supports Kontakt 7 up to version 7.6.1, which is not new enough to load these updated libraries in new projects (Kontakt is now at 7.10.6).
So, you *need* Native Access 2 in order to get the latest versions, but Native Access 2 only runs on "current" systems.
And, Kontakt 8 is around the corner, that means that Native Access Legacy is going to be left totally behind soon in my book.
If you ask me, that's quite a mess. I'm seriously considering moving to Linux, and at the current state of things that means for me saying goodbye to Native Instruments...
- Mario
-
- KVRAF
- Topic Starter
- 3153 posts since 10 Jan, 2005
Oops they did it again: the latest Analog Dreams update sets the minimum Kontakt version to 8.2.0.
So, they just don't care; NI.... I'm almost done with you.
- Mario
So, they just don't care; NI.... I'm almost done with you.
- Mario
-
- KVRAF
- 2165 posts since 22 Jan, 2005 from For me to know, for you to find out
@mabian
So a few thing you can do to protect your investment. I suggest doing this once you get your system back and stable. I did this about a year ago, and I stopped having problems with NI
#1 - Kill the NTK Daemon at startup
#2 - Kill any Native Access process at startup
#3 - Never run Native Access again
Yep, I'm walking away from NI, but I still want to use my investment. I do have Absynth, Reaktor, and Kontakt 7 loaded and running well, so no worries there. I'll be using that computer as a NI standalone in the future
So a few thing you can do to protect your investment. I suggest doing this once you get your system back and stable. I did this about a year ago, and I stopped having problems with NI
#1 - Kill the NTK Daemon at startup
#2 - Kill any Native Access process at startup
#3 - Never run Native Access again
Yep, I'm walking away from NI, but I still want to use my investment. I do have Absynth, Reaktor, and Kontakt 7 loaded and running well, so no worries there. I'll be using that computer as a NI standalone in the future
I have a really fast computer, some good mics, vintage musical instruments, and lots of fancy software. Just need some talent
- KVRAF
- 26033 posts since 20 Oct, 2007 from gonesville
That's NA's problem. It doesn't have to be yours, you can ignore it. NA not knowing where stuff is has no effect per se on the stuff's functioning.mabian wrote: Mon Jul 15, 2024 2:24 pm after installing Ethereal Earth 2.0.2 over 2.1.x Native Access still "sees" 2.1.x as installed.
I had it uninstalled for a bit, I don't need it unless I have to install something, say on a new machine. Which I did, and its issue, unable to run an installation process after a download has finshed was magically vanished on that one.
I came close to mindlessly updating something again (Vintage Organs, a vintage library by now), force quit out and no worries.
-
- KVRAF
- 3041 posts since 23 Jun, 2006 from Hungary
-
- KVRian
- 659 posts since 10 Oct, 2018
Why not let the user explicitly specify the Kontakt version cap?
That's no ZDF
That's no ZDF
Weapons of choice (subject to change):
Godin Redline, Kuassa, Fuse Audio, Audiority, Roland A-500pro, Dune, Dagger, TAL, Reaper for Rock & Synthwave pleasures; Viper and FL Studio for guilty EDM pleasures
Godin Redline, Kuassa, Fuse Audio, Audiority, Roland A-500pro, Dune, Dagger, TAL, Reaper for Rock & Synthwave pleasures; Viper and FL Studio for guilty EDM pleasures
-
concealed identity concealed identity https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=215821
- KVRian
- 1044 posts since 21 Sep, 2009
Man, I absolutely hate this. What happens to old projects with Analog Dreams loaded in Kontakt 7 once I'm on a new computer? This is so frustrating.mabian wrote: Sat Feb 15, 2025 9:58 am Oops they did it again: the latest Analog Dreams update sets the minimum Kontakt version to 8.2.0.![]()
So, they just don't care; NI.... I'm almost done with you.![]()
- Mario
-
- KVRAF
- Topic Starter
- 3153 posts since 10 Jan, 2005
In theory nothing because the instrument should be already loaded in the project. In reality I already have had issues. And I'm not sure anyway I can tweak further the sound.concealed identity wrote: Sun Feb 16, 2025 1:24 pmMan, I absolutely hate this. What happens to old projects with Analog Dreams loaded in Kontakt 7 once I'm on a new computer? This is so frustrating.mabian wrote: Sat Feb 15, 2025 9:58 am Oops they did it again: the latest Analog Dreams update sets the minimum Kontakt version to 8.2.0.![]()
So, they just don't care; NI.... I'm almost done with you.![]()
- Mario
Not really sure if there's a safe way to port the settings to newer kontakt instances without data loss, especially when it was kontakt vst2...
