Thanks.

For me, bugs are on "double 64" bit checked, and only on mono tracks.
Unchecked, all works correctly (ZoomEQ and Console Emulator).
 
On double 64 bits...

The EQ analyzer is working fine so far - the bug that was shutting it down for me in earlier versions seems to have been fixed.

Can one of you guys PM one of your .cwp's that is experiencing the issue? I'm gonna dive into this today and see what's up.

Ok, PM sent
Thanks

It was really embarrassing last night.  I got home from work and installed X3c, and prepared for a new client to come over.  When my new client arrived, I pulled up one of my best projects to play for him. Then it happened!  A very nice buzz was coming through my speakers from the console emulator.  I managed to track some acoustic guitar for him, and was bragging about X3's features.  I had just told him about the new QuadCurve EQ with the spectrum analyzer, and pulled it up on the first guitar track and @%##! it didn't even work! I guess the lessen learned here is never, never, install a new update just before a session!

nchardy
It was really embarrassing last night.  I got home from work and installed X3c, and prepared for a new client to come over.  When my new client arrived, I pulled up one of my best projects to play for him. Then it happened!  A very nice buzz was coming through my speakers from the console emulator.  I managed to track some acoustic guitar for him, and was bragging about X3's features.  I had just told him about the new QuadCurve EQ with the spectrum analyzer, and pulled it up on the first guitar track and @%##! it didn't even work! I guess the lessen learned here is never, never, install a new update just before a session!

Try flipping off the 64bit Double Precision Engine to see if that temporarily alleviates this problem. Edit > Preferences > Audio > Driver Settings

I will try that tonight.

Scratch that, mine is now working fine, 64-precision or not.

Dan Gonzalez [Cakewalk]
 
Try flipping off the 64bit Double Precision Engine to see if that temporarily alleviates this problem. Edit > Preferences > Audio > Driver Settings

Yes, this appears to solve the problem, but only after the project is reloaded with Double Precision disabled. Enabling Double Precision will precipitate the problem immediately (on some tracks), but disabling it requires a reload for the "cure" to take effect.