My plugins are 32 AND 64 ?? Plugin Layouts

Plugin manager is kind of a nightmare.  I'm installing both the 32 and 64 bit versions of some plugins (into different folders accordingly) such as Rapture for backward capability.
 
If I look at the VST instrument plugins in Plugin manager, clicking on the Rapture points to the file c:\program files\steinberg\Vst Plugins\rapture.dll
 
If I click on  properties for that very plugin, however, in the details, it claims to be pointing to the c:\program files(x86)\steinberg\Vst Plugins\rapture.dll
 
Same plugin selected the entire time.  Most of the plugins have a popup "About" but it rarely tells you if you are using the 32 or 64 bit version.  What is the point of even installing the 64 if it is entirely up to chance as to which one it is actually using?  I'd like to be able to label them so when I add a plugin to a project I know if it is the 32 or the 64 one I am adding, but that's how I discovered the issue above.
 
It is not clear how to set a plugin profile as the default, so I either have showing an incomplete profile (doesn't include newly-added ones) or my organized subset of plugins (that I want visible) that are incomplete after scanning for new ones (I have to add them in manually for both my 32 bit Sonar and my 64-bit Sonar).  That is a bunch of steps for each time you add a new plugin.  Since I am re-adding/re-loading all my plugins on my new machine, this process is major drudgery.  32 Bit Sonar Scan, organize, save profile, then 64 Bit Sonar Scan, organize, save profile.
 
 

Pretty much as Randy is describing but I alter it slightly as like you I have both Sonar 32 and 64 bit versions installed.

I created a 'VSTPlugin' Folder under 'Program Files' and one under 'Program Files (x86)'

I also created a folder under 'Program Files (x86)' called 'VSTBridged' for those plug-ins that only have 32 bit versions available.

Plugins that have installers for both versions get installed in the respective 'VSTPlugin' folders, those that are 32 bit only all go in 'VSTBridged'.

The scan paths in each Sonar version are then set to 'Program Files/VSTPlugins' for 64 bit and 'Program Files (x86)/VSTPlugins' for the 32 bit version.

Then both versions are set to scan 'Program Files (x86)/VSTBridged' also.

Do this in addition to the default scan paths so the original Sonar installed plug-ins are unaffected, then provided you install your 3rd party plugins to the right locations, Sonar will use the native 64 and 32 bit versions and also bridge those that are 32 bit only in Sonar 64 but will run them natively in the 32 bit version.

It's easier to do than explain so excuse my long winded reply.

Well, it's been less complicated for me than some folks I guess. I want my VST folders there in my Cakewalk folders. Plug-ins that are 32 bit automatically go to x86, those that are 64 bit go to the Cakewalk VST folder in Program Files. With the Cakewalk Plug-in Manager set to scan both folders, the program susses out what has to be bit-bridged and what doesn't, I don't need them separated beforehand. I find it all really straight-forward. RB

Ah, I see. I have so few things with two flavors available - most of my things are purely 32bit, so I don't have the doubling up issue. I can think of a few things that have 2 flavors, but I only include the appropriate dlls in my custom plug-in menus, so there's no doubling there. I still use 32 bit Sonar more than 64 bit, so I have two flavors of menus - one for each version of Sonar. RB

Lanceindastudio


I would make 2 folders for 32 bit plugins. One folder for ones you have the 64 bit cversion of too, and one folder for the ones that you only have 32 bit.

Then, in 64 bit sonar, only allow a scan to the 64 bit folder and the 32 bit folder that does not also have a 32 bit version.

In 32 bit sonar, point to both 32 bit folders.

If you have a project that is before you had 64 bit, just use 32 bit sonar and use 64 bit sonar for all new projects.

That is the best way I can see to do it-

Bingo, we have a winner...

Except Lance put it more succinctly than me...

chaunceyc


I do have all of mine organized on install and  directed to exactly 2 directories, depending on 32 or 64.  I kept the Steinberg naming convention out of habit.  One is under c:\Program Files (x86) and the other under c:\Program files.

The odd thing is that Rapture only shows up once in Sonar 64, even though I have the 32 and 64 installed in the two (different) directories and X1 is set to scan both of them.  I wanted to see which of them was installed, and that's when I saw this odd behavior where the one instance says it is found in the 64 bit folder but the detail for that same instance says it is located in the 32 bit folder.  I have a screen print that shows this perfectly, but this forum doesn't seem to allow them - usually my browser crashes whenever I try to post here of late.

Hey Chaunceyc,

this is what's causing your problem:
"Ihave the 32 and 64 installed in the two (different) directories and X1 is set to scan both of them."

You need to set the 32bit version of Sonar to only scan your 32bit VST folder, and 64bit Sonar
to only scan your 64bit VST folder plus VSTs that you Only Have in 32 Bit.

If Sonar is set to scan both locations, and there are both 32+64 bit versions of a plugin, you will
have all kinds of VST hell - and it's not easy to figure out as you already know.

Just make sure you keep the 32 and 64 bit VSTs separated into their respective folders, and scan
Only 32bit VSTs in 32bit Sonar, and in 64bit Sonar make sure you do not scan any duplicate 32bit VSTs.

For me, I simply copied all the VSTs I have that are only available in 32bit, over to another "special folder"
and added that "special folder" to the 64bit Sonar scan. So Sonar 64bit scans the 64bit VST folder, AND
the "special folder" which has 32bit VSTs for which there is no 64bit version.


A Note on Rapture:
Also, interestingly you are only supposed to be able to install either the 64 or 32 bit version of Rapture,
but NOT Both.

The tech note says that only the last version installed will work. I see you gave Rapture in your example,
so just to let you know, you could be running into a "Rapture Only One Version" install issue.

I can say however, that it IS possible to install both 32 and 64 bit versions of Rapture - I've done it.
I think it was quite a convaluted install procedure, and going by the tech note I'd have serious doubt
that it's supported.

Let me know if you really need both version of Rapture installed. If you do, I'll see if I can dig out
any notes I made.


Meanwhile, tidy our VST folders and make sure the Sonar 64 is not scanning both the 64 and 32 bit versions
of a plug, it causes a real mess, confusion, and if you're anything like me, a headache !.

Cheers - Cliff

Hey Noel,

How do I get a coffee mug like that? I'm a raiders fan too, and those are Raiders colors.
I'm gonna hit up Jimmy or Brandon for one lol!

That coffee seems to be working! 

Lance

Noel Borthwick [Cakewalk
]

Right as others have said, to minimize confusing duplication, you should ensure that:

1. You have discrete folders for 32 bit and 64 bit plugins. (normally under "program files 86" or "program files" respectively)
2. Ensure that your VST Scan path in each flavor of SONAR only references the matching folder.
3. If you have a plugin that exclusively is 32 bit which you wish to use under X64, then explicitly add ONLY that plugin's path to the scan path for the 32 bit version. A scheme like this will minimize problems.