Hi, folks!  Anybody using the latest UAD software with X1 on a Win 7 computer?  How is it working for you?  
 
I haven't updated my UAD software for a couple of years, since I'm afraid of what might happen.  Still using X1/Win7 because I like track layers, and jBridge doesn't bother me.

Working good for me.

Good to know bapu.  I was concerned since UA does not "support" SONAR any more.  I really want some of the new UAD plug-ins.

Well, it's my understanding that the latest version has fixes specifically done for SONAR at Cakewalk's request.

Excellent!  Would that include for X1?  or just X3?

The fix was specifically for something that occurred with X3 because of something that UAD had done for X1 which in turn lead Cakewalk to make a change that wqas then broken by X3. Got that.
 
 
Needless to say, while that sounds confusing the 2 companies have worked together to get both the current version of Sonar and UAD talking smoothly.
 
It isn't that UAD doesn't support Cakewalk. It is that UAD no longer test using Sonar. Clearly the recent history shows that UAD does support Sonar.

The latest UAD plugs had a bug which UAD fixed. Cakewalk helped them identify the issue they were overlooking. The issue was nothing to do with Cakewalk and Cakewalk has not done anything at all with "the current version of Sonar" which is still on X3D at time of writing (people were experiecing these issues in X3D before the UAD's recent patch was introduced, and apparently it now works fine on X3D if you install the latest UAD version, if so then it's clear who's codebase is at fault).

X3E will introduce workarounds which will avoid certain behaviours with the buggy pluggin code. If the plugins code is not buggy then it will do nothing (current UAD code has now been fixed). It will be here within a month.

Any buggy behaviour with the plugin in X1 then might be fixed (as the plugins themselves were buggy not Sonar). However that's not to say there were not any existing bugs between X1D and X3C that may or may not effect UAD. We can confirm however no code in X3D causes any bug with UAD.
 
Obviously UAD supports Sonar otherwise they would not have fixed their bug. Below was the actual quote from Cakewalk written at the time where X3D is the latest version, X3D is still the current version, and this should clear up any confusion as all the paraphrasing basically originates from this source...

Noel Borthwick [Cakewalk]
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.

 
* Remedy has now been added.
** X3E.