Sytrus' cpu load in Live...

[musikmachine]

Is rather high. One instance using 2-3 operators was using 20-30% of my cpu. Is this normal for the vsti version? It's much lower in FL. My laptop is a 1.6Ghz dual core. Also it completely crashed Live when i tried to delete it.

[musikmachine]

I forgot to say i'm running live 8.03.

[reflex]

Are you playing the same patch(es) in both versions?

Try lowering unison order ("ORD") and oversampling, those have a huge influence on the plugin's cpu usage.

[musikmachine]

Are you playing the same patch(es) in both versions?

Try lowering unison order ("ORD") and oversampling, those have a huge influence on the plugin's cpu usage.

Yeah the same patches seem to be using the same amount of cpu so i i'll have to test it out some more. It was when i started editing a patch that it started to get a bit high. I'll try your suggestions when i'm editing and see what effect it has. Cheers.

[zerocrossing]

I was just using it yesterday in 8.0.2 and all was fine. Are you sure you don't have the oversampling cranked all the way up? Usually you can get away with having it a lot lower.

[musikmachine]

I was just using it yesterday in 8.0.2 and all was fine. Are you sure you don't have the oversampling cranked all the way up? Usually you can get away with having it a lot lower.

I didn't change anything, just adjusted the operator parameters. It's good to know though, i read a few posts saying that sytrus was a bit of a cpu hog. I'll try it out.

[tony tony chopper]

I didn't change anything, just adjusted the operator parameters.

There are several levels of complexity/CPU usage in Sytrus internally, roughly if you touch FM in the matrix, operators will eat more CPU.