preventing midi talkback from messing with scripted actions

[mssngmrblz]

I have a knob set up as a DJM mixer style filter.

I have a script that returns the knob back to home (0.5)

when i sweep the filter up (for example) and let go of the knob it executes the script and returns the knob back to 0.5 in about 1 second.

problem is...sometimes midi is feeding back from ableton and messing up the knob position.

i don't want to disable 2-way midi cuz it's awesome.

Is there a way to prevent midi talkback the from messing with scripted actions on controls?

[Softcore]

What I have figured is that

Cursors (your finger on a control) and midi feedback are ALWAYS prioritized over scripts and physics. I had the same problem with physics, any feedback back into Lemur from the DAW would "stop" the moving of a multiball which was caused by physics (no friction).

I reckon the only way to go, is to create custom expression or midi out, only for that knob and sacrifice the feedback (only for that knob, not the whole template).

[mssngmrblz]

do you know of an easy way to tell lemur or max4live "hold on there for a second....wait until this object isn't spittin' digits before trying to make it your bitch already!"

i'm imagining a 'gate' that is uni-directional just till the fader stops outputting changing values...then 60ms later BOOM! bi-directional again!

i'll work on it with u if you help me start it.

[Softcore]

Can you post the single knob-script combo that does what you describe in your first post? because, frankly, what you are asking could be possibly achieved with on frame scripts and custom midi messages but I believe there must be a faster way....

Also, inside Ableton Live options, what is your setting for the "takeover" mode in preferences for midi? I really don't have any problems with the feedback with similar functions like the one you described - once the script is doing something to the objects, then they send their new value out so the feedback is always correct. Do you have the "back to 0.5" function "delayed" or "timed" ? ....

So many questions....having the specific script you use would definitely answer them all!

[mssngmrblz]

returnKNOB.jzlib

returnknob

(3.69 KiB) Downloaded 98 times

I really appreciate the help here.

Here is the script attached...i'm excited to hear what you come up with

thanks

[Traxus]

That file is crashing my editor when ever I try to open it, but I've been working around similar difficulties.

Where applicable, I've been using the z variable to flag which action it should listen to. Alternately, sometimes you need to store an 'action is active' variable and use that to help determine what script it should listen to. (As in 'fade_out_active = 1' or something)

[Softcore]

@traxus

Teh infamous "Im crashing if you got a bipolar knob and not the classic skin saved with the template-library" bug.....
For future reference: open options of editor, disable "always use project skin" and select classic and it will load just fine.... (in other words you force the editor to open the file in classic skin, regardless of the skin it was saved with)

Now, to OP: Do you actually map that button in the middle somewhere too? Im not getting artifacts here - as in, as soon as I mapped the knob, it works as expected ...

[Softcore]

No wait - got em....ok I 'll be back!

[Softcore]

Ok here's what I dont get.....

We move the knob in Lemur - it returns to 0.5

What do we want it to do when we move the mapped control in the software? If we want it to re-adjust to 0.5 as soon as we leave the control (in the software) what's the meaning of having bi-directional feedback? The knob is always returning to 0.5 anyway.

[Softcore]

Here's case 1.....The knob returns to 0.5 when interacted via Lemur, stays where it is when interacted by the software....probably not what you are after - I think you want the knob to return to 0.5 in all cases - Im working on that

ReturningKnob-case1.jzml

(3.6 KiB) Downloaded 100 times