peakamp~ inside of poly~
Hello folks,
I just recently stumpled over the behaviour of a, quite simple, object I cannot really understand.
If i have a peakamp~ object inside a poly~ and I mute the poly~ instance, peakamp~ continues to output the last signal value it sampled.
Maybet it's me but from my understanding following the logic of ~ objects it should cancel it's output in the same way snapshot~ does the moment it's poly~ instance is muted.
Is this different behaviour between peakamp~ and snapshot~ intentional. If yes, why?
best
Dominik
[e] I'm using Max 7.2.3, a (very brief!) test on Max 6 showed the same result.
good question.
I know, I know... pushing is a sin.
Nevertheless, something about this behaviour smells buggy to me or I just don't get the reason for it. Would be nice to have a "professional" opinion on that matter.
In other cases one may want the last value to be preserved. It is simple enough to set a different value after the poly~ is muted.
Hmm, in my case I'd actually like to set a different value which gets constantly overwritten by the output of the muted peakamp~.
Of course I can program a workaround using a gate and I'll probably be done in 15 minutes.
As I said, I'm just trying to understand the intention because to me it seems inefficient to produce a constant stream of redundant data.
It does not set a constant stream. When muted inside a poly~, the last issued value simply remains on the output. All you need to do is use a trigger object to set a different value after muting the poly.
i sometimes use this "feature" of poly patchers when muting the DSP of a line~ object between a numberbox and a signal related parameter target.
if turning off the DSP would reset the last signal value to zero, that would be kind of wrong (if not impossible to implement).