Ignore click but still be mappable ?
If i select "ignore click" for a parameter, i am no longer able to map it to MIDI or Keystrokes. Am i missing something ?
Does this resolve your concerns?
----------begin_max5_patcher---------- 708.3ocyWFrbaBCDF9L9oPitz1YR7.X.amacZu3C8Vu0zIi.TskCHwHIRcZl 7t2URPBtIX6LES6EDZYQ5Wer6JwCS7vohcTEFcE5aHOuGl34YMYL30z2CWR1 kUPTV2vYhxRJWiuv8LMcm1Z+8qzuSgHEJARQ0Hs.kUvpPLsBIp0U0ZDiizan HIgulh7uLHb9zOzNLELNMSTysiUXiweH3ZE6WTisfvo9Ml40kLdAUa0SPqux 0ol99ccCl3V+ZsVQzYaX702HoYZ25NIBdGTPxLaSrYDPyfNnu27Nrb6JTjt8 xfE3NhiSJshC+QIiTfMO3wISLWt3ujlRpptPeEdbIQfefYwGtXgoIxBjP+dH QxvRBPjoTY6X5zq99JpSYXlARHbJD7feRNuErrODBO.Dhh5.AW3PuPH5.P3o oPB10T4MTNIsv5g+.Fp70MLHEKcKr.PvcMIeWiWslKjTzmJXY2dMvt6gGvzn LBGAQWUBdtwuur5yqPD39ao2ixIZBhSuiJgD0BpRM8UyOm8OI+LHw1rbtM1b dOePBG3nR5Ogg8ELuRRqn.z.X2aD6PDlFbLp3tNO5fAo9iBSf.nik89xl2Di d8HmnCjJ6BYrWiWNMteFsbTPDH7SjRm4RbVhDYKskL+PwNIiBWxzP8ETv+Af IpSVUT3gHS74b6Ols1clozc20wXsqH3Hqrt7XmVvAqkI8rOIr9ZGE3rdujfC vdm14xt4zebFVqbM12G4JQsLqEdMZ.8rhyoJMiSzLAuiOA66zFVdNk2kM4Lk Qb48uy9oJmjSPNGSMkr7JADXzPjvXScuEKcGtcVammmjAS7l8YFZ0OuUvwcU e7YP8FzGbrHA+QKRX4IvxjQSMwCvW19TiKGlTUAG6T0LjVg.EP1JjltIWLwU Ux00V7B9Eo6Xs96bfHgRTZn9TszUKY2hDnVLLOON42PAMxmG -----------end_max5_patcher-----------
Sorry, i should have been more specific. I’m talking about a m4l device, and the way i can map GUI elements (buttons in this case) with live’s mapping system. Whenever you select ‘ignore click’ i can’t map it in live.
You mean you want a live.button that is visible and mappable but not clickable?
The reason is : live.button is a bit weird when mapped to a midi note. The only way to have it outputting a bang on note on only is to set it to output a bang on transition to both zero>one and one>zero. But then, when you click it with the mouse, it sends 2 bangs.
That’s really annoying, since i have to always put 2 buttons : 1 regular button for mouse action and 1 live.button for live mapping.
Yes, that is annoying, and I’ve never understood why live.button can’t also be mappable when it’s not in ‘both’ mode. Maybe you should submit a feature request? For now, though, the only thing I can think of other than your solution is to filter out bangs that come too soon after the previous bang, but admittedly that’s not an ideal fix.
Ok ! Maybe it’s feature request time (i seem to be not alone to be bothered by live.button).
Filtering bangs is a good idea, thank you !
feature request for sure :)
but for a fix, if you know there’s always nothing but 2 bangs coming from live.button at a time, instead of trying to filter by timing, ‘zl group’ is nice too:
----------begin_max5_patcher---------- 559.3ocuU1rbiBCC.9L4oviOylgeRSn6s84nSmLlfCwc.aFaQZZ6z28ZKvIj tIaHY6jCfwRBgzmjEeLIflq1wMTxuIOQBB9XRP.JxIHnee.slsaUEyflQk7W U4uPC6TA7c.JFHu1BdopVnhCvaM7NOSc5HO2qU1VKjV8n+h6E1vfUaDxxkZ9 Jn6sRShlFERRliKoywM1mG5ntuzQdZsRBFw63mNNw9RchEEXbZi8eEufNvVI qFsk9GsfUQcJ9bxD2sv+OjznEx8H4JS5zzTbY1ER5nwmzw2kjFH4msKHmIKu 41fznGQVL6mqMH5tPj2qHIjRspsgjbVzPCsWmFMIW9DRFBkEoW.MIiFMY+rj ATkkUb59DQa8Hv0K4RVdEeXe7eAF2QnqukI9woO3PQlmHipkY..VbKoYkXKe ZdK.JoOW2xz6w2ITeJTDe1dj8gOnYRi.DVGMnrdsyUmgKwO3uOd5reThgskW rjAfVXSL9gmL8XpmSNPT0xUq8h8xGhfJkr7e.qir0rQogwZrmgImPWssBhYo +Xv2pJs08zWsds6PpC4O2YH1c3W5aUPFZiG42+oJVGbxOt+wnZ0q7E3dzRNT IJ3FPHY9J8SG9+0.i1HJJ3xgmhJDFW2DVvhNYi7nCmEiHdxtagS1XnSz8iNQ iIdhuawyXJV2Zzz0YyZZ1x0ldWhAhcF3KJsa67PbqP1sEGbP07sBu8KPILsc hDXGG0p6N9ta9L63V624yIeARXAdDB -----------end_max5_patcher-----------
Hi Raja, how does the zl 2 group 2 work ? The first 2 is the length of the list ? Do you have to give it as an argument ?
There’s something else I don’t get and never noticed : live.button is set to bang on both transitions type but it doesn’t when you uncheck the toggle. But if you connect a print to the live.button, you see that two bangs are sent when you set the toggle to 1…
+ 1 for bug / feature fix, call it the way you want…
- This reply was modified 3 weeks by Stephane Morisse.
hey SM, hope I am getting at what you’re after.. the zl.group object puts out lists of the size you determine as argument after it has received as many items (iterated or in lists). This will not work with bangs though, hence all you need to do is send your live.button’s bangs to a toggle object (1/0) and either place a ‘sel 1′ object after it to filter out the zeros or a ‘zl group 2′ object – the latter would require a ‘loadmess x’ so a zero>one transition of the live.button will output from zl group and not the other way around, another bang afterwards would then be required too for neutral processing. the ‘select 1′ options is maximum good though: live.button > toggle > sel 1 > bang (when receiving message 1).