A few things to mention here.  (When I say UAD I mean UAD-2).
 
1. I had to rebuild my plugin layouts because some of the UAD plugins were grayed out.  The 7.3 release has renamed some of the plugins by adding the word "legacy" to the end of the name.  
 
2. Almost every time I add a UAD plugin to a track or bus I get the message that the audio engine has shut down, but when I hit the spacebar it plays fine.
 
3. Sometimes when I add a UAD plugin to a track or a bus, with only UAD plugins or no plugins, I get the message that a non-UAD plugin is in that track and latency will occur.  One of the times I saw this message, when I hit the spacebar the track level spiked to 99.9 db, several times before I could disable the UAD card.  A reboot of Sonar fixed the issue.  Now when I get the latency warning, I reboot Sonar.  Luckily nothing was damaged with that level spike.
 
I've reset and rescanned the plugins so many times now, I've lost count.
 
 

I have given up on X3 until UAD plugs work with it properly.

The UAD latency message will not be resolved by Cakewalk and is a UAD issue as indicated by Noel in a previous thread.  He basically says that UAD added some code to the previous release that would recognize Sonar X2 and suppress the message; with Sonar X3 the message shows.  He says we need to take this up with UAD ourselves.
 
 

I have given up on UAD until it works properly with Sonar X3.
I have a new in the box, still sealed in plastic, UAD-2 Duo if anyone is interested...
Got it last year when I picked up a second LA-610; it works "fine" with Sonar .
 
Tom

interested
 
 

There's another thread on the forum with my unsolved UAD-2/Sonar X3 troubles. http://forum.cakewalk.com/Lovin-X3-But-Not-UAD-m2911112.aspx
 
My problems are not exactly the ones you've been having, but they are definitely show stoppers. Both Universal Audio and Cakewalk were officially notified 3 weeks ago and have returned acknowledgement emails.
 
Meanwhile, I'm getting used to life without my precious UAD plug-in's, and Sonar X3 is so feature-packed that the pain isn't that great.

melmyers
There's another thread on the forum with my unsolved UAD-2/Sonar X3 troubles.
 
My problems are not exactly the ones you've been having, but they are definitely show stoppers. Both Universal Audio and Cakewalk were officially notified 3 weeks ago and have returned acknowledgement emails.
 
Meanwhile, I'm getting used to life without my precious UAD plug-in's, and Sonar X3 is so feature-packed that the pain isn't that great.

That's a great thread.  Everyone is having different problems.  
 
All the programs that let me specify where to install vst I send to a non-default folder.  Of course UAD does not give you the option so it is the only plugins installed in their default location.  Good to know you can manually move them.  The reason I say that is because I'm not having the 32/64 conflict because of my installation scheme.  The plugins all work but there are clearly some bugs to work out on somebodies side.  
 
I only started with UAD this year, so I'm not up to speed on how often and how quickly they work to resolve issues in software they don't officially support.
 
 

I've been a UAD user and fan for over 7 years. I don't recall having these kinds of project-stopping problems with Sonar before, so there's no comparison for how long it will take to fix things. I can be patient, but in the meantime there's work that must be done, and I'm having to learn to do it without my UAD plug-ins.
 
As far as I'm concerned, UAD plug-ins are the best, but I'm worried by the fact that the UAD-2 system is not tested like it should be on Sonar.  I switched to Sonar in the first place because the DAW I had been using was not working properly with UAD, and the Sonar/UAD combo have performed well together until now.
 
According to a recent poll on the UAD forum, Sonar ranks as the #4 DAW with UAD users. Strangely, the newest 7.3 update lists Nuendo as a "qualified host", while in the users' poll Nuendo ranks 7th, with barely more than half the users of Sonar. If it were my business, I'd make sure my product worked flawlessly with DAW #4, before worrying about numbers 5, 6 or 7.

some UAD plugins inserted into Prochannel must be restarted after opening project, because they not working. Some plugins causes Sonar crash after this restart. Last time it happens, I must reinstal whole UAD pack!!! What is this?

melmyers
I've been a UAD user and fan for over 7 years. I don't recall having these kinds of project-stopping problems with Sonar before, so there's no comparison for how long it will take to fix things. I can be patient, but in the meantime there's work that must be done, and I'm having to learn to do it without my UAD plug-ins.
 
As far as I'm concerned, UAD plug-ins are the best, but I'm worried by the fact that the UAD-2 system is not tested like it should be on Sonar.  I switched to Sonar in the first place because the DAW I had been using was not working properly with UAD, and the Sonar/UAD combo have performed well together until now.
 
According to a recent poll on the UAD forum, Sonar ranks as the #4 DAW with UAD users. Strangely, the newest 7.3 update lists Nuendo as a "qualified host", while in the users' poll Nuendo ranks 7th, with barely more than half the users of Sonar. If it were my business, I'd make sure my product worked flawlessly with DAW #4, before worrying about numbers 5, 6 or 7.

Mel, you didn't have problems with UAD in previous versions of Sonar because:
 
1. UAD was testing in house with Sonar. Remember we used to have our own  Sonar enhancement button on the UAD console? LOL!
 
2. The plugin manager is different in Sonar than it was in earlier versions. Especially now in X3 with VST3 etc.
 
3. UAD has some weird "chain API" code that makes them NOT behave like other plugins. I had a conversation with Noel and he mentioned trying to see what he could do about it at some point. This *could* be part of the UAD problem, but I really don't know for sure. I reported my UAD problems past and present and happened to get Noel helping me...so that's all I know at this point and I've not talked to him in a while. He's a mad scientist though, so hopefully he's cooking something up for us in the near future.
 
My advice is...try to hang in there with Sonar and this release. I see new patches and Baker support like crazy. They are really trying to make this release right. When a company tries like they are right now, patience is an easy one for me. I can always get by using X1 or X2 until they totally fix X3 if I experience any show stoppers. But thankfully, as of now, I'm not having any issues at all with X3 or UAD 2's. (other than if you export with the Fatso on the master bus, it takes TRIPLE the time it would take without it!)
 
For those worried about the default directory UAD installs to, just copy and paste the plugs to the folder of your choice. Just make sure if you use both Sonar 32 and 64, that you do NOT have the UAD 32 bit plugs listed in the 64 bit plugin scan and you'll be fine.
 
If by chance anyone is having insane problems with UAD (I did have some major issues before the last update) I recommend uninstalling, making a back-up of your presets, then deleting all UAD registry items as well as folders and plugs...then reinstall. I seemed to have had a problem with all the UAD updates over time. The last one just didn't work right. Uninstalling, removing UAD registry items, dumping all folders and plugs resolved the issue as well as manually moving the UAD plugs to the VST folders *I* wanted to use. Then of course, a reset and rescan of your plugs (make sure you check rescan existing plugs and rescan failed plugs) and you should be golden. Well, at least I was this particular time. :)
 
-Danny