wave arts tube saturator, is good for nothing

[Matti]

Yes something is wrong. Check that all power savings are off in the BIOS
Check multiprocessor support is on in your daw
-Its difficult to give any meaningful advice with what I know and without seeing

Matti

[jeronimo]

Yes, something is wrong with how your system works with this thing.
I wouldn't recommend a clean install just because of a plugin.
Have you bought it already or you're just demoing it?
I would just forget it.
But that just me.

[HomeProducer]

Originally Posted by taturana

since i used to be a programmer, a long time ago, i really don't buy the idea that it couldn't be coded in a way to have better cpu performance without damaging the audio quality... most times that depends more on the way the algos works than everything else...these modern cpu's are quite impressive in power..

or else it's only valid as a lab experiment...

a CPU heavy plugin like this and showing an aliasing mess like this is just a joke.

I just ran the demo. Sound was not bad, still digital. Then a quick aliasing test. Plugin left my harddrive.

Looks like the most inefficient code in the world.

[Sensorychaos]

wow!

[javahut]

Originally Posted by HomeProducer

a CPU heavy plugin like this and showing an aliasing mess like this is just a joke.

I just ran the demo. Sound was not bad, still digital. Then a quick aliasing test. Plugin left my harddrive.

Looks like the most inefficient code in the world.

Like you would know more about programming, designing plug-ins, aliasing and audio than the guys at Wave Arts... puh-leeze.

[mirrorboy]

To the OP-

I know this may sound counter-intuitive but the first thing I would try is actually lowering your buffer to 1024. Then try 512.

The plug may have problems running at 2048- it's not a very common buffer size to run sessions.

Anyways, I'd give that a shot before anything.


Good luck!

Scott