pcontrol and mute~ question
As said in the manual, pcontrol can only stops MIDI function while mute~ can only stops audio function.
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~.
I don’t think you can put completely different effect modules or software instruments in poly~.
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.
I just did a small test on mute~ and poly~ with multiple patches containing fiddle~, they consume almost the same amout of CPU.
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.
Unfortunately, poly~ won’t be able to stop control rate function in the subpatch. It seems to me that nothing can stop control rate function in a subpatch. What ever data I send to poly subpatch will still be accpeted even if it is muted.
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.
Cheng Chien-Wen wrote:
> Unfortunately, poly~ won’t be able to stop control rate function in the subpatch.
[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.
Cheng Chien-Wen wrote:
> Now I am having trouble with the CPU consumption resulted from the
> statistic stuff in my patch.
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…
What do you mean by "argument local to poly~" ?
Could you explain a little bit further ?
I mean that [poly~] can accepts the word ‘local’ as argument.
See the help file (subpatch optional-arguments) and more important MSP
Reference for poly~ object.
Forums > MaxMSP