lorenzo.pagliei

I've just opened the helpfile of mute~ in Max 7 and there is no more the following statement I found until Max 6.1:

"pass~, mute~ and begin~ are DEPRECATED. For controlling audio processing in a patcher, please use the poly~ object"

Does it mean that now they work properly and can be used?

I've just opened the helpfile of mute~ in Max 7 and there is no more the following statement I found until Max 6.1:
 "pass~, mute~ and begin~ are DEPRECATED. For controlling audio processing in a patcher, please use the poly~ object"
Does it mean that now they work properly and can be used?

mute-in-max-7-is-no-more-deprecated

I think the general answer is to wrap your patch in a [poly~] if you want to control (start/stop etc...) its dsp separately.

Yes, this is my normal habit, but I just guess if is there a change with pass~, mute~ and begin~ in Max 7 since in the respective helpfiles there is no more the "Deprecated" statement.

Yes, this is my normal habit, but I just guess if is there a change with pass~, mute~ and begin~ in Max 7 since in the respective helpfiles there is no more the "Deprecated" statement.
Anybody of Cycling?
Thanks


I wish poly didn't have a vector's worth of delay.

I really just wish there was some version of a pointer audio land. I mean if we have 10 branches each with 10 objects and we want to calculate 1 sample on one branch then we have to calculate (vectorSize*10*10) samples instead of just 10. With a pointer to a branch, one could just send one value to the desired branch, get one value back, and set the pointer back to null the next sample. I might take a total rewrite of max for that functionality. You can sort of hack that with poly~, or gen~'s if statement but it's not easy at all.

Ug... Guys I'm sorry I don't mean to bitch. I just sort of think this is Max's one truly systemic downfall. Everything else can be hacked really.

I really just wish there was some version of a pointer audio land.   I mean if we have 10 branches each with 10 objects and we want to calculate 1 sample on one branch then we have to calculate (vectorSize*10*10) samples instead of just 10.   With a pointer to a branch, one could just send one value to the desired branch, get one value back, and set the pointer back to null the next sample.  I might take a total rewrite of max for that functionality.   You can sort of hack that with poly~, or gen~'s if statement but it's not easy at all.

Ug... Guys I'm sorry I don't mean to bitch.  I just sort of think this is Max's one truly systemic downfall.  Everything else can be hacked really.

mute~ in Max 7 is no more "deprecated"?