I was wondering if you guys that use both versions could try something for me if you get a minute please? Keep in mind there are some rules that need to be followed so this happens the way it should.
 
1. You have to have both Sonar 32 and 64 installed.
 
2. You must have your plugin directories set for the Sonar defaults at installation which are:
 
32 bit: C:\Program Files (x86)\Cakewalk\Vstplugins
 
64 bit: C:\Program Files\Cakewalk\Vstplugins
 
3. You must be using Sonar X2a
 
4. If you have all that going on, open Sonar 32 and go to preferences/vst and do a plug reset, then rescan.
 
5. Close 32 bit Sonar, open 64 bit Sonar and repeat step 4 just to be sure.
 
6. after all that is done, open a blank project in X2a x64. In a blank audio track, insert the Perfect Space plugin and The VC 64 plugin. Do they come in as "bit bridged" for you guys?
 
These are the only 2 plugs that come in that way for me. All other Sonar 64's as well as 3rd party 64's load up perfectly accept for these two. I was just curious to see if anyone else saw this but me? This happens on 2 of my pc's that have completey different configurations and different hardware. The installs are the only thing that is the same with them. On both pc's, these plugs bit-bridge even though I have ALSO created custom 64 bit plug menu's for them.
 
In plugin manager, I see Perfect Space x64 as well as VC 64 x64. So they are being seen by my system, they just are refusing to load up. It appears the 32 bit version are loading in bridge mode and I need to find out why that is. As I said though, all other plugs are working perfectly. Can you please let me know if this happens to you too? Thanks. :)
 
-Danny

Danny those 2 plugiins are just 32 bit only. Both are taken from other plugins that are still 32 bit. Perfect Space is taken from Pristine Space and VC64 is taken from a Kjaerhus plugin.

Thanks John, much appreciated. Why do they show two times in both my 32 bit plug folder and my 64 bit plug folder?

I actually just double checked this and they are NOT showing x64 extensions as I mentioned in my original post...so they appear to be 32 bit as you said. I wonder why they needed to be installed in both my directories though? Well, that solves this issue...thanks man. :)

-Danny

Danny those plugins are down right great. Its a shame that they will never be updated though we can hope for Perfect Space. 

I don't know why you have them in both folders. The only thing I can think is its an install thing. In that because you have both 32 bit and 64 bit X2a installed the 64 bit version installed them in your 64 bit folder. That is just a guess.


BTW Happy New Year Danny.

Thanks John, Happy New Year to you also. :)

-Danny

Plug in management and the browser have been a bit odd since I did the X2a update. For example, I loaded a project from a couple months back and the browser was displaying my plug in's from the same time period. Things that were installed since I worked on the project were not displayed. I rescanned and there was no change so I saved the project, exited and reloaded. After that I saw all my plugs in the browser.

I've had a couple issues like that with the browser. Sometimes it doesn't display plugs the way it should.

ampfixer


Plug in management and the browser have been a bit odd since I did the X2a update. For example, I loaded a project from a couple months back and the browser was displaying my plug in's from the same time period. Things that were installed since I worked on the project were not displayed. I rescanned and there was no change so I saved the project, exited and reloaded. After that I saw all my plugs in the browser.

I've had a couple issues like that with the browser. Sometimes it doesn't display plugs the way it should.

I'm not sure what is going on with the scanning for some. I do know CW informs us to reset our plugins in the Plugin Manager than do a full scan for the X2a patch.

If you get some odd behavior it may be due to not doing the reset.