Thanks for the reply Philippe..
Would it be possible to store the midi settings per patch? I'd look to set up a few patches, purely to use as an external step sequencer, that way I'd be adding no actual modules to the patch (saving space??) or maybe it could be possible to assign purely 10 patches (as an example) with extended patch space to save the extra information? (So as not to eat up 1000 patches worth of available memory resource)
It would suit me to have separate analog and midi sequencer patches if it makes things easier to do.. Something is better than nothing I'd think.
The note velocity could be set as a standard value for that sequence.. It's only the dedicated big step sequences that let you get knee deep into the details of each and every step.
The TRIG to note on/off seems seems the most common sense to me..
The reason I brought up the discussion, was I found a thread from four years ago where you discussed it.. I look at the doepher dark time step sequencer (I appreciate it has no modular monster built in) but that allows you to step sequence by CV, midi, or USB.. I realise you won't get all the fancy options over midi and USB that cv can pull off.. But it's something.. And if your step sequencing something else, the odds are your hands are tied up elsewhere.. It would be good if we could get the origin to output the notes over midi, we could get some simple loops of our other gear on the go.
Out of curiosity, the mini brute se that's due out in a couple of months.. Does that output the step sequencer over midi? How have the team handled it? I know there's no big LCD and GUI for creating the sequences like the origin does..? Can a few of those ideas not be borrowed?