After having a "real" DBX160XT compressor for a decade I thought of going for a plug and bought Waves rendering of the old DBX160VU. SONAR X3e finds it, but when I open the plugin it just opens a blank (white) square and no graphic at all. If I try to close the plug, SONAR freezes and crashes. This happens every time. All my other plugins works good. I tried to uninstall/reset/reload but no luck.
I uploaded a demo of another of Waves plugin (PuigTecs EQ) and exactly the same thing happen when I try to use it. I tried to uninstall/reset/reload but no luck.
 
No answer from Waves yet.
 
Anyone recognice the problem? Could it be a graphical fault (no 3D-card here)?
 
Edit: Waves answered finally and told me to update my graphic driver. That did the trick! Why didn't I thought of that. ;)
Thanks all for your help and participation!

Sonar, Waves &/or vst3 don't get along all the time.
Also try the stereo version of the plugin if using mono & vice-versa. Check & change the interleave button if needed but be careful, doing that can crash Sonar too.

DBX 160 and other Waves work fine here, though I'm on Platinum.
 
Do a clean uninstall/reinstall of Waves plugs (You're using Waves Central, right?).  Reboot.  Now do a manual VST reset/rescan (both are important).  Any change?

Your signature says you are using Sonar X3c. You should be using X3e, which was the last update to X3. There were a lot of issues resolved in the updates between c and e.
 
Regards,
Dan
 

carl
Sonar, Waves &/or vst3 don't get along all the time.
Also try the stereo version of the plugin if using mono & vice-versa. Check & change the interleave button if needed but be careful, doing that can crash Sonar too.

Still the same bug.
 

JonD
DBX 160 and other Waves work fine here, though I'm on Platinum.
 
Do a clean uninstall/reinstall of Waves plugs (You're using Waves Central, right?).  Reboot.  Now do a manual VST reset/rescan (both are important).  Any change?

No change.

dcumpian
Your signature says you are using Sonar X3c. You should be using X3e, which was the last update to X3. There were a lot of issues resolved in the updates between c and e.
 
Regards,
Dan
 

That's an old signature. I'm on X3e. *change sign*


 
Still no answer from Waves. Thanks all here for your help, though!
 
 

Could be an incompatibility with your video card. Waves products use GPU acceleration, which AFAIK cannot be disabled. I've seen this problem in the past, and not just with Waves but also Meldaproduction, which also uses GPU acceleration. In each case it had to be fixed by the plugin vendor. (Interestingly, FabFilter, which also uses the same technique, has never had a problem - a testament to their superb quality and one of the reasons you pay more for them.)
 

Wasn't there a problem with Waves installing both the VST2 and VST3 .dll's in the same directory? It seems like I had a similar problem, and solved it by deleting the VST2 .dll and doing a plugin rescan in Sonar.

bitflipper
Could be an incompatibility with your video card. Waves products use GPU acceleration, which AFAIK cannot be disabled. I've seen this problem in the past, and not just with Waves but also Meldaproduction, which also uses GPU acceleration. In each case it had to be fixed by the plugin vendor. (Interestingly, FabFilter, which also uses the same technique, has never had a problem - a testament to their superb quality and one of the reasons you pay more for them.)
 

That's my guess too, that there is something my weak graphic card can't handle. No 3D but supports 3 monitors.
And like you said - I got Fabfilters Q2 and C2 on the sale - works perfectly!
 
 

Leadfoot
Wasn't there a problem with Waves installing both the VST2 and VST3 .dll's in the same directory? It seems like I had a similar problem, and solved it by deleting the VST2 .dll and doing a plugin rescan in Sonar.

 
Thanks, I read about this but I think there only is the .VST3 on this plug.

Agree..its gotta be a video problem. I got both over the BF sale weekend and they installed, activated and are running fine.

Waves answered finally and told me to update my graphic driver. That did the trick! Why didn't I thought of that. ;)
Thanks all for your help and participation!