vst 32 BIT/64 BIT same partiton and plug in manager issues

This may have been broached before , but a search of the forums didnt result in anything specific.

Let me lay the groundwork

I have Win7 64 bit, Sonar X164 and X1 32 bit on same drive

I have separate folders for the Native 64 bit VSTs and the 32 bit ones.. Some of the VSTs have the x64 designation behind them, some like IK dont.

The 64 bit cakewalk ones under program/ sonar/VST
a separate 64 bit folder in program

under programx86
the 32 bit sonar/vst
32 bit vst

The issue I am having is that in the plug in manager even though it appears to be the 64 bit one, when I click on plug in properties in the "found" window the path shows the 32 bit location.

I tried setting up from scratch a new scan with just the 64 bit folder, and creating a plug in profile named 64 bit and adding the 64 bits. Well that worked fine

Then , I deleted the 64 bit locations, added the 32 bit locations, and created a 32 bit profile and scanned . That worked OK.

Unless I added the deleted 64 bit locations after all was done , now the 64 bit references were gone. Even when I added them back, I had to do another scan for them to be synced, and this is where the above problem with the 32 bit path showing up..

I also have Jbridge and some of the 32 bit ones are showing up Jbridged.

I want to be able to use both Versions of sonar from the one partition, but since they appear to share a common plug in manager shared location ,this may be a problem.
I am wondering if I could have a different location for the plug in manager for my 32 bit Sonar and the profiles stored there for just the 32 bit VSTs?My 64 bit Sonar would also have its own plug in manager location and profile folder, and maybe copy the 32 bit VSTs to a different location to be jbridged/bit bridged?

There are 2 different Plugin Manager programs or at least there should be. each one is accessed from within the particular version of SONAR you are running.

here is some useful info for running both versions of SOANR and setting up plugin folders which seems more like your problem.

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's VST Scanner and you have 2 of that plugin appear in each version of the Plugin manager ie the 32 bit and 64 bit Plugin manager. That's right; there is a Plugin manager in both the 32 and 64 bit installations of SONAR.
 
To get around all that I have my system setup as follows.
 
I have an additional folder just for 32 bit (x86) plugins for those 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 I 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.

Shouldn't X1 32 bit ignore 64 bit plugins? I thought it did but I don't know for sure. I have not run 32 bit Sonar in so long that I can't recall what it does. Any folder that has a mixture of 32 and 64 bit plugins should not present a problem. Not that I know that for sure. I do try to separate them but I can't say for sure I have. Because 64 bit X1 can use either I haven't noticed any problems.

Jim. when I came home and fire up my PC indeed there are two separate plug in managers, one in the 64 and one in the x86 folders, BUT they were sharing the plug in manager profiles under a common  Roaming folder,
So I created a separate folder for the 32 bit folder in the roaming folder and set up the 32 bit vst folders for the sonar 32 bit , and 64 bit vst for the 64 bit sonar.
NOW , I need some thoughts on jbridging the 32 bit vsts into sonar 64 bit.
I would create a third folder to include the 32 bit vsts to be jbridged, let jbridge scan only those and put its results in a separate jbridged output folder.
First, I have to ascertain which 32 bit vsts have to be bridged to include in the to be scanned folder by jbridge, then im unclear as to which folder to include in the Sonar plug in manager scan.
I see there is a checkmark on properties of a vst to make it jbridge ot bitbridge capable. so now i am further confused.

The instructions with jbridge are as clear as mud..It says create a seperate folder for the bridged plugs..
So my quandary as I understand from reading many many posts
for sonar X1 64 bit:

64 bit vsts plug right in
SOME 32 bit may work
some 32 bit need to be bridged but after running the jbridge conversion what folder do I include(if any) in the scan? do I omit the "dont work in 64 bit plugs"? 32 bit vsts and scan the bridged counterparts?