Help me get [mute~] to work?
I'm trying as best I can here: I connect [mute~] to a sub-patch, send it a '0' or '1' and. . . 'no data' comes out of it. Even if I open up the [mute~] help reference, the patched example there doesn't work either. The audio engine is most definitely on. Issue persists after an application restart.
Any tips appreciated! Thanks.
See:
it simply works. (Mac max 8.3.3)
from that screenshot one can't say what could be wrong.
in any case if you use manual toggle.
sel 0. could be tricky, but that is another problem.
mute~ as well as begin~/gate~ do work as advertised, but sometimes it can be worth the effort to walk the poly~ path.
in the end poly~ is a bit less confusing imho (and might protect you from issues the other two methods can have in special circumstances such as bpatcher, poly, max4live)
to "cut off" an existing audio connection you can also abuse an empty poly~ patcher.
Thank you. Does poly~ work for circumstances beyond adding polyphony? That's the way it was taught to me-- to add duplicate/copies of a patch. If I create a "guitar pedal" with a chorus, delay, and pitch shift, can I used poly~ to disable whichever of the three effects the user isn't enabling? Thanks.
As to Source Audio, well, yes it's works in theory on other people's computers. I'm trying to troubleshoot why it doesn't work on my computer -- not even in the Max help file.
if mute~ object does not work at all, then maybe you have
a patch named so in max search path ?
P.S.
you will probably use some kind of routing for effects,
like pitch shift -->> chorus -->> delay
you would use matrix~ with some ramp time
to smoothly bypass effects, and after set ramp time disable
effect processing - if that really is needed...
muting delay might kill repetitions before they naturally fade out
while mute~/pass~ works for me in max 7.x, it is officially deprecated since more than 10 years.
poly~/thispoly~ is a very safe way to turn audio on and off in a sub. (plus it would also accept a signal to turn it off.)
oh, and there is a fourth method: dynamic loading of patchers using pcontrol/p or bpatcher. but dont do this until you are really firm with them.