Hey all,

I was wondering if its possible to have a shared LIB tab for different versions of Kontakt. I run the v6 portable as well as 5.73 in my system. I've figured out how to share the quickload between them using symbolic links but can't seem to figure out how to share the libraries tab. I'd like to avoid having to add my libraries more than once.

Thanks.

 

I have both symlink Kontakt 5 and no install Kontakt 6 installed and they run together fine and all libraries are synced between them. The way I did this is I installed symlink Kontakt 5 first normally and then just dropped the Kontakt 6 dll in my vst plugins folder and it just works, never had any issues, then I add libraries through the exe provided with symlink install and they all appear in both versions.

Hope this helps.

 

That's exactly what I'm trying to accomplish. I'm trying to understand how you did it though. So you're not using the library manager from 6 at all? the library manager that comes with 6 is more robust than the v5 one so I was hoping that would be the 'base' folder and that 5 would read from it. Where do the apps keep their library info? maybe I can make a symlink to 6's library info and move it to where 5 stores its info.

 

C:\Users\Admin\AppData\Local\Native Instruments\Kontakt 5 I think this is where it stores the data on my PC, you might try looking there. But other than that I can't really help. I've had K5 symlink installed for like a year, when 6 came out I was too lazy to install it normally so I just dropped the dll to my plugins folder and it was just an accident that worked and I never questioned it. Perhaps because I've never installed K6 on my PC it gets all the data from K5 installation. Try experimenting or wait for someone who knows what they're doing to reply.

 

Thanks. That's where I created the symlink to the k6 quickload....but I can't seem to find where the contents of the library tabs are stored in order to create the symlink. Any gurus help would be appreciated.

 

The keyword here is "Portable" that you mentioned. It has an isolated structure, you can't share it easily. Other non-portable versions share the same environment and uses the same Service Center location, therefore you have the libraries there the same way in different Kontakts (apart from the missing onces due to compatibility).
Whether copying the content of the Portable's Service Center to the other version works, it needs to be tested but mind you that there are .xml files there that begin with the name Kontakt, you should keep those on the original location, just copy the libraries' .xml
(And also you would need to copy the .plist files for the libraries.) <-- Edit: sorry, that is only on mac, on windows it's in registry, so I find it more dangerous to deal with.
I still think you should rather add the libraries in that other Kontakt if you don't want to screw everything.

 

Last edited: Feb 21, 2019

That makes sense. I guess the quickloads will be shared while the libraries will be on a version. Just didn't want to through the hassle of organizing the tabs twice.

 

So if I am reading this correctly, If I had created a quick load structure in K5 and installed K6 they will ready the same quick load info cause they share the service center data...is that correct?

 

No, that's wrong. Quickload isn't saved in Service Center but in Kontakt 5 folder in a location I don't recall now for windows, and when you install Kontakt 6, it will create a new library which is called "Kontakt" and you have to copy the quickload contents from the Kontakt 5 folder.
Let us know which platform you use (win or mac), so we could give you the info about the exact location.

 

I have a quickload folder at c:\users\user\AppData\Local\Native Instruments\Kontakt 5

What I did was make a symbolic link from my K6 portable folder and dropped it in that location so that when I save a quickload from k5 OR k6 it saves in the same folder.

 

I was just wondering why you need both versions.

 

I generally keep an older version of the app on after upgrading to a newer one just in case the newer one doesn't work. But as projects start I'll load up VEP's with the older one while filling my new templates with the older one. The process of switiching over to the newest one usually takes me a little while.