Im hitting a brickwall for case2...
There is a way to "wait some time" before feedback is sent back into Lemur but there is NO way to tell whether you have "left" the mapped control in the software or you are still touching it (no z from Live back into Lemur). So there really is no way to prevent the timer running out and the knob resetting to 0.5 even though you may still be holding the control in Live with your mouse....
preventing midi talkback from messing with scripted actions
-
- Newbie
- Posts: 40
- Joined: 03 Feb 2013 15:08
Re: preventing midi talkback from messing with scripted acti
I know this is a little late....but Softcore I wanted to thank you!
it works great!
What exactly did you do to the knob to allow this? i'd like to do it to some other controls!
it works great!
What exactly did you do to the knob to allow this? i'd like to do it to some other controls!
Re: preventing midi talkback from messing with scripted acti
Study the "reset" script which is "on frame" and notice the "speed" and the "t" custom expressions. Also notice the "set t" script.
Once you let go of the knob z goes 0, so t goes 0.
The on frame script is executed only if t = 0.
So it starts executing.
Once the knob goes "near" the 0.5 value it "locks" to 0.5
and t goes 1 so the "on frame" script stops being executed.
Once you let go of the knob z goes 0, so t goes 0.
The on frame script is executed only if t = 0.
Code: Select all
if (t) return;
Code: Select all
if (Knob.x>0.5) Knob.x-=speed;
if (Knob.x<0.5) Knob.x+=speed;
Code: Select all
if (Knob.x>=0.5-speed && Knob.x<=0.5+speed) {Knob.x=0.5;
and t goes 1 so the "on frame" script stops being executed.
Code: Select all
t=1; return;}