From 2 values, delay one of them...
-
Thanks Reinhard!
-
lets see. I have a new complication: I attach an izzy file for the example.
In the example, when "limit scale value" receives a value under 99, the bypass in "auto-fade" is on. When "limit scale value" receives a value over 100, after 2 seconds the bypass in "auto-fade" goes off.so far so good.now, there are some tricky situations in which the values change in the middle of a change of state in the bypass, which reverts this behaviour. And this, in my patch, happens very often. How could I prevent this??? -
Dear,
sorry, I don't get it. You want a value between 99 and 100 to switch something. If you set an inside-range-actor to min 99 and max 100 it will tell you exactly that. Your downscaling with a limit-scale-value-actor and feeding this into an inside-range-actor set to min 0 and max 0 does not make any sense. Try this - if the value is other than 99-100 you get a 0, if it's in you get a 1.best r -
I understand reinhard, but this is not my problem anymore. I took away limit-scale-value-actor to try to explain my new problem in the new example attached.
case 1-If I send an "enter" (from now on called "on"), the macro turns on-If I send an "exit" (from now on called "off"), after 2 seconds the macro turns offcase 2-I send an "on", the macro turns on-I send an "off", after 2 seconds the macro will turn off-before this 2 seconds pass, I send an "on"In case 2, I would expect to have the macro "on", since the last signal I sent was "on", but because there was an "off" already on the way, that arrives after the 2nd "on", the final macro state is "off".how can I prevent this? -
-
yes!
I knew gate was the way, but the implementation was my problem.thank you very much! -
Attached a solution with a gate actor, as soon an on trigger gets sent the gate closes until a off trigger gets sent again.
Best Michel
f2dfc3-untitled.izz -
same but more clever - that makes the difference between user and guru...
-
-
thanks!