[cocky post deleted, Kneel before Zod etc]

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

one more confirmation over at the UAD forum:
http://uadforum.com/uad-tech-info-faq/15471-sonar-x3-uad-aux-send-disable-bug-recipe.html
 
I would dearly love to figure out what setting or configuration is different in Danny's system versus mine and the others. 

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.

Craig,
 
But you don't have access to the new FAIRCHILD comps.... they are really wonderful.
 
Jim

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.

brian brock

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.

6 or 7 instances may be why I don't see what you see. The most I've had in a project while testing for you was 4 which I thought would be enough. It may just be an 1176 issue. Here's another weird one for you. I like to use Voxengo Pristine Space followed by an 1176. I cannot use that combination in Sonar X3 at all. BUT, I can put the plugs all over the projects...they just can't be together on the same bin while being enabled. I don't know for sure if this is a Voxengo issue or a UAD issue, but this combo only does this in X3. I reported it months ago but there was never a fix. The 1176 has also given me CLSID messages in the past...so there very well could be something screwy with that particular plug, Brian. As a matter of fact, version 7 (not sure which one axactly, 7 or 7.1) of the UAD software, the 1176 will not work at all for me in Sonar without crashing it hard. I had to stick with another version 6 until it was fixed in a later version 7.
 
Whatever it is....UAD and Sonar definitely struggle a bit being friends in certain instances right now. We just need to be patient...especially since Noel has made a mention of being involved with it. I think you've exhausted everything you can at this point, ya know? Let's just hope and pray for a fix brother. :)
 
-Danny

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.

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.

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