It is possible- no issues have occurred.
 
The issue i was having was related to plugin templates and plugins names (when the same template is used in 32 and 64 bit vs.)  It is a problem when the plugins have the same name in 32 and 64 vs. as someone noted below.
 
Generally, Sonar sees the plugins it wants to see, regardless of the contents of the plugin folders.  
 
 
 
 
Will Sonar know which ones to use?  Will Sonar get angry?
 
What about jbridge?   Should I bridge both ways?
I just ordered it and should get it in 24hours or less.
I just watched a video but before I use it I'd like to read the difinitive thread on jbridge.  
Anyone know which of the many it is?

No need to run the JBridger and make the new dlls if you are using Sonar. Sonar supports JBridge so you just need to tell the plugin manager which plugins you want to use via JBridge.

I have just finished a permanent switch to ONLY using 64-bit plugins in 64-bit Sonar.
 
That being said, I did have good success with the 32-bit plugins that I DID allow in 64-bit Sonar, by being careful to firstly test each one I wanted to potentially use in 64-bit Sonar, and once satisfied that a given 32-bit plugin did work OK in 64-bit Sonar (using either BitBridge or JBridge), I moved each 'certified' 32-bit plugins to a SUB-folder within my 32-bit VST Plugins folder.
 
32-bit Sonar will still see those 32-bit plugins, because it automatically sees sub-folders.
 
64-bit Sonar will ONLY pick up the specific 32-bit plugins from the sub-folder holding them, after I added ONLY that sub-folder with the approved 32-bit plugins in it.
 
The above made things quite simple, with no duplication or confusion, or issues.
 
I hope the above suggestion helps clear things up for you - it certainly did for me.
 
Bob Bone

I'm trying to avoid going through all my plugins because there are over 1000.   What I'd like to do is put ALL my plugins in a directory and hope that Sonar and jbridge can make sense out of it.  I guess that's just wishful thinking?

> I'm trying to avoid going through all my plugins because there are over 1000.  
 
Then don't. Just use the plugins your need. If some project moans about a missing plugin add it later. I bet you don't even remember what half the plugins do. Learn to use the plugins you need inside out, when you have run out of learning how to use them only then decide if you need a new plugin, unless you really need a plugin for some missing functionality. If you have 1000 plugins I bet at least 50% of them (maybe 75%) do the same thing.
 
Cheers.

I guess I tend to move cautiously, considering how foolish I would look in front of someone when plugins I toss into a project wreak havoc - as some 32-bit plugins certainly do when put into 64-bit Sonar.
 
I look at that situation as a lawyer might - never ask a question you don't know the answer to.  I no longer have 32-bit plugins to worry about, but I certainly would not want to look like a bumbling yo yo in front of a client, nor would I want to have to redo or recover work.
 
Bob Bone
 

I can't tell what Sonar version James is using and that makes a difference. Sonar X3 has extra options because it supports VST3 and previous versions don't. X3 also gives you the options to use VST3 as a default and hide the duplicated VST2 plugs. The version of Sonar will be part of the solution.

robert_e_bone
I have just finished a permanent switch to ONLY using 64-bit plugins in 64-bit Sonar.
 
That being said, I did have good success with the 32-bit plugins that I DID allow in 64-bit Sonar, by being careful to firstly test each one I wanted to potentially use in 64-bit Sonar, and once satisfied that a given 32-bit plugin did work OK in 64-bit Sonar (using either BitBridge or JBridge), I moved each 'certified' 32-bit plugins to a SUB-folder within my 32-bit VST Plugins folder.
 
32-bit Sonar will still see those 32-bit plugins, because it automatically sees sub-folders.
 
64-bit Sonar will ONLY pick up the specific 32-bit plugins from the sub-folder holding them, after I added ONLY that sub-folder with the approved 32-bit plugins in it.
 
The above made things quite simple, with no duplication or confusion, or issues.
 
I hope the above suggestion helps clear things up for you - it certainly did for me.
 
Bob Bone

To be clear I agree with this should you wish to spend the time (looks like you don't though). Get rid of useless plugins and plugins you won't need though. Get your plugins out the PROGRAM FILES folder I would suggest as well (in order to avoid permissions issues). I had to do this myself although I didn't have as many plugins. Spend a day on it. Otherwise #5.
 
No pain no gain!

i run X3d.  
i don't use old plugins in new projects- why would I?
Yes many of the plugs do the same thing but they are loaded in old projects by the dozens.
 All of you are being very kind chiming in, but what I'm trying to discover is whather I can have all my plugins of ALL varieties, 32, 64, vst2, vst3, all in one big folder!  Then, use that folder in both 64 and 32 bit sonar so that i KNOW it contains every possible plugin I own.   I'm hoping the software is smart enough to ignore the plugins that aren't compatible but they will be available should a project require them.  I promise I will not use them in a new project!!!
 
Is this possible/advisable?   Has anyone tried it?  
 
If I have to spend a day sorting through, i will.   but i will NOT like it.

We are not telling you that you HAVE to sort through all of them.  Ultimately, you are in total control of however you want to do it.
 
I posted above because some 32-bit plugins DO cause problems in 64-bit Sonar, both with BitBridge and with JBridge, and I gave you one way around that - should you choose to follow it.  I do not have the volume of 32-bit plugins that you do, so for ME, certifying mine was no big deal.
 
An additional method is to do as you were inquiring about - throw them into one giant folder.  I would never choose to do that myself, but it is your planet.  PLEASE NOTE that this would be to access both 32 and b4 bit plugins in 64-bot Sonar.  I would NOT recommend making your 64-bit plugins available to even be seen in 32-bit Sonar.
 
A third choice is to add your 32-bit plugin folder paths into the search path for 64-bit Sonar, which would let 64-bit Sonar 'see' all of them, but would still keep them separate, for possibly weeding them out at some later time, or if there are issues or whatever.  With THIS method, both 32-bit and 64-bit Sonar would see all of the plugins that can potentially be used.  64-bit plugins would not be seen by 32-bit Sonar, but would of course be seen in 64-bit Sonar, AND all of your 32-bit plugins would also be seen in 64-bit Sonar.
 
Any of the above choices are doable, you just have to reason through what makes the most sense for you.
 
The X3 Plugin Manager was revamped, and does a nicer job of presenting/managing/incorporating all of your plugins.
 
Bob Bone