MIDI Kinetics Forum

Hey

I have set up a Lemur template with Live to arm some tracks and also launch scenes. My problems is that I am having to double tap the button every time in switch mode, anyone else had this problem?

Cheers
Steven

I think the answer I got from Softcore on this forum, is the same answer to your question too:

https://forum.liine.net/viewtopic.php?f ... 585#p17911

Yup, you need "pads" not "switches" even though "arm" buttons inside Live are of switchable nature.....Blame Ableton designers for that - never understood the reason why they did it this way....

You can set up a script on the switches to send a double 127 value each time you press it. Then assign that variable instead of the 'x' value.
I think..

any chance of posting that solution?

I don't know the first thing about scripting.


suppose I need to rtfm.

Yeah if someone could provide a script to have an arm button with indication whether or not it is on or off that would be great.
Same situation for when scenes are launched, having to double tap.

Guys, you really need to understand what Im saying here.......DUE to the silly programming of said buttons by the devs of Live, a PAD works as you want - NOT a switch.

Now, there are 2039484 ways to make a pad (pressed 127, released 0) to behave VISUALLY like a switch.....BUT YOU STILL WONT HAVE ANY SORT OF "CONNECTION" ABOUT WHETHER THE ACTUAL BUTTON INSIDE LIVE IS ON OR OFF AND THE RELATED BUTTON IN LEMUR. In simple words, EVEN if I provide you with a solution, its bound to happen that the arm button in Live will be OFF and in Lemur will display "on" or vice versa.

many hardware controllers have two elements for one function: one indicator LED and one pad. The pad sends only a short message to the DAW, and the DAW sends a "on" message back as long as this function is activated (switch behaviour). In such cases I usually replicate this in Lemur. Use an LEDs object as indicator and a Pads object. The LED only receives data from the DAW, the pad only sends data (not receiving anything). Then you have the exact same happening in the DAW and in Lemur.

I don't know how it is in Ableton. Just recently I had to use this method again for a controller for Harrison Mixbus.

Your observations are correct Phill. Im quite sure the "solo-monitor cue" buttons in Ableton Live do NOT send any sort of feedback at all (even though they are of "switch" nature).
I will check today for the "arm" buttons, but Im quite certain they follow the same idiotic design.

Hmm, I see, couldn't this be an m4l patch solution though? You could do it in the MIDI Remote scripts, but I don't know how to do that. I'll have to look at the LOM, unless someone knows if you can get that part of the API.