live.button behaves as toggle in automation
In this patch I have a button. Through the Live-midi-automation I want to bang it with a note-command. The funny thing is that the button behaves as a toggle. The note switches it on, the next note switches it off (!) and it only bangs once. On mousecontrol all is as expected, so no problems.
Did I overlook something?
I’ve noticed the same thing. My workaround was to use another button in a feedback configuration to turn the toggling button off, like so:
----------begin_max5_patcher---------- 497.3ockTssaiBCD8Y3q.4mYiBjRZ18WoZUjIdRh2EFivlnTU0+85aPbRMnz WrwyLdly4fm4izDRs3JHIY+I6srjjORSRrlLFR7mSHszqGZnRaXj5AkRfjbm KbnULnZ.k0Yg2pyj58NvkYRMEOQx9q2cGUc3LGOsuGNnbQTTTtZcd1u2XVKW OtNcENyVbQ8+9UQPs43ToM19LM0rj+jTogeAVcOetP6QZKLm63zsqGj.pnJt .C3T4VCMpJLqEUiqST5ahzhBTkMAa2LSxBgPHzBzsxcjoz2q4nB52CHstABu v8hp2njdAX6oJUOWqGvsujd00KuF8qY.DGGMOZOrlxN.XM7VSLqyi3WAcx4b BZ74kKwwijb8FNoa2G40NApkDKOVEKWCHWIUu64erHZ0OWl+9sZkxhyndG+w VFwGWWYNsIP9iJDmE8pEdM9PJuvk7ExVqfMxlxWihXJhB+i3opFqTMB7zyBK SUWRkZ33+M4RtDrErYYEGOJlEnhdFzO2Ms+8cW04zN7XbyOIw9xRyQ7wYj1N Ti86GuHEC8GF6m8Cqxt0kx.ohiSMoucqwLHnybFCv.XSZ4rNAGUdLTTVrpR2 +W5FYVt50ucpxNmX6K1APaLyIhNd7YYwCHLNMJ9YrvAtctQYNFsq5AjpO7Y5 W3ZWkVD -----------end_max5_patcher-----------
It’d be nice to get some official response on this strange behavior, though.
Currently, there is no "trigger" mode for live.button and live.text for automation purposes, just off and on.
No trigger-mode for a button? What else should you do with it? But the workaround is nice and works fine. Thanks, nonagon, for that.
In the inspector you can set the live.button to send a bang for both on and off. It’s the last item in the inspector
But the intention was to send 1 bang and be prepared for the next one.
Now it takes 2 triggers for the process. And that is regardless the trigger option.
But please correct me of I’m wrong.
is there any plans to impliment a trigger mode for live.button?
i’m using it, or at least i wanted to use it, as part of a key map ( an auto fadein fadeout (linked to bpm / bar length) for the volume of each channel) i have a live button for each channel to start the fade, with a mouse click it works fine but i want to key map it to the number pad (key 1 for channel 1 etc) on my keyboard but all it does is act as a toggle – i.e i have to hit the 1 button again to turn it off (and it doesn’t send a bang)
i did think of using key and select to map in the same way but i have to be clicked on the m4l object for these to work (doesn’t work well when i’m using my launchpad as well for clip starting)
anyone know to hardwire from the keyboard to a button using the api?
It’s on our feature request list, but it also will probably not be added in the foreseeable future. In the meantime, you can fake it:
----------begin_max5_patcher---------- 972.3ocyWE0bhCBD9Y8WQl7rmSRzX06s69azoiClrpbk.YBns85z+6GABIPj XSac5buPzcWfu8icWVdc5jvcrmAdXvOCtOXxjWmNYhRTsfIM+eRXA54LBhqL KjBOw18mvYZUB3YgRbYf3TEEKX62azUhDYGwzCaqfLgdKRRWMOZVvcapGSWW OFKGCdnYJ6YTAG+Wn153HoZsX5oBLk.BEBh6DxNI5KUKR7RIn2wvv1EGmqPp D8+HNNzZGonBk0g+pBiHA+lQxc7AnpgOZHD4rvD3LTwwLp0lOIrySqAudX0R 0mkqi5bTIIefvxdDTPJxHLG1O9UfUBTeVaFbsDSKq.NPEHQCns2UzIhXqC4m L2q98nLXvI6xigFSNTgyYzZP3LyZwls69f3TUvPpMtUVPQkdlrfwH6PUmwb7 NB3bFHCeQTbAR.BrFOIQsyCWTVgoBm0BnH4ZbjmUwHDmkRq4rGM4vYbF7DNW bTsVcrkSBkULiShki7dIXE.miN.F5yIKiChfHaMdxwRUA.wIKp+rPMFuxhVG NO6xbsDWEWlu8N4bWj2kD1CE9x8LV71zoleL6SRlNUqb4xbfH4pwQlQpOK1z uf02AYtCQOLLgF8MSnJ2YTjltnURpYzwEbHlnabT1Ba7kwJJ.cFe3sjHzvYb gOa1LVpHdPpHxuut9i3qckVIX5PUoTtQsd+j.mcpJybDXBACbcobfKvz1aZt uK4umgGw44tU1U7LNujIqR2.vfGF0w1GE2KFKri9uB1dXQ+3d8MD1MBk3W2V DGcFx2J2EYj9VjPTg2cRnCnraS585rvaGEep1PtR6GioCEBaGhzzqWqMgS6X A0n936qzjrp2iqzdbhp833Eqst691zebjmlfSeulf+DdtLNPHCCeeeLR8IIx L15iekl8ctqzwWW9YbFB9LL20iNi5BP7ndXGdUroAW21bkSoRtfBnZqtcydt 8s8gOsG45L31T2qjDeFQNAr8skmLEmr.NltmoSYlcoRVUt9ATQdTdR9jQ9fS kWBPNAWLzr4BnjOjRPxSlxg0OJU9gZ0xfskOKehQy8lwyGDlhWZNb7YQgLvY 34WHOFcemfsVygVxLeTKVHyGshM7RDGYUhqDW1aIsd1jWzxxMdSxcdQLhRY5 WRtsqboG6HL5gwBq5c8Zrj7NxGqWK90fMKW6USsuAyoDtJBvs+Gcof9WD2TP 3hKfSsuWcndFhcL5hKd8eo6EUmFKj5sc9wT5GCRIqRmm1VmdQ7l4IW92TUQs jEppZ0+4K5HihaW98xsKGClR+BXR9m2l9O.IzR1O -----------end_max5_patcher-----------
thanks for that – i did try something similar but it doesn’t seem to work (it turns off the button led) but isn’t starting a fade when i map it to the 1 key.
very strange – i’ve attached the patch to let you see. the patch will fadein / fadeout the first 3 channels of abelton (loadbang is fade out). i put your button at the bottom (fades on channel one) – when you click it with the mouse all good – fade out happens – when you map it to the 1 key (or any key) the button lights (and turns off) and the max button bangs but no fade?
I had the same problem.
I found that there was a conflict from having the qwerty-keyboard midi keyboard as midi-input turned on.
I turned off "Midi From…. Computer Keyboard" on that channel, and now everything works.
Please someone let me know if this has been fixed yet (in Max6)? I am running 5.1.9 but it is still a problem.
I would also like to know if this has been fixed in Max 6. I’m struggling with this issue currently. Emmanuel’s suggestion does not seem to work in all instances (for example in a device of mine certain buttons are supposed to disable themselves once they’re clicked and this seems to cause problems.) I’ve had customers tell me that the new version I sent them which aimed at fixing this issue can sometimes crash in Max 6. I have not witnessed this problem as I’m stuck with 5 at the moment. I’d be quite glad to know if there were any changes at all made in 6 concerning this issue (possibly in the way the button handles a "set 0" message as in Emmanuel’s patch?)
Or is it possibly something that’s changed with Live 9 vs 8?
Stephane: Yes. The issue was brought to my attention by customers of my Subtractive Looper, but it was in both of these devices that I had tried to implement Emmanuel’s patch. Have you noticed the problem I described in the Randomizer? I was able to reproduce it once. It seems that if you click one of these buttons fast enough your upclick will arrive before the delayed "set 0" message, which for some reason can then lead to the button continually triggering itself every 50 ms (even though the buttons are set to bang on zero>one not both.) I really don’t understand fully, but I believe I’ve come up with a fix, which is to simply remove the [delay 50]. It seems to work and I’ll be sending out an update momentarily.
Even with the delay removed and the button set to bang on Zero->One, the upclick (only if you don’t click fast enough) causes the button to trigger again. This double-triggering is annoying but for now it will have to suffice. Any ideas? This has been way too frustrating for something so trivial.