So, when you insert edit-step into the configuration, it's to decide which "zoom factor" you have on the sequencer? That a great idea. I thought about having different fixed zoom factors, but having something which can display between 1-64 steps *and* linked to an important Renoise parameter would be much more Duplex'sque in nature. WIth higher values, it could even span multiple patterns (not sure that's a good idea though).
Hmm, about the Editstep knob, simply I borrowed the editstep feature of Cie's Lauflicht. It has just 1, 2, 4 values only though, it's quite useful. You mean the same thing here, don't you? Well, In any case I entrust you about this function.
Same for retrig, it could be a bit complicated to implement - unless you are talking about a "on-note" retrig, and not the "between notes" retriggering that N.O.W is capable of? Retrig on a note is simple to make.
I think that the N.O.W's retriggring is the best, but even the "on-note" retrig, it's better to have enough. It will be a good accent in the seq-phrase.
Btw: do you have some ideas for how these features (hold button(s), tweak parameter) could be brought to the stand-alone grid versions (APC/monome/Launchpad)? Currently, the step-seq relies on a custom method (hold buttons, use slider to adjust volume and/or buttons to adjust pitch) - we could perhaps instead make the buttons select the active mode, and then have the slider act as a "mode-dependent" slider? Something like the nanoKontrol could then have these knobs assigned individually (again, just like how N.O.W does it)
Does this mean, we need mode-change buttons row?
Hmm, if I say about nanoK2 limitedly, I want to map each mode directly to each knob, since it's intelligible and intuitive. Also personaly I like to use 16 buttons for seq-steps.
But indeed, considering flexibility with other grid controllers, it may be unavoidable. So I'm OK with it.
Anyhow, I will be very glad and thank you if those mapping abilities will be added.