Regarding workflow consider the following suggestions.
[1] Nudging
Implemented as a global shift mode function (shift+knobX).
This would allow for rapid movement, hopefully creating scratching like effects when the sequencer is running. The offset with respect to original sequence should be displayed when touching knobs (+-number of steps). This would additionally allow to firmly go back to initial position.
Possible assignments:
shift+knob5 - sequence 1
shift+knob6 - sequence 2
shift+knob7 - drum sequence (all 16 tracks)
shift+knob8 - active track
Obviously there are more possibilities to consider, for example moving all sequences at once, moving only active steps (could be quite useful for editing), muted/unmuted tracks etc. On the other hand moving active track would suffice in a minimalistic implementation.
In case of moving whole drum sequence and single tracks independently the effective position of tracks should be displayed when touching knobs.
When saving the effective sequence should be saved. After saving offsets can be reset to 0 (current track positions become new reference points for offsets).
[2] Ratcheting
Implemented as additional knobs mode for active track (apart from pitch/shift, velo and gate).
Mode activation by shift+knobs button. Pressing knobs button again would exit ratcheting mode, but other than that this button should function as normal to retain fast switching between three available standard modes.
Top knobs would be used to set ratcheting per step.
Mode indication – blinking gate diode (for less obtrusion ca. 1Hz rate 90% PWM throttle
).
Ratcheting steps should be color coded if possible.
[3] MIDI CC
[3a] MCC configuration
CC tracks should be selected in place of drum tracks. It should be possible to select as many cc tracks as required (0-16).
Each cc should have a user selectable neutral value (most commonly 0 or 64). For convenience cc definition could also have range and type (continuous or switch).
It would be useful to have a different drum map with cc configuration. Note that the ability to have more than one drum map (or even a separate drum kit per project) has been asked several times.
[3b] BSP usage
Knobs would be used to set cc value per step (when drum sequencer is active and knobs are in 'Velo' mode).
MIDI output does not differ substantially from note messages. Basically cc with neutral value should be sent instead of note-off message. Initially gate should be set to 100%, so that the next cc would be sent on the next step (with value of the next step if present or neutral value otherwise).
No cc should be sent until entered in some steps.
Shift and gate options are perfectly legal for cc, but in a minimalistic approach they could be omitted.
Ratcheting could be used for cc as well to enter intermediate steps to smooth the sequence.
It should be possible to select and save drum map separately for each project.
Regards
Michał