Drum Rack (Mute/Unmute) – Button toggle
Hello ! I’m tweaking a novation launch control & i’m a little lost for a simple thing on a drum rack.
First i was happy to do a led feedback for a mute/unmute drum rack pad.
On the same button i would like to do a simple “mute” toggle button.
I tested with reaction :
1-When button x is pressed
2-Condition : Only continue if Drum Pad mute (bool) is equal to false
3-Then, Drum Pad set mute True.
Ok, it works on one function.
But i don’t know how to do to have both condition/toggle for mute & unmute (because if i make a second reaction with inverted settings, i’m stuck in a “mute/unmute” loop.
It’s a stupid question i know, it’s just i don’t know where to search the solution. (maybe on “get value from ranges” or not ?)
Thanks a lot ! (and next step if i can…make drum note feedback on the button 😉 )
Thank you for your attention – i will redo script and reaction later and i will send it here. But now my script is erased by pressing “save’ button.
Would you mind sharing the Reaction you want to change? I don’t fully understand what it is you want to achieve, maybe if I take a look at it I’ll understand.
When you have a momentary button, it will register your button press and release as 2 separate events. What you can do to prevent the button release from activating the reactions is to make the first action block exit the reaction on the condition that the current velocity of your button is 0. If you do that, only button presses, which produce a velocity of 127, will go through to the other actions in your Reaction.
well that is working as momentary still…..
the css reactions do not provide convinient options for a listener….
was pressed for a button…
was moved for a slider…
it would be super cool to add an option like 1. button was pressed 2. button was released..
anyway –
To turn hardware momentary button into CSS toggle you need:
– rename it in a template from “Button 1” to “A Button 1” – this will turn listener for that button from button into slider and you will see the listener options changes from “was pressed” (for a button) to “was moved” (for a slider) – that will not work for button “was pressed” – so you need to make it “was moved” – strange, right?)
– add a condition for 127 velocity match
have tried that yesterday – but that was working awkward …
Sign up
User registration is currently not allowed.