peakamp~ inside of poly~

    Jul 06 2016 | 2:12 pm
    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.

    • Jul 06 2016 | 5:50 pm
      good question.
    • Jul 12 2016 | 9:07 am
      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.
    • Jul 13 2016 | 8:02 am
      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.
    • Jul 13 2016 | 10:38 am
      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.
    • Jul 13 2016 | 4:46 pm
      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.
    • Jul 13 2016 | 7:54 pm
      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).