I`ve got a problem with my PD. I installed PD-extended 0.40.3 and it was working very well since I made my last project (transforming live input, playing samples from disk, etc)- now my pd doesn`t work properly: after computing audio and turning on the project application works very slow, sound is deformated and I can`t do anything.

I`ve tried to install older version of PD but its startup wouldn`t like to download paths necessary to project working (PD extended paths).

What could I do?

Sounds like you've added something thats peggin the processor.

What's in the patch? Specifically, are there a lot of gui objects?

In project there is some delay lines with sound transformations like reverb, pitch-shifting, etc. and also two sample players. I have some number boxes, toogles, etc. Could it be a reason?

yes, if the number boxes or toggles are being updated constantly this will significantly affect pd's performance.

you can 'debug' your patch by gradually removing different parts and checking pd's cpumeter* to see which part causes a cpu drop when removed.

*cpu meter is in one of pd's menus..maybe 'tools' or something?

I have tried to delete some elements of patch and check it- there is still problem. Using of CPU after computing audio and starting project is 100%.

Sorry and what platform are you running on?

GUI objects can make Pd slow when they're all blinking and flashing, also displaying arrays slows it down a lot. Its best to subpatch things show they can be close/hidden.

But it could also be the effects you're running...

Can you upload the patch?

I've encountered similar problems with delaylines, especially when they are not being 'fed' by signals, or when they are fed by continuous streams of zeros. Never found a solution though...

And now i remember i've also encountered it with the [svf~] object, so when i wanted to deactivate it i kept sending a signal to it, but muted it's output.

I`m working on WinXP.

It could well be the 8 freeverbs that your running...probably definatley

I reckon you should just have one instance and send the output of each subpatch to this. I recommend using catch/throw to send signals, so attach [throw~ reverb] to each subpatch.. THen attach a [catch~ reverb] to the reverb

also you don't need the multiple [dac~] , just the one. And feed the output of the reverb to the one [dac~].

This should free up resources

Thanks, I`ll try all of that.

I changed my patch according to all of your propositions and it is OK. Thank you very much!