sinistar

Here's what will probably be a simple one for you experts out there.

I'm writing an editor for a device that doesn't like SysEx parameter changes directly affecting its parameters. It prefers you send the SysEx equivalent of front panel keypresses to achieve the changes, e.g. by selecting a parameter #, then using Value Up/Value Down.

This obviously sucks. However, as I workaround, I was hoping that there was a way to track directional (value) changes in the output of a slider and make its output get rerouted when its values start going up rather than down, or vice versa. I know there are the switch and route objects that might handle the routing aspect in various ways, but the thing I can't work out is how to best track the up or down directional changes in the slider's output value stream. I looked zl.change but it didn't seem to be quite capable of this, unless I missed it. Obviously, I need to keep a running tally of the last two values and any time the > or < compared to the previous value starts going the other way,

I need to change the data stream's routing.

This obviously sucks. However, as I workaround, I was hoping that there was a way to track directional (value) changes in the output of a slider and make its output get rerouted when its values start going up rather than down, or vice versa. I know there are the switch and route objects that might handle the routing aspect in various ways, but the thing I can't work out is how to best track the up or down directional changes in the slider's output value stream. I looked zl.change but it didn't seem to be quite capable of this, unless I missed it. Obviously, I need to keep a running tally of the last two values and any time the > or < compared to the previous value starts going the other way,
I need to change the data stream's routing.

triggering-actions-on-changes-in-a-stream-of-numbers

Check out the [change] object.. specifically the + and - modes.

Triggering actions on changes in a stream of numbers