[norm~] creates a click when incoming sound goes from silent to not silent (and a possible fix) about pd-else HOT 3 OPEN

noisegate does some fade in with the attack time, this is in fact needed

from pd-else.

I understand, but the problem doesn't come from [noisegate~]. When the incoming signal reaches a silent state, [mov.rms~] returns an infinitesimal number. As soon as a "new" sound arrives, its volume will be divided by this extremely small number, leading to the click...

As far as I know, the only way around is to avoid any silence going into [mov.rms~], and putting a [noisegate~] only on the left part of the patch (i.e. on the incoming sound itself, and not on the analysis). It's not possible to do it from outside of [norm~], so one would need to edit your object...

from pd-else.

I understand, but the problem doesn't come from [noisegate~]. When the incoming signal reaches a silent state, [mov.rms~] returns an infinitesimal number. As soon as a "new" sound arrives, its volume will be divided by this extremely small number, leading to the click...

i know

from pd-else.