Alex: Sonar X3D, UAD 7.4, Win7 Home Premium with SP1.
 
Craig: You would be correct Sir. The older versions worked fine for me. The newer ones after 6.4 were jacked in Sonar for me. The only reason I updated to them was I bought the new plugins that came with the newer versions. So if you ever take the plunge for the newer stuff, you'll be forced to update your UAD software and will need to reconfigure a few things. They no longer give you folder choices, they install loads of mono plugs, you will have to rename/relist any custom plug menu's....it's actually pretty gross...especially if you have both 32 and 64 bit plugs installed.
 
Brian: Still no issues on my end even in x64. The only thing I'm experiencing is what Mel and others reported with fx chains in PC. I can do fx chains in the regular track and bus fx bins with no issues. I decided to try one of my older machines that has a Duo in it. I'm running a project with 21 UAD's using both your methods and mine and everything is working flawlessly. I wish I could figure out why it's working on my end and not yours. Sorry man....on the bright side, Noel checked in...and if he says he has a fix for it, have no fear for the great Noel is here. :)
 
-Danny

There are two folders that UAD puts the plugins in ... On 64 bit windows . In Program files ,, There are all the stereo versions in the Universal Audio folder but no Mono versions ,,, The Mono versions are in The Steinberg folder under powered plugins ,,,But There are a duplicate set of stereo ones in there ,,,If I don't delete the stereo plugs in the Steinberg folder and leave the Mono Ones Alone ,,, my Sonar X3 will crash big time.  I followed Danny's VST reset and rescan procedure to the tee and that's how I found out about those duplicate Stereo versions. I wonder if those duplicates are causing most of the Problems ...... The only real problem I have since then is the -20 latency warning message on just about everything I do

Anderton
Interesting. I'm still on UA software 6.4, and it works fine. I can put effects in bins, buses, whatever. Maybe this is an instance where "if it ain't broke, don't fix it" has served me well.

 
tested with UAD Version 6.4, same problem. 
 
One further thing I notice is that the problem is almost guaranteed to happen once 6 or 7 1176s are instantiated and you add another one during playback.  This is obviously a nonstandard application, but it may serve to demonstrate the problem at least.

all of the stuff I'm seeing also happens with current UAD effects.  I suspect that Pristine Space also adds a large delay the compensation of which may interfere with UAD processing...
 
patience, yes.  I believe this will get figured out when the -21 error does, but I'd like to see some recognition of the variety of issues people are having.

brian brock
all of the stuff I'm seeing also happens with current UAD effects.  I suspect that Pristine Space also adds a large delay the compensation of which may interfere with UAD processing...
 
patience, yes.  I believe this will get figured out when the -21 error does, but I'd like to see some recognition of the variety of issues people are having.

Brian, have you tried going back on any UAD software versions? I found something that may have something to do with my situation vs. yours. I *thought* I was using 7.4, but it appears I'm using 7.2. I don't know if that's why my stuff may be working...but it may not hurt to try it. If it works, at least it will get you through for a while until they fix it. Sorry about that....I thought for sure we had updated all our UAD cards to 7.4. Since things ARE working for me, I'm staying with 7.2 for now.
 
-Danny

CakeAlexS
Not sure what you mean by "recognition" but If you read Cakes statement the issue very clearly lies with UAD so you are probably on the wrong forums for that. Updates for your plugins will fix the issue and an X3E update may help workaround the issue, I wouldn't expect that for a couple of months. Not much more to say other than that really. I think the thread has served its purpose.

Noel's statement is that "this API is no longer actively supported by them at the host level... they would add a remedy from their end. From our side I have now removed custom UA chaining support from SONAR for the next X3 update...".  It sounds to me as though most of the UAD issues lie not with one or the other company, but are the result of a breakdown in their relationship, such that Cakewalk has continued to use a function which is no longer supported by UA.
 
As I've already written, my purpose in this thread is to speak with other users of both UAD software and Sonar X3, to try to understand what is causing these issues, and to develop workarounds or techniques to avoid problems with using UAD effects in Sonar X3.  Additionally, I hoped to apply a bit of pressure on Cakewalk to address this.  Noel has posted a helpful reply, in which however it's still unclear whether he is referring only to the "-21" error, or to the broader spectrum of issues which have come up.
 
I hope to continue receiving more replies from UAD users, ideally with a view toward understanding whether there is a key difference in systems which accounts for why Danny reports no issues when following the recipe I posted, which in my and some other systems creates an error consistently.  I have also been on the UAD forum, asking people there to attempt to replicate the issue as well.

The current UAD driver tests for versions of Sonar and makes some changes for them, specifically repressing the "-21" error popup.  There may be other changes as well.
 
Older UAD drivers, which were written during the period of greater cooperation between Cakewalk and UA, apparently implement a "custom chaining API" which at that time was still "supported by them at the host level".  So, if Cakewalk's Sonar X3 code still expects this custom chaining API to be supported at the host level, it is reasonable that Sonar X3 will work without issues with the older UAD version.
 
I could be wrong.  I don't understand any of this, I just want to get some of the best effects plugins to work with Sonar X3

I guess I m very lucky!   My FX toggle works everytime and I use UAD plugs as my main FX source both as insert, loop AND FX CHAINS mixed in with non-UAD.  Everything works great and when it doesn't, I toggle FX (disable all FX) and press again (enable) and it's all good!    Good luck and I hope this get fixed properly down the road.  

 Same here as Stxx, toggle global FX gets the PC fx bin UAD plugs working here.
 None of the UAD issues mentioned here that I've seen have been exclusive to X3 here, when X2 was first launched the exact same issues with noticeable loss in UAD performance and the"-21" error were all present here in X2 until UAD fixed it with a new driver.
 IMO UAD drivers have been hit and miss, mostly miss, since they went 64 bit exclusive. I have both XP 32 bit and Win 7 64 on this machine and the older UAD plugs perform much better in X2 on my XP 32 bit install than they do on the same project opened up in Win 7 64. With their 64 bit version
 It just doesn't add up to me, how plugins designed to utilize processing and ram power from a card could in any way benefit from being 64 bit?
 I also highly doubt they have done anything to the code of the older plugs, that were designed from the ground up to be DSP powered. I'm pretty convinced there's some kind of internal UAD wrapper.
 TC powercore stopped development years ago, but they are still updating their drivers and work without issue here in projects loaded with other 32bit wrapped and 64 bit plugs. VST 2 and VST 3.
 
 
 In any case, folks are free to direct their blamestorming at who they choose. UAD does not officially support Sonar. I read they plan to drop support for their PCIe cards in the mac platform. They dropped support for UAD-1 ... A pattern?
 
UAD working here in a slightly crippled state in 64 bit. I'm done buying UAD plugs until they take more responsibility for what they sell.