How can I recover instrument setting from an instance on KONTAKT 6 - if I just installed KONTAKT 7?

JordanVanderwerf

I think I may have just screwed myself here..

I have a project with multiple KONTAKT instruments, Asian, middle east so so on..

I had them loaded VIA Kontakt 6 player, I had made some small adjustments to each instrument, y'know refined them to my liking..

Then... I went and installed Kontakt 7 in the native access app.. and now that I've loaded my project again, every one of my Kontakt 6 INSTANCES are disabled and I'm unable to find where Kontakt 6 went haha..

I had thought that I might be able to use kontakt 6 and 7 seperately but apparently NOT.. haha

I will probably never update S^&^* again until the project is finnished.. DANGIT!! please help!

Thank you!!!!!!!!!!!!🤣

JordanVanderwerf

My god... I figured it out! &^&*ME😜

okay. I still think this is a very valid thread. so here is the answer. (Albeit still kind of annoying and not 100% satisfactory.)

with this, I was able to switch my "custom" VST3 folder location through Ableton, to this stupid UNCHANGEABLE dedicated folder. - This reinstated the instances I had saved on my project and will allow me to complete this ONE project.

The only problem I find with this, is because I've got most of my other VST3's saved onto my 2nd hard drive in a special location. they are now not accessible at the same time and this Native Instruments "Dedicated" folder. I will have to switch back and forth OR move all my VST3's (basically all my VST2's as well..) over to this "programs, common files, VST" bologna...

Well... I am praising hallelujah😭 that I have figure out THIS CURRENT PROJECT.. but some how I am now totally terrified to open any older projects that still need work.. for fear that I will not be able to use my other 3rd party VST3's at the same time as all my Kontakt libraries..

Life goes on.. I'm so incomplete.. hahaaa eemooo😂

JordanVanderwerf

Furthermore, what the hell is the difference between 64bit and 32bit, I mean, I know the difference actually.. but WHY does Native Access, only allow you to decide where to put 32 vs 64? shouldn't I be able to decide where I put my VST3 vs my VST2???????? the F%^%^&.. or are they talking about 32/64 as if it was VST2/VST3????? whyyy

Does not both VST2/3 come in 32bit and 64bit?

Native instruments is infuriating.

JordanVanderwerf

My god... I figured it out! &^&*ME😜

okay. I still think this is a very valid thread. so here is the answer. (Albeit still kind of annoying and not 100% satisfactory.)

with this, I was able to switch my "custom" VST3 folder location through Ableton, to this stupid UNCHANGEABLE dedicated folder. - This reinstated the instances I had saved on my project and will allow me to complete this ONE project.

The only problem I find with this, is because I've got most of my other VST3's saved onto my 2nd hard drive in a special location. they are now not accessible at the same time and this Native Instruments "Dedicated" folder. I will have to switch back and forth OR move all my VST3's (basically all my VST2's as well..) over to this "programs, common files, VST" bologna...

Well... I am praising hallelujah😭 that I have figure out THIS CURRENT PROJECT.. but some how I am now totally terrified to open any older projects that still need work.. for fear that I will not be able to use my other 3rd party VST3's at the same time as all my Kontakt libraries..

Life goes on.. I'm so incomplete.. hahaaa eemooo😂

EvilDragon

It's not unchangeable... You can change the plugin folders to which Native Access installs things, in Preferences...

VST3 by definition from Steinberg has only one fixed system path. Some DAWs don't allow you to change it. It is always going to be C:\Program Files\Common Files\VST3.

earthom

I have the same problems. I'm beginning to understand them, but it's taken me a long time, not least because of support that didn't know what to do for a long time. But now it's too dangerous and expensive for me to migrate all the tracks of the libraries used in my projects from K6 to K7, or to uninstall K6 as suggested by support. I don't trust Cubase's 'auto migration' that easily! I have far too many projects, tracks and libraries. So for the time being, I've decided on the following solution: I've uninstalled the updated versions of the libraries and reinstalled the older ones – a downgrade, in other words. [Here is the link to the older versions: Previous versions of recently updated Kontakt libraries / compatibility with K6 older libraries — Community (native-instruments.com)Another solution would be to take snapshots of the relevant tracks in K6, duplicate the tracks and access the snapshot in K7. But: for me, with orchestras, a wide variety of tracks just for different articulations, that's a huge amount of work... it's out of the question! I very much hope (and actually expect!) that NI will provide an update for K6 instead, which could solve the problem. As a customer, I don't feel properly understood if this is all there is, because I have significant disadvantages:

• It is a lot of work, and in my view unreasonable, that we are all supposed to do here now, since we have always been able to expect an updated library to be compatible with older versions of Kontakt.
• With the 'temporary solution' I've implemented, I will never be able to update the libraries that I'm using in one of my projects in K6 on my computer. So I'm giving up two things: updated libraries and the K7 – in all my future and already created projects with these libraries. And this is multiplied by all users... ;-/

Dear fantastic creators and tinkerers at NI – we've loved your products for almost 30 years – continue to make us proud and happy, please! 😉