Gate generates two triggers
-
Did you reproduce this on Windows?
Its not happening for me on Win 10 Isadora 2.6.1 -
-
Hi,
I'm on Isadora 2.6.1 and High Sierra 10.13.6. The same as @Reinhard; if trigger from Trigger Value actor the Counter adds 2 through the Gate. It is solved if an Multi Blocker actor is added, although I suppose the idea is to know why.
Best
Javi
-
What of you change the keyboard watcher to mode "up" rather than down?
-
I can confirm the bug 2.6.1 and following.
I've noticed that if you initialize cur value to "1" the bug randomly appear, some time it do a pair succesion of number then it switch to a unpair sequence like some time the bug appear ( ost of the time) and sometime it works as expected.
The bug is present if you trig manually trig box in trigger value actor and also if you link it to a control pannel button, but if you trig it with a pulse generators it works fine
-
Can you post a test file? I just can't get this to happen.
-
Out of curiosity I checked older versions of Izzy and could reproduce this (obviously not for everyone) bug down to version 2.2 (nothing older available). Rebooting - same.
As it took me some time to isolate the problem out of a more complex patch, let me know if I can be of further help to investigate.
best
r
-
Can you post a patch with this behaviour? I can't reproduce it.. I have tried a number of times.
If you file has the same behavior on my system I will be able to report the bug for correction. -
Attached. Counters 'cur value' are initialized to 'MIN' - but it makes no difference if so.
-
@DusX patch posted down here by Reinhard got bug as mine so I don't double post.
BTW just to be sure ( 'couse initially I did this mistake) do you press the 'trigger box' in trigger value actor? the bug appears only when you manually do it ( or when you do it with a button in control interface)
-
@reinhard also in your patch the sequence switch randomly from even to odd.
I have to investigate if cycles are involved
-
I found out what the problem is, I don't know why but you can get around it without extra actors.
If you connect the output of the "gate" actor first to the trigger input of the "counter" actor the "mutable" input will turn into a trigger and then it will only trigger once. If you first connect the "trigger value" actor output to the "mutable" input of the "gate" actor it will make the input a number. Then it somehow triggers twice.
Best Michel
-
OK, so your file does it for me.. but building the same in a new file doesn't.
-
@michel
I saw that, but strangely I can't reproduce it in a new file. -
@michel brilliant debug
BTW I have to say that this problem is a false problem. I can not imagine why some one have to connect a numeric value to a trigger input :-)
-
If you first connect the "trigger value" output to the "gate" input and then the "gate" output to the "counter" trigger input this happens at least on a Mac. Did you try it on Mac or PC.
Best Michel
-
Because it triggers? So far this seems to me as an obvious way of connecting actors. Thanks to @Michel I will take more care of the Mutables in the future. Comfort has its price.
-
-
Yes its true, it does not happen in the beta 3. But it does happen in 2.6.1 and in the beta 2.6.2.
Best Michel
-
I have it on beta 3