iulius

I've been trying to do the simple things like formatting my patch into a poly~, getting rid of ui objects and changing number boxes into int objects but i've come across the lfo sections of my patch, which i believe is the culprit for the excessive CPU reads (sometimes 110% on activity meter).

I thought the issue would be somewhat resolved by using a gate~ vs selector~ object but i see that even though a signal is not coming into the cycle~, rect~, triangle~ and saw~ objects after i switch the gate to use none of them, they are still producing a signal. (noob mistake)

so processing must still be taking place yes?

either way, what should i try next to overcome this obstacle?

I thought the issue would be somewhat resolved by using a gate~ vs selector~ object but i see that even though a signal is not coming into the cycle~, rect~, triangle~ and saw~ objects after i switch the gate to use none of them, they are still producing a signal.  (noob mistake)

optimizing a patch for cpu load