can someone tell me what's making pd getting really slow response to patch interaction when i turn the dsp on?

http://www.pdpatchrepo.info/hurleur/crimescene.png

There's a lot of gui and signal objects... (Pd is bad at handling gui).
For example in your vol3.pd patch you could use only two [*~] at the end of the chain. You have many instances of identical patches, so a change in one of them can have a significant effect on the whole.

yeah i realize that :\
unfortunatly reducing gui objects is not an option, i really need them.

what is the workaround for that?

thank you for your quick response!

You could use only one gui per abstraction, switch between them hradio-like maybe using your keyboard, and, of course, sending the data from the abstraction to your "master-gui" so that it's displayed when the switch happens

put a cpu meter (from media->load meter) in your patch, and then start deleting bits until you notice a big decrease in cpu usage. whatever causes that decrease has a good chance to be the culprit.

unless you update the gui-elements at an absurd rate, this should not be a problem. you could omit 2 *~, (and one line~) in every subpatch and if you need the hip~s for getting rid of dc in the output only, you could remove them from the individual vol-subpatches, and use a pair of hip~ for the output only.