Will try to get to the x64 test tonight. Yeah, ASIO RME FF 800 at 1024 buffers, 24/48. Will try the x64 as well as on another system using Echo Audiofire 12 just to see if there are any other difference. If I can't get to it tonight, I'll try to get to it tomorrow.
 
-Danny

I just tested in 32bit Sonar, so I'm not sure I need you to.  Still, if you can think of anything going on that'd be great.  Possibly it's an issue Sonar has with using 2 UAD cards in one machine?
 
I have a thread at the uad forum also, perhaps someone there will have an observation.
 
Same problem here in 32 bits.
 
Also, I've found that even with "Always stream audio through FX" checked, I still get the aux send disabled if I add the track effect while playing back - which makes sense, since the "always stream" function is more or less just keeping the audio engine in playback mode all the time.  Actually adding the track effect while playing back is more consistently screwed up.  I'd say it disables the aux send half the time or so.

Danny is right. Its possible that this issue is also a side effect of the plugin chaining API. All versions of SONAR since 8.5 use this custom UA API that we implemented for them years ago. 
 
I was in touch with UA fairly recently about this and their response was that this API is no longer actively supported by them at the host level and only used by them internally now. I was also told that 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 so hopefully this shouldn't be an issue going forward.
BTW this isn't really specific to X3 technically - the only reason that you see a difference in behavior is because the UAD driver seems to be testing for a specific SONAR version and masking the error messages - which is why the some UAD warning messages started popping up in X3.

> for the next X3 update
 
Yey so this appears to be full confirmation that we are going to have X3E :)
Thanks Noel.

Finally, a baker with some news on this.  Thanks NOEL!!!!
 
JK
 

Thanks for the input, Noel! It's easier to be patient, knowing decisive action is in the works at Cakewalk and UA.

Noel Borthwick [Cakewalk]
I have now removed custom UA chaining support from SONAR for the next X3 update so hopefully this shouldn't be an issue going forward.
BTW this isn't really specific to X3 technically - the only reason that you see a difference in behavior is because the UAD driver seems to be testing for a specific SONAR version and masking the error messages - which is why the some UAD warning messages started popping up in X3.

great to hear that you're making progress on UAD issues.
 
To be clear, there is no error message for the issue I am raising.  The only error message I see regularly from UAD effects is the -21 UAD plugins separated by other plugin error.  This is a different problem which actually disables processing on aux sends - I think it could easily also be an issue with chaining behavior, given some of my observations, but there's no error message that used to get masked here.
 
I hope that the problem I am raising is also fixed by your changes for the next update.  Is that likely?
 
Also, any rough idea on a timeline for the fix? 
Thanks.

It really sounds like Danny is using different DLL's. I suggest comparing notes if he still isn't experiencing issues.
 
Also Danny what version of Sonar are you using, and what operating system?
 
Again if people could update their footers with their specs things might become a little more obvious just from glancing down the thread top to bottom...

Thanks..

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.

Hi Brian,
One interesting piece of data: this morning I came into the studio to try and replicate fixing the UAD problem by un-checking "Always Stream Audio Through FX". First thing I did was once again replicate the problem by using your recipe. After successfully replicating I went to turn off that setting only to discover it was already off.
 
So, to summarize, I have successfully replicated the problem multiple times with "Always Stream Audio Through FX" un-checked.
 
Just some info to add...
 
Dean