MIDI Kinetics Forum

Hello fellow Lemurers.

Please can you help.

I have setup a CustomButton in "Switch" mode to work as a CYCLE button in Logic Pro X.
It is receiving from OSC.
It will activate Cycle within Logic Pro when it goes into "On" state but when I press the switch to "off" state, the Cycle mode still remains on in Logic.

It will only go off in Logic when I press it once again, which results in the button being "On" but Logic's Cycle Off!

Before:


After:



Thanks in advance!

Your friendly Lemur Fan Dan
aka SupernovaParanoia

I don't have logic, so I can't test, but..
My guess is that the 'cycle' state is change whenever it receives a '1'. Soo when you activate it the first time, it gets a '1' and turns on. Then you turn it off with a '0'... nothing happens because it's not a '1'. Then you turn the button on again, and send a '1', which changes the cycle state to 'off'.

So there may be a few ways to work with this. One way is to change your button to 'push mode', thus sending a '1' each time you send it. Then use some kind of led (with leds, or text, or canvas, or another object) to remember if the state is on or off.

You can also create a separate variable that sends a '0' followed by a '1' each time you press the button, keeping it as a switch.

There are more solutions, but you want to keep it mind that: unless you just pay attention to it, the cycle's state has to start out the same as seen on lemur, or they will be out of sync as you'll only send '1' to change it's state.

Anyway this is all speculation as I don't have the means to test..

Hey Ndivuyo

Thanks for the quick reply.

Yes, I assumed this was the problem too. You are correct that the "pad" mode does work every time I press it but then
the visual aspect returns to "off" state.
I would be interested in creating a variable that sends both 0 & 1. I think that would be the best course of action, though my coding skills
seem to be letting me down here. Any ideas?

Cheers mate
Your friendly Lemur Fan Dan
aka SupernovaParanoia

try this, not sure if it works (obviously can't test)

The way I know how to send out custom OSC variables is to make 2 variables. The first one is the variable with your value, and the second one is equal to the first variable. Then you can send the second one out to the DAW/wherever (the first one cannot send to your DAW for some reason I can't remember, but it won't work, nothing will be sent).

Anyway, if this doesn't work it is because the 0 and 1 are sent too quickly together that the Logic never gets the 0 first. But hopefully it will!