Hi Benjaminfrog,
I had the same problem with the plugins still showing up wrapped. I uninstalled the UAD software from Control Panel, rebooted, re-installed, re-scanned VST's and now they are showing up correctly. I did have to re-add a couple of them to my plugin layouts to get them to show up properly, but things look like they're working OK now.

Oh, and stevee9c6, I really don't have a dog in the fight over VST3 in general, but just for the record the plugins in 6.4 are not VST3 (unless it's cleverly hidden in some way) and run just fine in X2 x64.

Dean

I was under the impression that avoiding the bridge was important. I believe that its a performance and ram usage improvement without the bridge. And you can't dock bridged plugs.

stevee9c6


You can do anything you want to as a work around but the truth is that all new plugs  from UAD will be VST3. There is no other reason for them to dump Sonar and officially support Cubase.  Do I have inside info? no, but frankly, I am now firmly convinced that UAD has the ethics of a snake. Several months ago when this rumour surfaced here, I sent a support ticket to UAD.  They could have told me that this was a possibility instead of stating that it was a internet rumour.  I am incredibly glad I bought the Lynx instead of the Apollo. Unfortunately, I have spent over $3k on a UAD quad and plugs in the last year. There will be no more money spent on UAD from me.  UAD stuff for sale... dirt cheap.

But what would it mean to no longer support Sonar.  The plugs won't work in Sonar?  They won't fix Sonar-related bugs?  Can't Sonar take care of that?  Is there still a Sonar Compatibility Mode in UAD 64-bit?  Sorry, I'm confused.

Ok, got my 6.4.0 installed and I believe it to be working. However, having never used bitbridge before, how do I know the plugins I'm using are 64 bit and not bridged 32 bit? I can find no reference to 64 bit anywhere on the plugin interface. Sorry, I'm new to the 64 bit environment.

Oh, and looking at the UAD Control Panel, there is no longer a place to activate "Sonar Compatibility Mode"

Hey Benjamin, I have a bit more info from another post here.  It looks like the plugins get installed in a different location on some systems, so you may have to add another path to your scan path.  See if yours installed into this folder (or search your hard drive for the Powered Plugins folder), which probably wouldn't be in your scan path until you add it.  I copied this from another post:

"6.4 installed the 32 bit plugins to my VST folder located in the C:\Program Files (x86)\Cakewalk\VST\Powered Plugins folder. The 64 bit plugins went into C:\Program Files\Universal Audio\Powered Plugins\UAD2-Powered Plugins. I went into Sonar X1 and deleted the location for 32 bit plugins and added the 64 bit file location and rescanned. All is working fine."

Hope this helps!

Hi Folks,

I'm totally perplexed. I did a clean install of Windows 7 x64. Installed Sonar X2 and then UAD 6.4 and I'm still getting the same outcome. The path the plugs installed to by default was...

C:\Program Files (x86)\Cakewalk\Vstplugins\Powered Plugins

I moved them to...

C:\Program Files\Cakewalk\Vstplugins\Powered Plugins

...which is the default path in Cakewalk Plug-in Manager x64. Sonar sees them, but is still treating them as 32 bit plugs and, again, they have absolutely no effect on any audio I run through them. For plugs that have metered displays, there's no indication that they're even receiving a signal.

Thankfully, I created an image of my system prior to reinstalling Windows, so I can go back if I want to, but this is frustrating either way.

Thanks for all your feedback. I'm glad some of you have gotten it to work. If anyone has any further suggestions, please chime in.

If Sonar isn't supported I'm selling my two Solo's and going Waves and others I guess. I just put in a support request with this question. I haven't installed 6.3.2 and now 6.4 has this rumor of not being supported.

I'm not switching DAWs just for a few expensive plugs.

Genghis


Hey Benjamin, I have a bit more info from another post here.  It looks like the plugins get installed in a different location on some systems, so you may have to add another path to your scan path.  See if yours installed into this folder (or search your hard drive for the Powered Plugins folder), which probably wouldn't be in your scan path until you add it.  I copied this from another post:

"6.4 installed the 32 bit plugins to my VST folder located in the C:\Program Files (x86)\Cakewalk\VST\Powered Plugins folder. The 64 bit plugins went into C:\Program Files\Universal Audio\Powered Plugins\UAD2-Powered Plugins. I went into Sonar X1 and deleted the location for 32 bit plugins and added the 64 bit file location and rescanned. All is working fine."

Hope this helps!

Aha!!! Right you are.
 
The guy at UAD told me that there weren't 32 bit plugs included in the installer and, not finding anything in Cake's 64 bit VST folder, I assumed that all that had been installed were the plugs in Cake's 32 bit VST folder.
 
Wrong! They were there in the UAD folder. Given that the support guy was wrong on that front, I hope he was wrong about UAD discontinuing all future support for Sonar. Here's hopin'.
 
Thanks again, Genghis!

A few problems on my end. I just sent UAD support an in depth description of my issues. Just in case anyone is curious, these are the problems I've seen with 6.4. Going back to 6.3 totally fixed me. I'll spare you the details, but here are my issues.

Sonar 32 bit excessive crashing with 1176 SE: Projects with UAD version 6.3 that were saved with an 1176 SE will crash when opened now. Pressing playback crashes Sonar. Dragging into another bin or re-ordering a chain crashes Sonar. Opening the project in safe mode allows the project to play once you remove the 1176. Bringing it into the project manually will crash Sonar when you press play or drag/move the plug.

Sonar 64 unrecognized CLSID for the 1176 SE: It claims it can't recognize the plug due to it being saved in Sonar 32. However, a menu pops up and it gives me an option to use the 32 or 64 bit plug. Both options work and both options load the 64 bit plug. Weird thing here, there are 5 other UAD plugs in that project that were saved from the old version. No CLSID warning for any of them or any issues opening in Sonar 32 or 64.

Default 64 plugin folder issue: we should have a choice were we install our plugs. I so hate that Stein VST folder. I cut them out of there and pasted in my Sonar 64 vst plug folder where they belong. I did try things in the default Stein folder first though. It doesn't matter where I put them.

Order of UAD plugs additional latency warning: Inserting a Sonar or Waves plug ( or any other plug) in between two UAD plugs in my bin gives me a message saying additional latency will now be added since there is a plug that isn't UAD in between two UAD plugs. At the end of it, it says "Latency -21". Whatever that means....probably 21 ms.

What I've done so far:

I have uninstalled 6.4, deleted all files and folders, went into the registry and deleted everything UAD, re-installed and I'm still having this issue. So I'm back on 6.3 and there are no issues. I didn't have time to test all the plugs to see what others may have given me this problem as I don't have the time. There could be more...or hopefully, it's just this one plug and they will see it may have a bug or something. I'll report back here once I hear from UAD support. I hope you guys have had better luck than me.

-Danny