I have a situation in which I would like to cycle between different cc values (say, B0 14 xx) by pressing a single button various times:
Whenever I press “Direction”, the cc value should be increased, i.e. first sending a value of say xx=2 for “up”, then xx=20 for “down”, xx=38 for “up & down”, and so forth, and finally something like xx=120 for “chord”. The next button press should get me back to xx=2 for “up”. How could this be done? Using a meta event?
Because of space constraints on the frontpanel, I’d like to save the LED for the “up & down” value, and instead have both the “up” and the “down” LED lit for cc value xx=38 (as per the example above). How could I realize this exception?
One last point, I don’t know if you need to also control this from external.
In case, it will work with an event receiver fwd to sender 1 as I previously say, but you will have a loop with your sender 100 (hw1), I think you can remove this event and just use directly the button to send CC.
Also you need a mechanism to update button value from external CC otherwise you will have offset and jump at toggle function
Yes, this will be the next step, but it is getting more complex than just that: the external messages are different, i.e. the machine I am trying to control is accepting the CCs as above, but is sending out NRPNs and Data (CC#6, CC#38) messages instead… and, these are not spanning the whole range from 0 to 127. I’ll see if I can also just send back the same messages (NRPN and DATA) to control it.
One more thing I would like to fix is that upon a power cycle, the initial value is set correctly to 2, but the corresponding LED is not lit (none of the LEDs shines). Also, after the upload of a new .NGC file version, the LED status remains, even though the value has been reset to 2. It takes a button press first to “synchronize” the LEDs. How could I get the LEDs right from the start?
Also IIRC I have same kind of issue you describe here, try to put led event definition before or after (don’t remember) the other button/sender definition.
thanks, that actually does the trick after uploading the new .NGC: then, the LEDs are lit correctly. However, after power cycling the box or sending a reset command via the command line, this is not the case and all LEDs are off, no matter whether the LED event definition is coming before or after the corresponding button or sender definition(s). Have you solved this for your box, or are you still working on this problem?
Well thanks anyways! I might as well need to analyse the current patch status and interpret a SysEx stream from the target machine, so I’ll probably have to set the LED status manually in any case at a later time.
