electrogear wrote:OK, thanks for trying to make me look stupid

. I had already looked inside the modules, and there are two inputs to the manual ADSR. A trigger, and a gate.
My apologies for the sarcasm; it really is Monty Python's fault.
Oh, you mean the
ADSR Code-module vs
ADSR (manual)... Now this is really getting confusing. (BTW, normally, when I
italicize, it often means I'm referring to the actual primitive, or sometimes module. I sometimes use colored text to indicate something inside
Code or
ASM.)
Glancing at the ADSR's
Code, it seems there is a check with
smoothRetrig which is turned on/off by the "Smooth retrig" checkbox in the preferences of the said module. I also can remember reporting to Malc before the the Attack acted differently in the old (beta?)
Code-ADSR vs the original
ADSR-primitive. So I assume that
ADSR Code-module's "Smooth retrig" =
ADSR (manual)'s Trig input. Sort of confusing...
So, it seems your request is already in the
AHDSR &
ADSR modules, but not in the
AHD,
R, &
D modules. However, in the modules the retrig smooth is configured by a green bool that is not dynamic. To make it on-the-fly alterable, you can either change the bool-pref with a GUI switch that has a MIDI CC function (like the
Switch toolbox module), or knock out the
Retrig module next to the envelope Code, & connect the
streamboolin smoothRetrig Code-input to the outside of the module if you want to link to it yourself.
Connect a Poly Readout to help see the actual values of said envelopes, & let me know if that is what you want please.