Issues with Kontakt 7 update & subsequent 32-bit software discovery

Papa Bach'ish · 2023-10-04T09:39:41+00:00

There was an error rendering this rich post.

We have 2 x HP Z440, Intel(R) Xeon(R), CPU E5-1603 v4 @ 2.80GHz, 2.80 GHz 64-bit operating system, x64-based processor

Other than 128Gb vs 32Gb memory, the machines are the same. Software setup is very similar, creating PC redundancy, when required.

We are running;

Cubase 12, Vienna Symphonic Library (VI Super Package) & Dorico 5

Native Instruments S88 keyboard Mk2 & few third party libraries within the NI environment

Our issues began when we finally started installing some of the Komplete Kontrol 14 libraries.

The process included upgrading Kontakt 7 version 7.1.5 to version 7.6.0.0.

This upgraded resulted in “Plug-in not found”.

We eventually installed Revo Uninstaller to remove the offending software, but noted that other than Native Access 3.6.1, the seven other Native Access programmes, drivers and such currently on the machine are 32 bit. I am sure this is the essence of our issue, but none the wiser to resolve this issue. Multiple attempts to reinstall in 64 bit remains futile.

Find more posts tagged with

Komplete

Comments

Vocalpoint

"We eventually installed Revo Uninstaller to remove the offending software, but noted that other than Native Access 3.6.1, the seven other Native Access programmes, drivers and such currently on the machine are 32 bit. I am sure this is the essence of our issue, but none the wiser to resolve this issue. Multiple attempts to reinstall in 64 bit remains futile"

Just checked my install (Native Access 3.6.1) and yes - while there certainly is a 32bit folder location you can set under Preferences - when I go into that "32 Bit" location here - there is only a single instance of the (now very old) Absynth plugin (circa 2015)

Everything else (easily 100+ other instruments etc) are all in the 64 bit location.

Also - there is no ability to "instruct" Native Access what "flavour" of plugins (32/64bit) to install.

It's all 64 bit these days.

Where exactly are you seeing this "Plugin not found" message? In NA or in Cubase or where?

Papa Bach'ish

Error Message.png

Thanks VP. The 32 bit is read off the Revo App and could in itself be incorrect.

As for the actual issue, the error is within Native Instruments. Cubase 12 is working perfectly with all other libraries. All is working well with the older version of Kontakt 7. I removed all and loaded the new Native Access, but sadly, the issue remains.

Vocalpoint

"As for the actual issue, the error is within Native Instruments"

Have seen this one before and it is coming from a missing path in the library tab. You will need swing in there and verify ALL the paths (or add some) that Komplete Kontrol is scanning.

If you still are having issues - another more "nuclear" option is to completely rebuild the KK database - steps are here:

My KOMPLETE KONTROL Browser is Empty or Incomplete – Native Instruments (native-instruments.com)

I remember doing this last year after a pile of weird issues and this is the only way to really reset everything - but you have to ensure that ALL your plugins are in consistent places on the hard drive.

POWER TIP: When I install ANY plugin - I never allow the installer any choice on what to do - I force every install and ensure the installer installs to these (and only these) specific locations:

C:\Program Files\Steinberg\VSTPlugins

C:\Program Files (X86)\Steinberg\VSTPlugins (rarely - if ever - used as I do not allow 32bit plugins on my system)

C:\Common Files\VST3

The "Steinberg" references are an old habit from long ago - but these three locations MUST be present in all apps (like Komplete Kontrol or Native Access) from my plugin stash to work properly.

There are no other possible locations to install to.

Update when you can.

Papa Bach'ish

What you are saying is making sense and was pretty much our first plan of action. We believe all the paths are as intended and correct. I'm aware of this as the libraries themselves are very large and I would not dare load them on the OS drive. This has been working and remains so on my machine.

These are the locations that are set up for NI and to my thinking are consciously correct.

C:\Users\Public\Downloads

C:\Program Files\Native Instruments

E:\ORCHESTRATION\Library

C:\Program Files\Native Instruments\VSTPlugins 32 bit

C:\Program Files\Native Instruments\VSTPlugins 64 bit

The other thing that is troubling us, since the update of Kontakt 7 version 7.1.5 to version 7.6.0.0, Kontakt 7 can no longer open as a standalone. I would like the opportunity to uninstall all the NI Apps on that machine and try again with Kontakt 7 version 7.1.5.

Do you know if that is possible?

In the meantime, when this flu is a thing of the past, I will careful work through your instruction above and hopefully resolve the issue.

Thank you in the interim.

Papa Bach'ish

Before running through the instructions you gave me; viz

My KOMPLETE KONTROL Browser is Empty or Incomplete – Native Instruments (native-instruments.com)

I checked for new updates. Last week I had reinstalled all NI software including the latest version of Native Access (3.6.2). All that was available for update today was the latest version of Controller Editor (2.8.2). I think this is what updated, by I could be mistaken.

The bottom line, Kontakt 7 opened as a standalone and without rebuilding anything, all issues appear to have been resolved.

We can now move the keyboard back to that computer and ensure it is all definitely working, but it all looks correct and resolved.

Thanks once again.

My suspicion, it was an update issue that was finally resolved.

Vocalpoint

Firstly:

C:\Users\Public\Downloads (ignore this)

C:\Program Files\Native Instruments (and this)

E:\ORCHESTRATION\Library (and this)

C:\Program Files\Native Instruments\VSTPlugins 32 bit (this is suspect)

C:\Program Files\Native Instruments\VSTPlugins 64 bit (and so is this)

The first three entries here (assuming these are from the Native Access Preferences Area0 - have nothing to do with plugins. The next two however are very important - and while these paths "seem" cool - they are VERY NI centric - which most of us would override in the real world so ALL our VST plugins are in one spot - and to ensure we do not need to add 20 obscure locations to our DAWs when we tell it where to find out plugins.

In your case as long as these oddball paths are correctly entered in Cubase as a VST location - it should be good. But again - this is not a default VST plugin location for most developers and just one more location you need your DAW hosts to remember.

If I were installing my DAW - clean - TODAY - these would be my locations and the only locations that any plugin would ever be installed to:

C:\Program Files\VSTPlugins

C:\Program Files (X86)\VSTPlugins

C:\Common Files\VST3

I am assuming its a bit late for you to start moving things now - but try to keep the locations central and to a minimum. Makes it much easier for troubleshooting.

Papa Bach'ish

My son is the composer and I am assisting him in researching hardware and software and then establishing first a recording setup for his piano and now a production studio to produce a range of music. We started with Cubase and the Vienna Symphonic Library. This year I purchase the NI S88Mk2 and established the production setup. Only recently did we purchase the big NI library. In the interim we had purchased a guitar library to add to what he had in VSL. We are both new at this and only happy learners. While I probably won't change the 2 x machines now, I am planning a new machine for him with more space and a clean, better setup. All learning is welcome and I do like your thinking. (I generally I avoid changing default locations unless it really makes sense), but unless I'm mistaken, the 5 paths are default, save for the E drive. That was very specifically intended to keep the full library installations off the modestly sized OS solid state drive and move the very large libraries to the much larger data drive.

Once again, your assistance is greatly appreciated and I will continue to design the ideal setup for the new machine.

PB'ish

Vocalpoint

"I generally I avoid changing default locations unless it really makes sense"

Well - it does make sense to override all plugin installers every chance you get. Vendors all tend to think they are helping you in some way by promoting their weird locations - but it only leads to madness especially when introducing all these paths to your DAW apps.

If I allowed vendor path suggestions to stand - I would have to add 20 directories to Studio One, 20 to Komplete Kontrol, 20 to Wavelab and so on.

As mentioned - regardless of plugin - they all go into the locations noted above.

And I do the same with my large libraries - nothing ever goes on C:\.

Over here all big libraries (Native Instruments, Spectrasonics, Toontrack etc - go on my S drive and all sample libraries, one-shots, loops etc are parked on the T drive.

Papa Bach'ish

Once again, thank you for all your assistance. My son and I are just over a year into our production studio setup and just over half a year into the NI S88 keyboard. Hard to imagine having even started without that, but as much as we had researched and build from the ground up, you do have to ultimately start from somewhere. Much to learn and most importantly, much to learn in terms of global design and thinking.

Thank you once again and we look forward to building on our knowledge. We feel we have done well so far.

Thanks

PB'ish

Quick links

Unanswered questions