Hi all,

I'm using the @bobdule Kontakt v6.7.1 on Win10, and i'm starting to think about installing Kontakt 7. I don't need v7 per se, but i know that in the near future there are gonna be new libraries coming out that work on v7 only, so i figure it might be smart to futureproof my setup now rather than later. What do i need to know?

1. All of my libraries were added with the "Add Library" tool that Bobdule provides in v6.7.1. Will that tool work for v7 too? If not, what's the process for adding cracked libraries for v7? (official + unofficial)

2. I have 3rd party libraries where the .nicnt was created by the NICNT Maker provided by Bobdule in v6.7.1. Will those libraries work in v7 too?

3. Will installing v7 break anything in v6? Can they co-exist?

4. Do i need to worry about anything in regards to windows registery when i switch to v7?

5. I've never installed Native Access, so i don't have a NativeAccess.XML file on my computer. Is there anything i need to be aware of in regards to that?

Thanks!

 

Last edited: Jan 4, 2023

Hello, as far as I know
1-2) absolutely yes
3) Not really sure but there is a catch: before installing make a backup of kontakt v6 files and of your projects because it is a breaking update. With that I mean that if you try to open projects with kontakt 6 patches saved in them with kontakt 7, you will lose all the patches and have to restart from scratch. (I've learnt that the hard way unfortunately).
4) Not really sure
5) it is recommended to have one in the right place in the hdd even if you don't have NA installed because it is used for licensing NI's products

 

1) yes
- those that is NKI ready need their original modified nicnt, but basically if it works in 6, it will work on 7 as long as no SPNID number clashing.
2) yes
- I think the nicnt generator, and add library we have now is from Kontakt 5, no ? maybe BobDule modified it
3) no, yes
- they both have different dll/vst3 name, Kontakt 6 is just "Kontakt", while Kontakt 7 is "Kontakt 7". So yeah they can co-exist while sharing the same libraries and run both of them at the same time in a single project.
4) no
5) not sure about this

 

I'm planning to finally install K7, but I have active projects with a lot of K6 tracks. Can anyone verify if what @relepega said is true? Will I lose my patches when I load up a project with K6 tracks whilst K7 is installed? I would assume that K7 is separate from K6 and I can technically have both running at the same time in one project, with none affecting each other, like K5/K6. @relepega's wording is a bit confusing to me, I hope someone can reassure me about this.

 

I kept both for awhile when switched from 6 to 7, due to older unfinished projects, they can co-exist with the same libraries

 

Only if you uninstall Kontak 6. Is like Stevie Dude said, Kontakt 6 and 7 can coexist. I even have a Kontakt 5 portable that take care of my old projects cause I'm lazy to migrate them to new versions.

 

It's not that K6 and K7 couldn't coexist. It's rather that once you've (accidentally) re-saved a K6 nki with K7, K6 won't open it anymore.

 

I'm hijacking this thread because I have a related problem. Few weeks ago, I've been a good boy and got a legit copy of Kontakt 7. I noticed that many presets from the Factory Library 1 (presets that I made me purchase the thing, like the organ or the full orchestral percussion set) are missing from FL2.
Is there a way to fix that issue? I tried adding FL1 (from a warez source) along side FL2 in Kontakt 7, but they don't allow it. Any ideas? Should I just keep Portable K6 and 30GB of duplicates?

 

Hi, I just installed Bobdule's Kontakt 7 (latest version, be sure to download the version with the PROPER FIX, Bobdule website isn't updated for some reason so you'll have to download it through other means) literally today lol. Everything went smooth, if you're unsure about the .XLM file Bobdule explains how you can download it in a text file that accompanies the full crack.

It's pretty much like the Kontakt 6 but with a more "modern" interface and a bit faster (at least in my experience). With all the tools that were available in the previous crack.

 

Last edited: May 13, 2024

If it is working this way, I would not even screw with it. I would worry about that when you need the space or if something happens that changes the situation. In Kontaktland, what is 30gb between friends anyway? Sometimes you are better off not rolling the dice.

 

since Kontakt 7 can play on old cpu (7.10.1 and up) there is no reason to keep 6.
only if you have graphic issue with open GL diretX11, and it can be resolved.

Kontakt Factory Library was made for K6 but also run on 7
Kontakt Factory Library 2 was made exclusively for K7
they are 2 differents products. it is a very bad idea to try to mix both.

if you want to replace Kontakt instance in old project.
it is also a bad idea, symply keep a 6 version that match with your project (loading library & automations directlly)
K5, 6 & 7 are 3 differents products with different registration mode.

the wix site is updated on application and fix, i added the full script unlock this weekend.

few libraries are in the older version (for hosting, installer format used, supplying reason)
there is no more iso installer at NI, now native access use separates url's links for every files to copy.

 

The few removed Factory 1 patches I wanted to keep, I just File->Save'd in K6. 30 GiB -> 1.3 GiB.

 

Last edited: May 13, 2024

Install both. I am having success with having latest R2R install of 6 and 7 side by side. The main reason I keep both is that the v6 I have was the last version with the ability to add custom libraries. I am therefore able to add in custom collections, like the Spitfire Albion Collection, using v6 and it then also shows up in v7. I also have a similar thing with a collection of 8Dio, Soundiron, and Tonehammer Choirs collection.

 

Could you find out and share what version of v6 you are using? Thank you.

Edit: Also a big heart to @bobdule. You are the best. <3

 

Last edited: May 23, 2024