• SONAR
  • Quick Way To Determine 32bit or 64bit Plugins in Project?
2016/01/15 13:55:26
davec69
Does anyone know of a quick way of determining whether plugins used in a particular project are 32bit or 64bit?  I have many plugins with both 32 and 64 bit versions installed.  Just want to confirm that Sonar is actually loading the 64bit version.  
 
I know there color coding in the VST Browser area, when selecting, but what about when they're already in a project?
2016/01/15 14:03:46
scook
32bit plug-ins when opened in 64bit SONAR do not display the standard VST header by default. Cakewalk does not provide a plug-in report on a per-project basis. The user created utility ProjectScope appears to display plug-ins used but I do not see where it identifies whether the plug-ins is 32 or 64bit. I have not used the utility so cannot comment any further about it. See the user utilities page for more info http://forum.cakewalk.com/FindPost/3238243
2016/01/15 14:46:23
scook
If the plug-ins are installed in different paths, a quick way might be to remove the 32bit paths from the VST scan paths in preferences. Then the projects should complain when encountering a missing 32bit plug-in.
 
While I do have some plug-ins installed for other hosts, I do not have the paths in my VST scan path. In the few instances where only a 32bit plug-in exists, it is either installed in the Cakewalk default 64bit path (like the few bundled with SONAR) or in special path created for this case. IOW, I do not have all the 32bit plug-in installed on my PC in the 64bit SONAR scan path.
2016/01/15 16:44:57
davec69
Unfortunately, my plugins are not separated in different folders.  Good idea though......
2016/01/16 07:02:38
Bristol_Jonesey
You might want to consider doing a tidy up - most dlls can be dragged & dropped to different folders
2016/01/16 07:18:06
THambrecht
32-Bit Plugins are always shown in a special window from the Bitbridge Server.
 
2016/01/16 07:35:06
JoeOss
I believe in the browser 32 bit show in green and 64 in blue
2016/01/16 10:47:31
northlake63
How does one go about removing the 32 bit from the scan path ?
2016/01/16 21:09:28
williamcopper
All in all: please CW, MAKE IT CLEAR!!  Would that be so difficult?    Even after a year of work with sonar, I still get fooled occasionally by what is and what is not a 32 bit vst. 
2016/01/16 22:59:42
Anderton
williamcopper
All in all: please CW, MAKE IT CLEAR!!  Would that be so difficult?

 
If you want to verify the plug-in bit resolution of a plug-in that's already in your project, open it up and look at the header, as scook already explained.
 

 
William, if opening the effect's GUI is too difficult for you, the only way I can think of Cakewalk making it any clearer is if SONAR could psychically implant the thought within your brain upon your thinking you wanted to know the answer. Even Cortana can't do that.
 
You can also find out when you you insert the plug-in.
 

 
If you want to find out whether a plug-in is 32- or 64-bit after the fact, you can look in the Browser.
 

 
Or the plug-in manager, if you want to delve deeper. Look to see if it was installed in a 32-bit or 64-bit VST directory, and if so, which one so you can determine whether it's being scanned or not. This will also let you know if SONAR is seeing both 32- and 64-bit versions.
 
If you want details about the plug-in without having to go into the Plug-In Manager, then click on the name in the browser, and look at the descriptive text.
 

 
 
 
 
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account