Making Live.button behave as momentary
I’d like to use a midi note or cc to press a Live.button. Currently it takes one press to turn it on and one to turn it off. Is there a way to have it listen to on/off commands and behave like a mouse click does?
To clarify, I have created the Live.button and am using the MIDI learn function in Ableton to map to my controller. The controller is sending this data:
04:37:14.996 From Plug 1 Note On 5 22 100 < -- button lights up
04:37:15.689 From Plug 1 Note Off 5 22 0
04:37:16.915 From Plug 1 Note On 5 22 100 < -- button turns off
04:37:17.576 From Plug 1 Note Off 5 22 0
This is really driving me insane and could ruin my weekend ;) Anyone?
From the documentation, it seems that the button should never stay on – it should just flash for the specified ms time.
At this time there’s no way of doing that with MIDI/key assignment, because we don’t have a trigger mode. We already have this in our feature request list.
Thanks for your reply.
So how does the button work properly with mapping? Am I missing something?
Should I be using another object?
I’m sorry, but I’m still wondering about this – is there no way to map a ‘button-like’ control through the ableton UI? Otherwise I have to hard code all my mappings.
Trigger mode is not supported at this time. This is on our list of things that we want to support, but I can’t tell you when or if it’s going to be available. In the meantime, you can still fake it using a pattr object (if you want to automatize it) and some select object.
Thanks very much – I’ll look forward to that!
I hope I understand correctly
I think you can do this with a Max messagebox containing "bang" cross wired back to the input of the Live buttton. It doesn’t go into an on/off loop, it just fires the once and re-sets the button back to off. It’s quite cool. I have this working in a patch for re-setting track sends that I’ll be posting up on maxforlive.com soon.
I’d like to see that, i’ve never used a pattr before and the APC40 has it claims momentary buttons for stop clips but when you map them they become toggles which i can’t seem to change with M4L….. Help anyone?
All I have been able to get is more of a one shot button, not really momentary. I am still on the hunt for a solution to this one.
I dont quite grasp how to make pattr object "fake it"
I’ve got it working with the APC as if you observe what state a button is in it will tell you with a 1 when it’s pressed down and 0 when you release it….
Can’t do it with midi mapping though only through the control_surface live path….
I saw someones patch on the Ableton forums that is using this method to make the Solo’s momentary, is that a correct comparison to what you are talking about?
No in that version he’s calling a set call to the live api, the buttons on the apc when in ableton mode 1 are momentary so you just need to observe there state, this can then be tapped to give you momentary control….
Have a look at Mike Chenetz’s launchpad tutorial patches and you’ll see how to observe them, then you simply connect the output to a live.text button and then to a toggle….
So I’ve been having a problem where if I press a live.button too many times, too quickly it starts acting like a toggle instead of a momentary. I’ve been substituting live.button for live.numbox. When you map it, it acts the same as live.button no matter how fast you press it.
It looks stupid, but im only making utility type things for myself, so it doesn’t bother me too much. I know I could always hardwire it, but… meh.. Lookin forward to that being fixed though.
I was looking for a similar solution, and I have found a fantastic one.
I can now assign a button to a shift function in Ableton (without MIDI Learn), which sets all incoming button messages from my controller to momentary as long as the shift button is active.
M4L cannot access external MIDI ports by default, there is however a way to set up a patch that hijacks incoming MIDI messages from any port before they reach Ableton Live (and the custom MIDI assignments within it!!) — the patch and further file installation instructions are to be found here: http://cycling74.com/forums/topic/m4l-midi-lib-unrestricted-midi-io/
This basically allows for reshaping incoming MIDI messages before they actually reach Ableton and transform them before they go back to the controller in use. Bombastic.
in order to set any button’s messages to momentary alignment, one has to merely unpack the incoming MIDI message and pack it again after setting the incoming velocity to 64, this way a toggle function of a Live button will get a switch message again when the button is released (its 0 message is turned to a 64 message).
The incorporation of a shift button additionally allows gated routing and choice between momentary function and the usual toggle mode. Hijacking the outgoing MIDI message from Ableton then again enables individual LED feedback, i.e. blinking red when pressed etc.
very revealing and utterly practical. Best of luck!
Solved! However, I am very disappointed that Ableton still hasn’t delivered on the promise to support trigger mode…
----------begin_max5_patcher---------- 580.3ocqU0sjaBBF8ZySgCWayfnwn6csO.8EnSmLnxlvVExfXZZ2Ye2K7gZv DaS1N6EgeN7g78cNGHutJ.UJOy5PgOE9svffWWED.PVffg4AnV54pFZGDFR1 qaXZTjaIdsCr7kOEOhI5a4BSLP7wW.c6DPwCnGo5pCbw9cJVk1kEwYj03nPB FCcaFaC+9vdpjssLADMBYgda0JaSzCV.M7Sr0Z14oZ3DUInsLXwu5g+rTn63 +FVHNeM91RljhlJDk4SnYpcLAsrgcUoeKezJqY9Lgibz+5HyQCHTj42TQOm9 HCnPUXSFgWZu.mlEaYwM.ilWXaSwdLJsRa3jx8UxFoxsC75sjjMaShLixHE3 M41Q3TRZgYTr2l6nmX06nZshW1qYWF0MnAChfkma5YxmGgGw8IuFt3GVsvmp lGfTreIwZVPcGjJ8TTWq2yBcjvIKrVqw1.4wnzekN22NHUlBK1JWldhQxbwB txwt2oEUv9owdgtVk0gkgh+lAEujAM8edm7FOWIUr2VHvgbGum8vm33Oq3zl vuHapuqKLNErgwDWWt0J4QQvoZzLw0uJAePK9bdqS1qpFy+gRNLdJ2qYcZtf p4RgWLV05hC9.utlI7uLVy6rWhAdDun98dxF7cxFR5cRmVd8QIWnGXjs30aL 0XVlk.SRAZzeRB7loKpD+WN+3JKxiTW+WkUA9RxWfefj2YXnGOdho5FR.HuM Wodw8bVVDLkKbSA6ORwNwGieKfPUFGq1XW6UNW847LyevXNm2V8Ga4NqWA -----------end_max5_patcher-----------
i noticed this problem also with vsts. i cannot automate certain momentary buttons of vst plug-ins in Live without breaking the automation. I’m so sick of finding this kind of absurd limitations under the surface..
On the other hand the limitations force us to become great workarounders. I added a button to my device to switch off the momentary mode in case a automation is played back. Because the "second bang" method seems to be working good except the automation..
And automation of the momentary button of a vst now also works after routing it to a macro.