General

Prevent button from triggering on external trigger

Started by shinz on .

Sign in or create an account to join the conversation.

5 posts

shinz

Last updated

Topic starter
Hi,

I'm using Lemur since some days and I'm a big fan. But I have a problem in combination with Cubase. The cool thing is that Cubase also can send out a trigger to Lemur when you press the mute button of a track for example so that Lemur can follow the status of your DAW in a way. The problem is that when Cubase sends out that trigger, it's not just changing the buttons status...the button is triggering the daw again when the status is changed. So I press the mute button in Cubase, the button changes it status and is unmuting the track again.

Is there a solution for that?

Best
Stephan

ndivuyo

Last updated

Yea you want to add a script to prevent midi feedback.

Often times (depending on what object you are t=using) the 'z' expression is good for this. If z is equal to '1', that means that you are physically pressing down on the object. Therefore writing a script with this condition will prevent feedback.
I don't know the best way to do this for your project, but I like to use ctlout() (or a custom midi expression) with this condition:

Prevent 'x' from being ent to cubase by default. And then have a script execute on expression x:

if (z == 1) {
ctlout(arguments);
}

This way when the button x value is changed, but z does not equal 1 (meaning you are not pressing it down), then the value is not sent to cubase and no conflicts.