The value for the 3rd byte comes from the action. You could use “Start” and “Stop” instead.
But we could define 0 as “off”, and 64 (or Data 2) as “on” for toggle types, and Data 2 (or “val” as default) that you can define for button (one-shot) types. Will try how that works out.
Not that simple…we added data 2 column which defaults to “val”. If set to anything else, that number is put out regardless of the action value.
I must admit my Snapshot is confusing, I already use the two Actions Start and Stop (and not the single Start/Stop). Unfortunately, the device I want to react accordingly to the Transport state has a fixed CC attribution. Of course, my case is very specific but I have no doubt that having full control on the whole Midi message would help some other users.
And I guess it would be quite complicated to have a drop-down menu for Data2 that would allow to choose between “val” and 0~127, wouldn’t it?
For “val” the value sent would be 0 or 127 for toggles, 127 for triggers, and the value of dials.
For 0~127, that fixed value would be sent at any change of the Action, whether it is a toggle, on/off or dial.
Thats exactly how ot will be. „val" however means „like now", which derives data2 from the value of the action.
It sounds perfect! Thank you!
