I’ve found an interesting behavior. When using the global delay command together with note microtiming, the played fragment starts acting like a retrigger — the notes seem to loop.
But that’s not all: automation behaves the same way — instead of stretching over the defined length, it repeats in the same manner. It seems that the system treats the global delay not as a timing offset but as a kind of processing cycle restart.
It might not be a completely correct implementation, but the result can be quite interesting for experimental sound design.
Essentially, instead of stretching time, it works as a retrigger, meaning this command doesn’t do what’s expected of it. I think this requires discussion.
Maximum value for Qxx is your current TPL setting.
Feel Qxx should fallback to TPL value (1 line) if you exceed that value; it may not.
Tested and even when using a Qxx value lower than the 16TPL setting on the song; this combination of ZDxx and Qxx are causing the undesired retriggering efffect.
It’s surprising how some things can be ignored, considering this simple fix will make working with long scripts within a single pattern much more convenient. Unfortunately, I don’t understand why this problem, even with automation, is being ignored.
Apologies, I see what you mean; what the actual fck is the filter doing during ZDxx ?!
The issue occurs even without any Dly Column or Qxx commands in play.
** DSP automation is going bonkers during ZDxx command. ** @taktik
Disabling the DSP on ZDxx lines provides a band-aid fix sorta, it only silences the madness: