Surge: Automate the Step Sequencer rotate buttons and endpoints

[baconpaul]

For those gray buttons add a host automation parameter "SCENE (S)LFO N FORWARD/BACKWARD" or some such

If they transition upward through 0.5 it is the same thing as pressing the FORWARD/BACKWARD button

The loop points are more obvious. Add SCENE (S)LFO N START and END params which are integers 0 -> 16

[hems]

"if the transition upward" means you would threat it as a "trigger", that is cool if you automating with some sort of random LFO, but if you would like to be precise, you would mostly liked wanting to have 0-15 value to set the precise value for START and END of the loop?

Or 16 steps scaled from 0..127 CC value?

I believe that would be more intuitive than "0.5 crosses" ( triggers ) ?

[mkruselj]

That's not consistent to how the button behaves. Button just has an on/off state, it jumps one step at a time. Any host automation or MIDI learn would need to repeat the same procedure... so for one step shift, you need one trigger change (upward transition).

[baconpaul]

@hems Right so this is the shuffle not the endpoint. We had the same convo on slack.

Adding controls for the endpoints which are just 0-16 automation params makes sense too but the gray buttons don't jog the endpoints the left shift or nightshift the pattern so are in fact transient buttons. We should do that with this issue too but it's not what is circled there.

[baconpaul]

@hems edited above to make it clearer; and to add both to this issue

[mkruselj]

As a stopgap measure, MIDI learn could be added to those buttons instead since it is likely much simpler to implement.

[K0rrid0r]

I know it might not be possible but i will write this anyway. would be super cool if it was also possible together with the planned midi cc for these buttons to also have "add modulation from" just to add some possibility to rotate them with internal modulation, super cool stuff also very crazy !

[mkruselj]

@K0rrid0r for that we already have an issue that is sorta related: #235

[baconpaul]

So: I thought it would be easy to wedge this into midi learn. It's not for two reasons

1. The Voice has independent LFOs and those get updated through the parameter mechanism. The amount of specific gross hacks I need to do to pass in a midi control which is not a parameter are way too high

2. (far less) The internal data structure expansion basically builds a parallel 'param' world just for these two buttons. It makes the code a mess.

So it's the wrong way to do it. The right way is to add params for these buttons (and maybe for each step!) which are DAW controllable and modulatable, but that requires list expansion which we are doing at the outset of 1.9 not at the end of 1.8. So reluctantly I am going to bounce this issue into the next release. Sorry.