Kontakt5 not working as a plugin in X1

I can get Kontakt 5 and my Steven Slate Drums library to work just fine as a stand alone outside of Sonar. My problem is that when I choose Kontakt 5 in Sonar as a plugin and try to load a drum set in Slate Drums, Kontakt and Sonar freezes. But if I go into Cakewalk plugin manager, choose Kontakt, then plug in options and check the box to engage the JBridge plug in wrapper, Kontakt works fine but seems to use quite a bit of CPU. However, why in the world would I need to use JBridge if Kontakt is 64 bit compatible on my Windows 7 64 bit OS running sonar 64 bit? And why does Kontakt work just fine as a standalone outside of Sonar?

Did it matter what folder I installed Kontakt in? I installed it in the default folder which is: %root%\Program Files (x86)\VSTPlugins. Is Sonar seeing this folder as a 32 bit environment? Does the (x86) mean Sonar is seeing Kontakt as a 32 bit plug in even though its 64 bit? 


Should I have installed Kontakt into this folder instead? : %root%\Program Files\VSTPlugins 


I'm confused. Anyone have any suggestions?


Thanks!

%root%\Program Files (x86)\VSTPlugins is for 32 bit plugins.

%root%\Program Files\VSTPlugins is for 64 bit plugins.

I would start by correcting the installation directory.

KEv

Thank you both for the tips. I will try a new install making sure I load Kontakt into the proper directory to see if that solves the problem.

 
Yes, you're currently loading the 32Bit Kontakt VST Plugin dll.
The tip-off was that it was installed under Program Files (x86)
 
I like to have separate VST Plugins folders for 3rd party plugins.
(As was mentioned above)
 
C:\Program Files\VstPlugins_64Bit
C:\Program Files(x86)\VstPlugins_32Bit
 
When running a 64Bit OS, you really have to pay attention to where the plugin dll files are being installed.  There's absolutely no standardization.  If you accept the default locations, you'll wind up with a mess.  Using the above, it's quick/easy to confirm the plugins are being placed in the correct folder.

You all were correct! Since I don't use 32 bit in any environment I got rid of the 32 bit .dll files related to Kontakt. I was having trouble with my BFD2 drum software as well since BFD came out with a 64 bit beta update. I got rid of the 32 bit .dll BFD2 files as well. Reinstalled both plug ins into %root%\Program Files\VSTPlugins  and have now achieved full 64 bit.


Thanks everyone for the help!

Most DAWS insist on their own location for plugins by default. Fortunately SONAR allows you to be very flexible in where you put plugins BUT there are some reasons behind the default locations.
Windows (x64) itself seperates 32 bit and 64 bit programs into different folders as follows.
64 bit programs by default go into C:\Program Files - while
32 bit programs by default go into C:\Program Files(x86)
I decided to stick with SONAR's default locations but I also understand that there are some weird things that happen because plugins themselves don't always conform to a standard of behavior let alone standard installation locations.
I've chosen to do the following. You can apply the principles but use a different folder structure if you prefer.
 
Depending on how many 3rd party plugins you might have and how co-operative they are you may find the following useful. If it doesn't apply to you feel free to ignore it or use only any bits useful to you.
Having both the 32 and 64 bit versions of SONAR on the same computer doesn't of itself cause any problems. Many of us run multiple version in both 32 and 64 bit without problem.
Problems can however occur when you tell SONAR to scan for VST plugins. when running 64 bit SONAR there may be 32 bit plugins that you want to run because a 64 bit version doesn't exist yet. That means having to scan the location where those 32 bit plugins are as well.
That's not a problem either except that when using 32 and 64 bit versions of SONAR you may want both the 32 bit and 64 bit versions of a particular plugin so each program can make use of it. The rub is that some plugins don't behave and you end up with both the 32 bit and 64 bit version being scanned by SONAR x64's VST Scanner and you have 2 of that plugin appear in Plugin Menus and the Browser window. There is a Plugin manager program in both the 32 and 64 bit installations of SONAR.
 
To get around that problem if it occurs, I have my system setup as follows.
 
I have an additional folder just for 32 bit (x86) plugins where the manufacturer wants to always install both a 32 and 64 bit version. When it works properly then the 64 bit VST scanner doesn't load the 32 bit version but when it doesn't work properly it means you end up having 2 of the same plugin where the 32 bit one is also running through  Bitbridge. For those plugins only I use the 3rd folder. Working out which plugins don't cooperate has to be worked out by trial and error.
1. Program files\Cakewalk\Vst Plugins\Manufacturer\plugin
All 64 bit Plugins
2. Program files (x86)\Cakewalk\Vst Plugins\Manufacturer\plugin
All 32 bit plugins you want to run in x64 because no native 64bit version exists.
3. Program files (x86)\Cakewalk\VST Plugins(x86)\ Manufacturer\plugin
All 32 bit plugins for which you already have 64 bit versions and the VST scanner insists on installing the 32 bit version as well under bitbridge giving you 2 copies of the same plugin in SONAR's Plugin manager.
SONAR x64 scans 1 & 2
SONAR x86 scans 2 & 3
Apart from folder 3 the others are all default locations if you allow SONAR to just perform it's normal installation.
 

I didn't think *.dlls could be moved?
(especially stuff like Native Inst., or spectrasonics).
yes, no?

You can often move the dll without problem.

 
As long as you re-point (or add) the new location in plugin manager.  
 

jbraner


Mike,
 
I guess I've been lucky, but I've never had a problem with scanning both versions (32 bit and 64 bit) of plugins. Of course, I use my own menus - and I just make sure the 64 bit versions are the ones I've got available to me.

I was speaking more  from past than current experience. I still have SONAR 8.5.3 (x86) installed for 1 MFX plugin that I can't make work in SONAR x64 of any flavor so for that I have 32 bit plugins installed as well. Apart from the rare occassions I use that 32 bit MFX plugin I am 99.9% 64 bit so the plugin issue doesn't occur because of the way I am setup. For some folks however their reliance on 32 bit is still very important and I've just found quite a few plugin vendors whose implementation for 32 and 64 bit plugins could be a bit screwy. Hence my warning. Sadly as I mentioned there is only trial and error to fall back to when trying this stuff out. I still use a lot of 32 bit plugins in my 64 bit system but bridge them all using jBridge exclusively. I even use a lot of 32 bit DX's that I use through an old (No longer in development) 32 bit VST plugin that when bridged allows 32 DX's to be used in a 64 bit host. An invaluable tool in using some of Sony's very powerful plugins which are all in teh DX format.
 
Perhaps now that 64 bit is becoming more widely adopted they all play nicely together which would explain your experience.
 
Another variable for me was that I often reviewed plugins as part of various testing work I used to do and so had literally hundreds of plugins on my system. Often poorly written creating conflicts of all sorts. With that sort of work I had a parrallel installation that was quarantined on its own partition and not used for day to day recording work. These days that is a greatly reduced plugin list which only amounts to scores rather than hundreds.