I'm not sure if it is a bug or just something I am missing - but when using the sonitus eq (the ones built into the tracks), the nodes randomly disappear from the graphic display which doesn't effect the graph line, but makes editing the eq impossible. Anyone know what causes this?

Which version of Sonar are you using?

I am using Sonar 4 PE

Am i looking at that correctly? Is node 6 all the way to the left?

I have never seen this, but it is strange that the node #6 is at 20 Hz, but on the text input for node 6 it is set at 15031 Hz.

Yes - for some reason they get all out of whack and you cant move them. 6 should be on the right (at about 15k)

I copied your EQ settings into my S4PE and I'm not seeing the same problem. All nodes appear and I'm able to move them freely. What are your system specs? What graphics card are you using?

On edit: Does this happen in all projects when using the Sonitus EQ? Do any of the other Sonitus FX have graphics problems?

I am using Sonar 4 PE

I had this bug myself .. it was just the EQ (to answer Phrauge's question) when using some cards (or onboard video) 16bit
mode.

There were a few complaints here about it (of course i bumped a few threads and opened some of my own;) and when 4.02 came out a fix for this was listed.

The 4.02 patch should fix your problem there !

so am I right in assuming tht if he switched to 24-bit or 32-biot colour mode for the graphics card, then it would work?
I read somewhere that some graphics cards actually work better with their maximum colour depths anyway, becaus ethe whole GPU is optimized for it!

so am I right in assuming tht if he switched to 24-bit or 32-biot colour mode for the graphics card, then it would work?

Right, it should work then.

but... there's a reason they fixed this bug after 4.0 .. no ? ;)

Resurrecting this ancient thread.  I just ran into the same problem tonight, except my DAW is a totally fresh build and has Sonar 5PE only.  So if this problem was fixed in 4.02 why then am I experiencing the same problem??
 
I've sifted through dozens of posts on this subject but so far no specific fix is discussed, only that "allegedly" 4.02 fixed the problem, and that setting the video resolution to 32-bit can sometimes fix the problem.  (huh???)
 
Anybody recall what the real issue or fix was??  I can't find anything on the forum as of yet....
 
Sonic