Hi
i’ve looked at the examples on the forums for double-press and hold button,
which work to a degree…
however the issue im trying to solve is
maintaining the status if a LED button of a double pressed midi button & recalling the status
a single button press will often revert the status of the LED incorrect
i require the LED to keep its status… and only change on a double-press
also, is it possible to recall the status of LED’s within Bomes, after a series of button LED switching… as im constantly enabling & disabling translators which switch the LEDs
Basically the action that you use for LED feedback will be different for that you send to your application. I think the best way to illustrated this is if you have a certain controller and want to update the application and the LED status you can give me an example on how you want one button to that application and LED feedback to behave. Then I can probably show you an example of how it would be done. Maybe if you have even a sample project file that you could post and describe one button behavior in that project that you are looking for.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
the single buttonpress keeps changing the LED colour… i only want the LED colour to change upon a double press…
the same button is also used as a (separate) preset enable/disable when i hold the button down(not included in *.btmp)
i only require that the LED remain in the same state after a singlepress or longpress
further to the above requirement, i need a method of ‘recalling’ the status of the midibutton LED state (in its last double pressed state) … as i often change the same LED button to another colour… through a different series of button presses via enabling/disabling various presets(this is demo’d in one of the translators)
I’m using a Maschine Jam , in which the button type is set to Gate…
1= Press and hold
2= Single Press
3= Double press and hold
4= Double press
So in translator 1.1 you would only want to send output if the value of ga = 4
Rules would need to look something like this
// put ga into temp variable
rr=ga
// reset count in global variable
ga=0
// only output on double press
if rr!=4 then exit rules, skip Outgoing Action
// outgoing value for double press
pp=12
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Oh and as far as recalling values. It is best to store values of each LED in different global variables and then you can recall those values when you enable or disable the preset.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
The attached is a template that is more complete and you can use for larger projects. It uses notes for input instead of CC as I find that is more reliable, especially with the Launch Control which changes templates when you send a CC1 (undocumented feature/bug).
Preset 0 handled project initialization and input for turning on and off LED status preset.
Preset 2 contains the key elements for maintaining input and gesture counting.
Preset 3 is set up for several gestures. Each translator looks at the note number and MIDI channel to see if it is to take action. This is done in the rules of each translator.
The output goes to the alias "Application and in the rules there is a perform action to handle LED feedback which is handled in preset number 7.
Presets 4-6 are just templates in case you want different handling with shift,contro, or alt pressed.
Preset 8 simply updates the controller LED’s when translators 0.3 and 0.4 are invoked.
Most of the changes you will need to do would be handled in rules.
Hi, Steve
i needed to update my Bome software for the file you provided to work…
i’ll need to spend some time with this file, to understand whats going on
& the perform actions
Indeed, the project file I provided requires version 1.9.1 and gestures is an advanced topic. There are 4 tutorials related to perform since it was release.