I was wondering if anybody use both of the two at the same time to stop everything in a subpatch in order to save CPU consumption ?

PS: In fact, these two objects sometimes also don’t work for objects like fiddle~.

Or do you mean to use a dummy “single voice poly~” to replace pcontrol or mute~ for effect and instrument subpatches ?
That’s really interesting. I should think about it.

Thanks.

I was wondering if anybody else also did the comparison on mute~ and poly~ before and proved that poly~ is better than mute~ when used to stop audio and MIDI function in a subpatch.

Pcontrol also won’t help. I guess pcontrol is especially useless. It in fact stops nothing or only the function of very few objects. What says in the manual is not true.

Now I am having trouble with the CPU consumption resulted from the statistic stuff in my patch.

[gate], etc. Check the reference for gate, and check the related
objects too. In fact, I think there’s a whole section of similar
importance* and utility in that object-picker widget thing you get when
you insert a new object without holding a modifier key.

You can stop control rate processing anywhere in Max.

* We are talking about the most important objects in Max – these are
basic logic functions.

just don’t trigger your statistic stuff, or stop it. The scheduler is
event driven. It won’t do anything if there are no events…
In almost 20 years I never ever needed the ancient Midi on/off function.
And in the beginning I had a 8 MHz machine running Max on a Classic…

By the way pcontrol does work for me when I tested it…

Stefan

–
Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com