UAD 6.4 (x64) Out - RESOLVED!

Jesus.....that is awful news man.  I am starting to hate that company.  i am hearing that it works wih Studio One.  i will teport back when i can confirm.  Dude....truly bad news for us AND for Sonar as a DAW.  I am SOOOO glad i got a lynx aurora 16 instead of an Apollo.

Make sure you have the path to the 64-bit plugins in your scan path.  You may need to add it in your VST scan settings.  It doesn't give you an option to change it when you install it and the 64-bit plugins installed to C:\Program Files\Steinberg\VstPlugins. 

I can't say my experience has been perfect yet though... some of the plugins see the 64-bit and a few still pick up the 32-bit from the old path.  The one I've seen so far that is bitbridged is the 1176 Rev A, but I think I can force SONAR to use the right one with a little creativity.

Genghis


Make sure you have the path to the 64-bit plugins in your scan path.  You may need to add it in your VST scan settings.  It doesn't give you an option to change it when you install it and the 64-bit plugins installed to C:\Program Files\Steinberg\VstPlugins. 

I can't say my experience has been perfect yet though... some of the plugins see the 64-bit and a few still pick up the 32-bit from the old path.  The one I've seen so far that is bitbridged is the 1176 Rev A, but I think I can force SONAR to use the right one with a little creativity.

Thanks for the tip. The path is defined and the 32 bit plugs are no longer on my system. Not sure why it's seeing them as 32 bit.

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.

Saxon1066


Any noticeable improvement in sound with the 64 bit?  If not really, then why change over just to avoid j-bridge?

No. Yes.

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.

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.

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!

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.

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

soundsubs


mine were installed in c:\program files\steinberg\vstplugins\UAD powered plugins



...which is strange because the installed didnt prompt or ask me for this path.

I sort of expected that for the 64 plugs. When you don't get a prompt as to where to install, they always default there due to Stein being the creators of VST or something.
 
What was really weird for me was, I've always received a prompt for UAD installs. My 32 bit folder is program files (86)/ Cakewalk/VST_32. It installed my 32 bit plugs there automatically which was cool.
 
My 64 directory is the same as above only in the c: program files without (86) and then Cakewalk/VST_64. But the install sent them to the same directory as yours...so I just moved them. It worked both ways though.
 
-Danny

No more UAD for this kid.  LOUSY policies of stranding customers...

Plus Sonar is now officially not supported.


http://forum.cakewalk.com/tm.aspx?m=2725457

Sure they will support Sonar, just not UAD-1, Sonar means sales...UAD-1 not so much.

deswind


My understanding is that UAD is ending the official support of Sonar.  This may not matter for UAD 6.4 but it may make a difference in future UAD software releases.   If I was sticking with Sonar, I wold be reluctant to invest too much more into UAD.

http://www.uaudio.com/sup...host-applications.html