BR? spiking with gui open

[english]

Ive got two daws at home. The first is a simple p4 3.4 northwood with agp gfx card going to a crt @ 1600x1200, which LS seems to run fine on.

My second is a dual-dualcore amd opteron 285 machine (quadcore), with a pci-express Nvidia 7900GT gfx card going to a Dell 3007 LCD @ 2600x1600.

When I run the exact same project with LS loaded on the second machine it causes extreme cpu spiking when the gui is open the seq (nuendo3) is playing and LS is in play mode.

When the gui is hidden it runs fine, no spikes, and when the seq is stopped but LS is in play mode it runs fine.

I have turned off multiprocessor in the Nuendo options but the same thing still happens.

The problem seems to get worse when more slices are activated in the main loop window. With 1 slice active the problem is still there but much less.

Ive also noticed on BOTH daws, when the LS gui is open, dragging around other plugin windows is a lot slower and very jerky. As soon as you close the LS gui its fine again (both daws.)

Any ideas appreciated

eng

[english]

Ok after more investigating it would seem its a conflict between a certain couple of waves plugins and having LS gui open that causes this problem, maybe even a certain type of project setup. Incidently the exact same setup runs fine on my old daw with LS open and running though so maybe there is multiple issues from certain waves plugs with LS on quadcore or something, I dunno

There is a problem tho when LS gui is open and moving other plugs windows around, in play mode or stopped. Slow down and jerkyness on both daws, nothing amazingly bad but might help highlight other probs with LS gui when open.

eng

[ohm]

The issue might be related to the use of transparent png's (actually one transparent png: the logo) in v. 1.4 this was neccesery to implement the customizable colors, but I beleive I heard it can cause performance issues on some systems. I'll investigate this further, but as I have no issues on my own systems, it would be helpful if you could contact me via email so I can send you a test version.
I'll probably choose to create a workaround for the logo display. and avoid using transparent png's if that's the problem. I could upgrade my GUI framework to actually, but that'll take longer - it will be a neccesery stap towards the osx version so I might as well... just thinking aloud here - you did write "ideas appreciated"