Is it possible that my synthesizer-patch uses more CPU when it's idle than when I'm actually playing?
Any suggestions to reduce cpu usage? I've already tried to switch off the phasor / osc objects when they're not in use. At the moment it uses about 18% when I'm playing and about 30% when it's idle.
-
More CPU usage while idle?
-
Can't create "pdtonegen" in your patch so I can't try it.
I've never noticed such cpu peak when idle, maybe it's related to your OS ? -
Oh... forgot to post this...
I'm working on ubuntu Studio 12.04 -
Noise in the moogfilter audio-in ! ??
pd 0.43.4-extended on OS X 10.9.1
-
Well the Idea was to give the moog filter something to work with when you initially work with sinewaves (they have no overtones to filter).
If I understand this correct you suggest not putting a noise in each one of the tonegenerators but just having one for all of them which maybe is an idea to work with. But the way you did it the moog filter doesn't filter it... right? So this is not what I want. -
Ah I'm sorry, it did not filter it because there was one of the connections lost... Maybe this is a good idea then... I'll have to doublecheck the sound then.
Thanks for the suggestion! -
... played around with the idea but it does just not sound okay. The noise is not controlled by the velocity anymore. Maybe I can reduce the cpu load by just using the pink noise (which sounds more musical to my ears anyway).
-
Ok I've tried it, no problem here it seems. I guess kandy is thinking to the bug with [freeverb~], requiring to input a non-stop signal to prevent your cpu usage to go to the roof. [moog~] is not concerned by this, as far as I know.
For a polyphonic synth every sound generator, including noise, should have its own voice, has you noticed. Furthermore I would put the filter in each voice too, but that means 6 cpu-expensive [moog~] in your case. btw your [poly] has 6 voices so the 7th tone generator is useless (the last outlet of [route] is a rejection outlet). Check [switch~] if you want to save cpu, it's your best bet.
-
Nevermind what I said, I've just played around with [moog~] and came across the same kind of cpu spike, really nasty, going from 50% to 300% after a few minutes of running. I've tried kandy's trick with [noise~] and it solved the problem, good to know.
