Kontakt 7 Pro Tools

[Jessia Adachi]

Ive seen this problem before and I know many other people have had the same issues. I've got a Cakewalk project that's two years old that I want to remix. Over the past two years I believe I moved the vst folders and probably have reinstalled Kontakt again for whatever reasons. I was probably only using version 5.8 on this project at the time and not version 6. Bandlab is currently updated with the latest version.

Now I have Kontakt version 5.8.1 and version 6.6.0 installed. Everything works fine on new projects using either of the installed versions. I recall having vst errors with Kontakt in the past or else it loaded but there was no sound. The easiest solution seemed to be to reload a new Kontakt synth plugin with the same library and redirect the old MIDI to the new plugin. I would then delete the old Kontakt synth plugin. I couldn't be sure I had the same plugin settings if I didn't have a configuration file saved to reload. It was a slight pain but it got me up and running again quickly.

This two year old project has about 90 tracks and a lot of them are Kontakt plugins. I don't want to jump through hoops getting this running again if I can avoid it. I can insert a new Kontakt plugin and use the same library as I did two years before and it works fine. So the problem doesn't seem to be with the Kontakt plugins I used before not working or being 'found'. It seem that Cakewalk is now confused and associating the plugin to a previous folder location or Kontakt version or perhaps something else.

The best solution I can think of would be to recreate the original paths using symbolic links. This, however, requires that you know the original locations of the Kontakt executables, and possibly also the original locations of the libraries if they've also been moved.

The beauty of symbolic links is you can move programs and data to a new file location without the DAW or VSTs knowing you've done it. They continue to look in the previous place and the Windows file system quietly redirects them to the new folder. But again, this fix does require that you first know the old pathnames.

I'll look into that as a possible solution. I believe I know where the vsts were located before. In fact, they might not have even moved. I can guess where Kontakt might have been located before pretty easily.

Alternatively I could simple copy the two Kontakt .dll files for 5.8 and 6.6 to every location Cakewalk is currently searching for vst files. That wouldn't be too difficult. I don't think they've changed recently. My hunch is it's the Kontakt locations and not the vst library locations that's causing the problem.

I've mentioned in other post how much I dislike Kontakt for several reasons. Starting with the horrible interface it just seems like a terrible tool to be an industry standard. I try to use any other plugin I can if I can avoid using Kontakt these days so it doesn't come back to haunt me. I only seem to have these kind of problems with Kontakt.

You create a symbolic link using the mklink command, which you run in a DOS window. This command creates a pseudo-folder that's actually a pointer to somewhere else. Let's say you have a project that references c:\VSTGone\VSTGone.dll, but either that DLL isn't there anymore or the whole folder is gone because it's been moved to the D: drive to free up space on your system drive. You can use mklink to create a fake c:\VSTGone folder, and tell it the real location.

Let's say Kontakt was originally installed at C:\program files\Native Instruments\Kontakt but that folder's no longer there, and has since been moved to D:\Kontakt. In this case, you'd use mklink to create a dummy folder that points to the actual location:

Now you have a pseudo-folder named c:\program files\Native Instruments\Kontakt. Any program that references it will be automatically redirected to D:\Kontakt. This happens at the file system level, so Cakewalk need not know of this sleight-of-hand and existing projects need not be modified.

Is the problem really that Cakewalk has a project which previously found a Kontakt version 5 or 6 before and now that location has changed? Shouldn't the fact that Cakewalk can insert either version of these plugins currently because they've been scanned be enough to open the old project? I'm not sure I understand why moving a plugin's location would cause this error. I can insert either version of Kontakt with the old plugin with no problem. My only concern is if I changed any settings of the plugin and don't have a configuration saved for that tune.

Another example is that I have a similar problem when I load an old project with a FabFilter vst or Amplitude 4 vst. The 'vst missing' error message pops up when loading but as soon as the project is finished loaded I can simply insert either plugin with no problem. My question is what confuses Cakewalk into believing a plugin is missing when it can obviously load the same plugin it griped about?

If I couldn't successfully insert Kontakt, FabFilter, Amplitude 4 or whatever without the 'missing plugin' message I would believe there was truly a problem on my side. The fact that they all load with no problem with new projects or after old projects are loaded confuses me.

I would think the Cakewalk/Bandlab crew would have some kind of tools to help straighten problems like this out. What can they see inside a project that we can't? I tried a Projectscope utility mentioned in another post but it didn't have the information needed.

You can find the paths to plugins - as Cakewalk understands them - by looking in the system registry. Open REGEDIT and press F3 to pull up the Find dialog. Search for Cakewalk Music Software. Under that key will be a subkey called Cakewalk VST x64, and within that another subkey named "Inventory". Lots of information in there, some of it obvious, some of it obscure, but worth an examination.

That method works to locate registered plugins, meaning all plugins that were found and successfully initialized by the VST scanner. It won't help you find duplicate instances, though. I usually resolve that challenge with a global search, but I don't use the Windows Search feature because it's so slow and doesn't produce results I can refine my search within. Instead, I open a DOS window and run something like this (in this example, to find all FabFilter plugins):

This will create a file called fabfilter.txt that lists every DLL named "FabFilter[something]", and then open it in Notepad. To find every instance of Kontakt, just substitute "kontakt" for "fabfilter".

I think it's time to give up and just reinsert the plugins again. I think I didn't change the presets on these instruments and I can get the volume and efx info from the old audio output that's not working. The MIDI is there and I just have to appease Cakewalk as quickly as possible and get back to work.

I did do plugin scans several times including re-scanning all plugins. I know the plugin Cakewalk is looking for is in one of the scanned folders. That's the frustrating part. What can cause this error if the plugin is actually there and I can insert it myself after canceling the 'plugin not found' error messages? I think that's my main question. Different vst version number? 32 vs. 64 bit version used in the project??

Thanks a lot Wesley.

This path was actually the problem : C:\Program Files\Common Files\VST3

Even uninstalling the program, Native Instrument keeps a big file (?!??) named kontakt.vst3 which contains the entire hidden Kontakt Player 6 software.

Removing it was the solution.

HAVOC is the ultimate cinematic percussive suite of over 850 instruments and multis that will transform the tools of your trade. The HAVOC sample collection has been derived from hundreds of industrial machines, farm tools, everyday auto body parts and gears, all recorded in a massive multi-car garage.

Wood, plastic, metal, and glass are among the many organic materials used, twisted, and morphed into HAVOC. From saws and chains, to buckets and drills, anything and everything one would find inside a garage was recorded. Why not bring these tools to the recording studio? Instead, HAVOC brings the recording studio to the garage. Everything was recorded in their natural habitat (a massive 24-car garage), the result of which was amazing acoustics and natural reverbs culminating in bigger and more cinematic sounds!

Kontakt.io is the industry leader in indoor environmental, location, and occupancy services using Bluetooth Low Energy (BLE ). Our mission is to deliver human-building interfaces that provide people with delightful, useful, and safe indoor experiences to help make buildings work for people. We are out to define a new building DNA that is human-centric. We build technologies that help transform buildings into indoor spaces that are useful for people in their daily journey to accomplish their goals, working or being cared for in a safe & sustainable indoor environment.

We started in 2013 when Kontakt.io built the first enterprise-graded BLE beacon solution for building-mobile interfaces. Since then, we have provided BLE solutions to over 30,000 end-users, delivered via +1,100 partners using +3 million IoT devices in the field. Today our solutions cover approximately one billion sq ft. We continue to be a pioneer in the field, with a focus on Smart Buildings in Healthcare and Corporate Real Estate Spaces.

Success in this position requires a passion for building high-performing and reliable applications. You need to have an internal urge to come up with innovative ideas and look for the best tools to solve scalability problems.

-Easy to Deploy. Using AI, cloud, and mobile technologies, our equipment autonomously communicates and validates itself without the need for human intervention, cutting deployment time from months to weeks or even days.

-Outcome Driven. We deliver outcomes, not boxed equipment. From on-site installation to monitoring, all the way to service-level agreements, our approach is uniquely designed to ensure the outcomes you need.

3a8082e126