hey,
i’ve run into some limitations and/or bugs regarding parameter locks.
specifically some behaviour that one would expect from something called “parameter lock”.
- when locking, for example, the filter cutoff (trigless) for 16 steps, i would expect this value to be held (aka locked) for 16 steps, meaning every actual trigger that would occur up to 16 steps after the parameter lock would have the previously locked filter cutoff value (except for triggers where the filter cutoff has been locked to a different value).
instead, the paramter lock only affects triggers that came before it, needlessly limiting the potential of parameter locks. it also makes the parameter-lock length pointless in most cases - it just takes the currently playing sound and changes the parameter to the new value, regardless of trigger-length.
imagine the possibilities when combining this with conditional triggers.
you could, for example, transpose a 4-page sequence differently every few iterations, just by having a parameter lock with a length of 64 steps somewhere near the beginning of the sequence.
- triggering the lfo in sample-and-hold mode via a parameter-lock currently does nothing.
what i would expect is for the lfo to sample the first value of the lfos function and hold it until the lfo is triggered again - you know, like a sample-and-hold circuit would.
i’m still not sure if this is a feature request or a bug report.
it would be great to get some feedback from the elektron guys/gals on this.
for an outsider it just seems like a few shortcuts were taken while implementing the parameter locks.
the post-launch updates the digitakt alone has been getting are crazy good, and i don’t want to downplay that, but the parameter locks more and more seem to me like a missed opportunity.
please correct me if i’m just using them wrong and this kind of behaviour is achievable in the current OS.
Thank!