Velocity sensitive buttons
Hi everyone.
I was wondering if it is possible to have Velocity sensitive buttons.
I’m using my spd sx pro as an control surface to trigger clips in ableton.
If you use midi map for this your can trigger at different velocity’s but if you use a control surface you can not.
At least I cannot but is it possible?
It would be usefull to trigger clips this way instead of mapping all the clips via midi.
Hi, I still made an attempt at creating a Reaction with the conditions you asked here. Even if you don’t need it anymore, maybe somebody else will find some use for it.
Inside the Reaction you’ll find instructions on how to set it up. I went for a Custom Code way of setting up the Reaction. I already set up the Reactions based on the script you shared in this discussion. If I’ve done it correctly, you should only need to set the Listener and be good to go.
If you do need to make adjustments, then the changes you need to make shouldn’t be that difficult. You’ll need to enter the channel and value of your pad inside Action Block 1 (you’ll see it explained inside) and I’ll explain below how you can get those numbers:
In your Controller Template, hover over the pad that you’ve set as a Listener in the Reaction. It channel and value will show up. Here’s an example of my Template:
Here’s the important part: The template says I’m using channel 2 because it starts counting from 1 and ends at 16 (which is the max possible amount of channels). But the code starts counting channels from 0 up to 15. This means you’ll need to subtract 1 from the channel displayed in the Controller Template, to enter in Action Block 1 of the Reaction. So, in the case of the example, I had to enter 1 as the channel of my pad.
The displayed number for the value is the correct number. Meaning, in my example I had to enter 60 for my nt_value.
Why have I used variables instead of the menus?
Guessing you’ll want to set up multiple pads in this way, you’ll want to duplicate one of these Reactions and then adjust them to the new pad.
Using the menus, you’d have to go across all the Conditions in the 2nd and 3rd Action Blocks to set them to the new pad (there are 4 such Conditions in total). This would become monotonous work to do for every new Reaction. Using the variables I’ve implemented, you only need to fill in the channel and value once in every new Reaction (if the channel stays the same then you’ll only need to change the value).
Another downside to using the menu of the Conditions, in their current state, is that changing the left-most dropdown menu of a Condition (the one where you select what pad to get the current value from) would reset the rest of the Condition as well (which doesn’t need to be changed); meaning you would have to fill out each entire Condition again.
I’ll make a tutorial about this method in a future post for the people who are interested.
Sign up
User registration is currently not allowed.