I came across this last night by coincidence when poking around in the ini files ...
 
There is a file called XRayExclude.ini in %APPDATA%/Cakewalk/Sonar Platinum
 
Depending on which installation you look at (X1/X2/X3/Plat) this file's last modification date is either in 2008 or 2010 - long before all the relatively recent fixes were made to make WAVES work nicely with Sonar
 
The contents of the file are:
 
; $Revision: 2 $ ; $Date: 3/04/02 10:23a $
[WinCake]
[EffectProps View]
;Exclude all Waves plugins, due to incompatibilities
XRayVendorExclude1=Waves
XRayVendorExclude2=Nugen Audio
 
 
Since this seems very old and I use x-ray a lot, simply commented out WAVES to see if x-ray works ... well, it does - it x-rays and ACT control still works (poorly as ever, but it does) ... but I have not done any long term test yet, so I can't say if it hurts stability ...
 
Any one willing to share memories from the past what the problem was with x-ray and WAVES?
Any one else willing to give this a try to see if it is a stable option these days?

I'm a relatively new Waves user so haven't really experienced this. Not much of an X-Ray user but I'll play around with it a bit tonight and let you know back here.

Works a charm here - I don't have a lot of Waves stuff, but I'd wondered why it didn't respond to x-ray, now I know, and it's fixed. Everything I have - again, not much - seems to work without issue so far...

Seems like it's worth having a dig around. I wonder what other legacy stuff that could easily be turned off, is around causing problems.

I wonder if we could get an official comment from Cakewalk ...
... what sort of WAVES vs. x-ray incompatibilities there were in the meanwhile legacy versions of Sonar
... if the Sonar fixes in the X3 versions that now allow us to work nicely with WAVES plugs also addressed this old compatibility problem

FreeFlyBertl
I wonder if we could get an official comment from Cakewalk ...

Yes, anytime by contacting tech support.

scook

FreeFlyBertl
I wonder if we could get an official comment from Cakewalk ...

Yes, anytime by contacting tech support.

Ok. just did via email ... let's see ...

There used to be an incompatibility with certain plugins that used DirectDraw in their UI. 
See this KB article KB article. If its working now perhaps Waves stopped using that.

Noel Borthwick [Cakewalk]
There used to be an incompatibility with certain plugins that used DirectDraw in their UI. 
See this KB article KB article. If its working now perhaps Waves stopped using that.

Thanks a lot, Noel.
 
That was exactly what I was looking for :-) Now I know what to look for and how to exclude selected plugins if I encounter problems.
 
For anyone else reading this  ... this is from Noels link:
X-Ray is not compatible with plug-ins that use DirectDraw to create their windows, such as many recent plug-ins by Waves. If a plug-in is not compatible with X-Ray, the plug-in's window will either flicker or not display properly. If you have any plug-ins that are affected by this, you can exclude the plug-in(s) from X-Ray (using instructions in KB article)