yes X3D ,windows update ,,,UAD version 7.4 , RESCAN . tweaked preference till it wouldn't run anymore ( had to reset) Reinstalled Sonar . built new computer ...tried everything I can think of ,,,, even installed on different machine .... even reinstalled UAD Cards . its a X3 thing .... I wish I could go back to X2 but X3 is too good to sacrifice .   meanwhile endless banner warnings and loss of plugin delay compensation

Michael says he has it working on X3D so unless he's lying it's not X3D.

It's not clear Gerald, did you reset the VST plugins and then rescan? (you wrote "reset" but that appeared to be related to "preferences" whatever they are, I'm not sure how you reset Sonar preferences other than rename AUD.INI).
Oh did you try and renamed your AUD.INI yet?
 
Are there any issues contained within your event viewer?
Are there any firmware upgrades with UAD?
 
 
Thanks...

I've replied to similar threads often.   When you add a UAD plugin either directly or via a plugin chain and you notice things acting up such as latency, non-responsive plug in etc, just toggle the FX button and for me, everything works after that perfectly. So you are disabling all plugins in your project at once and then re-enabling them. I have a TON of UAD plugins running the equivalent of 5 UAD cards.  This works EVERY time. Also, you only usually need to do this once after you inserted the plugin and doesn't have continually be toggled.  The only issue that is still there is the -21 error which is annoying but I can live with that.  Otherwise, I enjoy the UAD stuff immensely and use them all the time with X3d

mudgel
I'm unable to reproduce any of the current crop of complaints.

Since the problems I'm referring to are intermittent, unfortunately it's not enough simply not to notice them on a new installation.  I also have no issues most of the time.  I will look forward to hearing of someone consistently using UAD effects with Sonar without problems - so far I don't think I've read of a completely trouble-free experience.
 
It's true that the workaround is relatively uncomplicated, although that hardly seems like a selling point...  It's inconvenient to have to go hunting for what's wrong when, in a complicated mix, some equalizer has stopped working.

also it strikes me that the reason the -21 uad latency error message wasn't fixed in UAD 7.4 is that UA must be working on something more comprehensive for these problems, since from what I hear the fix for the -21 error was simply to add an exception in the code for X3, the same way an exception was previously added for X2.  That seems simple enough to do, but to fix that without fixing the rest of the problems would be asking for trouble...

For the record, I've done everything I could think of and everything suggested on the forums to get the UAD plugin's to work properly with X3. Also, stxx's workaround doesn't work on my system. I wish it did. Toggling the global FX button on the toolbar does nothing. Toggling individual UAD effects off-and-on in the FX bin makes them start to actually process audio...but the moment the transport is stopped, they reset to not working again. (For some reason I never get the "-21 error", which I'd happily deal with if the plugin's would just process audio.)
 
I still find it interesting that so many helpful forum members are joining the think tank to try and fix these UAD/X3 problems...while the people who work for Cakewalk remain silent.

I feel for you guys. As a UAD user, I've had a few issues myself but I don't use my UAD stuff in Pro Channel so I never have to deal with this. I can tell you a few things I sort of found out over the past few months. I don't know how true any of this stuff may be right now, but within the past few months, this is what I was told.
 
UAD and Sonar: When I contacted Sonar support about my UAD issues, I was told that UAD uses this thing called a "chaining API" that allows it to talk to the next plug in the chain. This can sometimes wreak some havoc and one of our bakers was working on a remedy for this. I do not know if it was finished by the time X3D came out, but I reported the problem (some of my UAD issues were on my end which I fixed by X3D) and I was told it's on UAD's end because their plugs do not work like other plugs...but there was a way to fix it by bypassing the chain API so the plug would behave like all the other plugs we use. When or if this will be/has been addressed, I have no idea...but I reported UAD issues and that's what I was told by a pretty powerful Baker.
 
UAD's report on it's issues and Sonar: "We don't test on Sonar in house anymore, so we can't really tell you if or when a fix may happen. We are aware of the problems people have with UAD in X2 and X3 though."
 
Danny to UAD Rep: "I'll beta test for you guys for free as I have all the plugs from you that I need. You went from having a special Sonar switch in your UAD control panel to not testing at all in house? C'mon, I'm sure the Cakewalk staff will accommodate if you can please try to work this out with them. If I can do anything to help, please let me know as we have quite a few UAD users in our Sonar community and I don't mind doing whatever I can."
 
UAD Rep: "Thanks, I'll definitely see what can be done about this and will keep you posted. If we need any additional beta testers, I'll let you know."
 
So that's all I can add to this discussion. I tried guys....I would have dedicated whatever I could to get these UAD issues resolved. Heck I can't even beg to be a beta tester for free these days! LOL!! Incidentally, I will try the Pro Channel thing with UAD to see if it happens on my end. I just use them in my track FX bins without any issues right now. I've noticed some latency issues as well as mono tracks NEEDING to be stereo interleaved or I get this demon, slowed down thing on a track. Stereo interleave fixes it, but it only seems to happen on UAD plugs where you have a mono track and use a stereo UAD plug. I'll report back with my findings when I try the stuff you guys have been talking about. I've been following the UAD issue threads, I just haven't had time to try some of the stuff you guys have been talking about. I'll be in touch.
 
-Danny

Danny Danzi
I've noticed some latency issues as well as mono tracks NEEDING to be stereo interleaved or I get this demon, slowed down thing on a track. Stereo interleave fixes it, but it only seems to happen on UAD plugs where you have a mono track and use a stereo UAD plug.

Hmmm not the same issue but wonder if this is related:
http://forum.cakewalk.com/Possible-MonoStereo-bug-for-test-Direct-X-only-m2956642.aspx
 

to be clear, the problem I'm having happens when using only the FX bin.
 
Danny, you're saying you use UAD effects extensively and have never had problems with them disabling themselves?
 
Do you use UAD reverbs?  For some reason the problems I have are usually when a reverb is in an aux send - possibly they use the UAD chaining api differently?  I assumed it had to do with the additional latency of running a track through an aux send with UA effect when the track also has a uad plugin.
 
 
 
I think stereo/mono interleave problems are a different thing - in general Sonar has a nonstandard (ie, "different from Cubase") implementation of mono, and this creates various problems.
 
 
thanks for your report on your use of, experiments with, and communications regarding this - it has to get fixed eventually...

Hi Brian,
 
That's correct. No problems in track fX bins as well as bus fx bins.
 
I use the EMT 250 religiously on just about every lead vocal that requires a killer verb. I don't use pro or dream verb any longer though.
 
I'll run some tests for you regarding the issues you're mentioning. But so far, I honestly have not had any issues with any UAD plugs on my track bins or buses. Now, you don't mean Fx chains, right? You're talking you put the UAD plugs literally in the FX bins on tracks and buses and they disable, right? If so, that has never happened to me in any version of Sonar. I should be able to try some stuff later in the day....I'll be in touch.
 
-Danny