• SONAR
  • Problems with X2a not showing plugins in FX bin dropdown
2013/10/03 11:05:28
Guitarmech111
I am running into a situation where X2 is not showing up plugins in a list for the FX bin, but they show up in plugin manager after a scan.
 
X2 is referencing the 32-bit versions of the plug in a 64-bit environment as well as a 64-bit mono, missing Stereo, version of the plug. X1 and 8.5 show the new plugin as expected with no reference to the 32-bit version of the plugin.
 
I went to phone support, but it looks like they are in a shutdown mode too? They are only open 5 hours a day for phone support according to the contact page. With the launch of X3, wouldn't you expect that there would be more support?  This does not look good.
 
My question, if anyone knows the answer, is - Where are the plugin lists for the VST sudio fx laid out. I found this:
%APPDATA%\Cakewalk\SONAR X2 Producer\Plug-in Menu Layouts\X2 Producer Effects.pgl
 
Can I delete this file and rebuild it?
 
I would like to phone support, but I guess they don't support the early risers...
2013/10/03 11:21:27
Guitarmech111
I can manually add the plugin into a plugin list and it works as expected. Why does X1 and 8.5 NOT see this issue. How does the X2 plugin list get built and how can I reset it? I have reset all the VST plugs and rescanned. Same results.
 
2013/10/03 11:30:09
scook
Depends on the plug-in layout you select to view. Any plug-in lists in the Plug-in Menu Layouts directory are static and must be maintained by you. The "Default - All Plug-ins" option in the plug-ins layout in the Audio FX menu and the Plug-ins tab in the browser is the dynamically built list of all plug-ins.
2013/10/03 11:41:16
Guitarmech111
scook
Depends on the plug-in layout you select to view. Any plug-in lists in the Plug-in Menu Layouts directory are static and must be maintained by you. The "Default - All Plug-ins" option in the plug-ins layout in the Audio FX menu and the Plug-ins tab in the browser is the dynamically built list of all plug-ins.


Thanks for the reply, What I am saying is that the 'default' list is incorrect in X2. The 'default' list is correct in X1 and 8.5 after scanning. X2 is NOT building the 'default' plugin list correctly.
2013/10/03 12:08:37
stevec
Have you tried a reset and rescan?   I think that does rebuild the menu.
2013/10/03 13:11:06
Guitarmech111
sure did, I mentioned it in my second post. Thanks for the reply though. :)
2013/10/03 13:53:15
Guitarmech111
Nice, cakewalk support hung up on me when questioning the difference from X2a, X1 and 8.5.
 
What happened was that X2a changed the scan process that is causing this problem with my plugins.
 
Apparently, if you have a plugin manufacturer, such as Waves, that has 64-bit and 32-bit plugs, X2a will cause an incorrect VST plugin scan and cause the default plugin list to be built wrong. Support suggested, before they hung up on me, that I remove any reference to the 32-bit plugin WaveShell and leave it out. I will try it to see if it works and if I encounter any issues.

That support guy does not get any points for customer satisfaction from me. If I was yelling or rude, I would understand it. Simply asking a pointed 'why' question should not cause this guy to hang up on a paying customer.  On top of shortened phone hours, they are rude too. Great support bakers.
2013/10/03 14:03:15
Dan Gonzalez [Cakewalk]
Guitarmech111
I am running into a situation where X2 is not showing up plugins in a list for the FX bin, but they show up in plugin manager after a scan.
 
X2 is referencing the 32-bit versions of the plug in a 64-bit environment as well as a 64-bit mono, missing Stereo, version of the plug. X1 and 8.5 show the new plugin as expected with no reference to the 32-bit version of the plugin.

 
Let’s make sure your plugins are not disabled within SONAR X2:
    Please navigate to Utilities|Cakewalk Plug-in ManagerSelect the category that your plugin falls into from the left columnSelect “Show Excluded”.If your plugin is visible please highlight it in the right column and select [Enable Plugin].Available? If not...
To manually add this/these plugin’s file path to SONAR X2:
    Navigate to Utilities|Cakewalk Plug-in Manager
    Select [Options]Within the next window select [Add...]
  • You're mentioning that only the 32bit versions of the plugins are showing. This may mean that you are pointing the scanner to only look at the VSTplugins that you have in:
    C:\Program Files (x86)\Cakewalk\Vstplugins and other 32bit scan paths
    Browse to the C:\Program Files\Cakewalk\Vstplugins 
    Select [Ok] and then [Ok] again.Lastly, select Scan VST Plug-ins
 
Guitarmech111
I went to phone support, but it looks like they are in a shutdown mode too? They are only open 5 hours a day for phone support according to the contact page. With the launch of X3, wouldn't you expect that there would be more support?  This does not look good.
 

 
  • Phone Support is open for 5 hours out of day starting at 1pm EST. 
  • Email support is all day from 10am-6pm. 
Trust me, these guys work hard and are tackling as many issues as possible all at once. 

Regardless, feel free to send me a PM if you see that I'm offline.

Hope this helps!
-DG
 
 
 
 
2013/10/03 14:13:36
Guitarmech111
Thanks for the reply DG, please note my last update. Support verified that X2a changed the way plugin manager builds the default plugin list compared to X1 and 8.5 - which have zero problems showing this plugin correctly. I might add that X1 and 8.5 was using the default plugin manager scan that I used in X2 after resetting the VST plugins.
I removed the 32-bit WaveShell from the plugin manager scan path and I now see the correct plugs listed in the default plugin list.
So, with that said, if X1 AND 8.5 can use the same scan info from the X2 executed plugin manager, why can't X2a?
 
My plugin manager had the 32bit VST folder as well as a 64-bit plugin folder.  I have both types of plugins  so I need both types of folders to scan.
 
Basically anothe X2a problem with another workaround that an X2b patch could fix. I won't hold my breath or push this issue for a patch though...
 
Regardless of my tone, I appreciate you chiming in here DG.  thanks!
2013/10/03 14:14:19
jatoth
Conley, I had this issue with Waves as well. I believe the fix (for me) was to change the order of the scanned folders. If Sonar found the 32bit versions first it ignored the 64bit version with the same name. I could be wrong though, it's been a while.
 
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account