I am not having this problems with the lastest UAD software, running UAD at 64 bit and X3.  HOWEVER, I did have to delete the UAD 32 bit plugs from my computer to get it to work right.  So I wonder if that may help others?

The fact that some of us are experiencing completely different problems with the UAD platform and Sonar X3 probably makes it harder for the tech people to nail down a solution. I haven't attempted to solve the problem by removing all 32 bit plug-in's, but if the solution is that simple, an official from Cakewalk or Universal Audio should jump up and say so. Their silence indicates it's not that easy, and I have other programs that use 32 bit plug-in's, so I'm not eager to dump them.
 
Because I received email verification from both Universal Audio (on Sunday 10/13) and Cakewalk (on both Wednesday 10/9 and Sunday 10/13), I know they are aware of the specific problems I've been having. The fact that I've heard nothing from them otherwise makes me hope that they're hard-at-work figuring things out and will communicate once they've got good news to share.
 
I trust that the glitches will eventually be fixed, but the fact that Sonar is not a UAD "qualified host" might be part of the problem. According to the recent UAD users' poll on their forum, Sonar ranks as the #4 DAW with their users. Interestingly, the newest UAD 7.3 update lists Nuendo as a qualified host, when it ranked at #7 with barely more than half the users of Sonar. As others have done, I've made an investment in both Sonar and the UAD platform, and it'd be great if they'd work together.

7.3 64 bit work great for me and no issues I've found.   I also did however need to remove the 32 bit versions and put them somewhere else.  Other 32 bit apps find them in the new home
 

Thanks for the suggestions about relocating the 32 bit UAD plug-ins. I had some time for troubleshooting today, so I moved my 32 bit UAD plug-ins out of the UAD host folder inside Program Files (x86) and had Sonar X3 rescan for VST plug-ins.
 
No improvement. The problem continues just as described in my original post. Existing projects, brand new from-scratch projects, all the same result.
 
Some have posted that they experience problems with certain UAD plug-ins, but not others, so I experimented with Ocean Way, Fairchild, dbx160, Massive Passive and several others. Nothing works like it should on my system.
 
And speaking of systems...stxx and deswind, you both say you quit having UAD/Sonar problems after moving the 32 bit plug-in's. What system's are you running? Is there something about your systems that results in smooth UAD/Sonar operation? 

All my plugins work fine including Ocean Way.    I am running 2 systems, a brand new HP desktop I7 Quad core 3.4 and an older Daul core laptop both running Win 7 64 bit.  Sonar X3 is also 64.   Initially before the patch I did have problem with UAD and FX chains but no longer.   I also sometimes get that latency msg but that seems less frequent as well.   Sometimes I do get a funny latency issue but if I hit the FX button and toggle FX off and back on, it goes away (that toggles ALL fx bins).   Seems like you do have some strange anomalies.   Go into the plug in manager and list your VST plugins and make sure you do not have duplicate sets .  Click in the plug in and check the path where it is installed to make sure you are referencing the correct ones.  OH, also make sure you don;t use stereo versions of UAD in the mono tracks as that can also cause issue.   Make sure you use the optional mono plugins.   Depending on how you sort them you may or may not see them designated as mono so when you have 2 o the same showing, the top one is the mono.   Again, check by viewing it's properties.   YOu can also view the properties when you open up the plug in and click the VST button and then details

Mel, if you have some time, I'm wondering if you wouldn't mind trying a few things for me please? I've had similar issues on my end and have fixed them all other than running a Voxengo plug and a UAD in the same fx bin. That causes a crash in seconds. I've reported that to CW support and they have confirmed it as reproducible on their end.
 
But my other issues were fixed by doing the following if you care to try them...no harm should come to your system by doing this stuff, but because I'm not a pc tech, be careful.
 
The first thing I'd recommend is a full uninstall of the UAD software. Totally uninstalling instead of allowing the update over top of update, fixed the majority of my issues. So try that. Before you do that though, back up your "preset" folder if you have any UAD custom plug saves because once you totally uninstall, I'd like you to delete every UAD folder you can find. You can also go into the registry and delete everything UAD as well if you would like to make sure it's all gone, but if you are scared to be messing around in the registry, don't go there.
 
Next, once you have totally removed the UAD stuff from all folders, reinstall the latest software. It updates a few plugin names to Legacy instead of their regular names, so you may need to update your plugin layouts in Sonar at some point.
 
Now, when you reinstall, one of the blunders of UAD is they do not give you a choice of where you want your plugins. I tried my best to get that choice into the last update but was flogged and told "go home lil boy". LOL!
 
****Side Note****If you are running both 32 bit Sonar + plugs and 64 bit Sonar + plugs, you definitely want to watch where these plugs are installed because the UAD 32/64 plugs do not behave like most of the other plugs when you have both 32's and 64's. You'll either get crashes or that CLSID (or whatever that code is) thing that asks you which version of the plug do you want to run. So do your best to keep any 32 bit plugs totally out of the plugin folder scan in Sonar 64 since you are using x64. ****End Side Note****
 
Once you have installed the UAD plugs/software, if the VST's were not installed to the folder you were hoping for since UAD doesn't give you a choice, find them, cut them and paste them to the directory where you want them to be. I promise it won't hurt anything and they will work just fine. Remember where you cut them from because if you need to uninstall, it's best to put them back where they were so the uninstall does its thing.
 
From there when you have everything installed and in the right folders, open Sonar and go to preferences then VST settings. Once there, make sure "automatic scan" is NOT selected. Change it to manual scan in the drop down menu.
 
Next, press the "reset" button (to the right of "scan") and then put a check in the "rescan existing plugins" box. From there, press the "Scan" button. This will take some time depending on the number of plugs on your system.
 
When it's all done scanning, take the check box out of "rescan existing plugins" box, change the drop-down where I made you change to "manual" back to "automatic" click apply/ok and see if anything has changed for the better.
 
I can't promise you it will work, but it sure did work for me. No problems on this end other than the Voxengo/UAD thing I mentioned. Everything else is fine. So give it a try if you feel up to it and let me know if it worked. Good luck.
 
-Danny

Did exactly what Danny outlined above - mostly problem free here except the occasional "Latency" pop up
 
Hoping that Sonar/UAD get back to solid ground soon - We have already been down this road Neo!
 
on a side note... Soundtoys stuff is still shaky over here .. an I think it is Soundtoy's issue..not Sonar's.. I love their plugs..not their service
 
 

Great writeup Danny.  The only issue I have is that the meters sometimes stop working, but I might try your steps when I have some time just in case it fixes that as well.  Thanks for taking the time to write up such detailed instructions.

after that people gonna tell me i'm crazy to say that the engine in X3 is not on pair with X1 ...
 
at least we can all say it's different ....in a good or bad  way i have my idea ...but i'm sure they gonna come up with some serious update ....

I have a UA Quad and an APOLLO and they work great in X3... no issues whatsoever.... however, I did notice that it was important to see exactly where the latest versions of UAD plugins are installed by UA installer.... once I narrowed down where the new version plugins were and scanned them appropriately, the plugins worked as normal.
 
The symptom I had prior to fixing this are exactly as you described... the plugins would insert and the gui's were there BUT, no audio impact.... it was a UAD issue and not an X3 issue.... 
 
I suggest you UNINSTALL the UAD stuff using WINDOWS, go thru your directories and ERASE any UAD plugin folders that remain... and then reinstall the UAD stuff... note what directory the plugins get installed to and then rescan plugs in X3.... that should fix your issues.
 
I apologize if this solution has been suggested earlier.
 
Jim