Gate generates two triggers

[Reinhard]

Hi,

as simple as that:

If I hit the letter 'a' on the keyboard everything is fine BUT if I click the trigger field in the Trigger Value actor, the Counter behind the Gate receives TWO triggers. Can somebody reproduce that and if so, is it a bug or am I missing something fundamental?

best

r

[Juriaan]

Hi there @Reinhard,

EDIT : I see what you mean now.. Let me investagate a bit further

IzzyReinhard25March.izz

[Reinhard]

@juriaan

Thanks. But same result - Keyboard Watcher works, clicking adds two.

[Juriaan]

Yeah on it.. It seems that if you use two Gates, instead of one that everything is operated as expected. See the below file for a new version that works 

@DusX Could you check or this is an user error or an actual bug ? If so, could you log it ? (Isadora 2.6.1, Windows 10 here)

IzzyReinhard25MarchFix.izz

[Reinhard]

@juriaan

Ok, it's workaroundable - but at least strange.

For the investigators: if I use a Sequential Trigger (which outputs a trigger instead of a number) it's the same, if I use a Trigger Delay all is fine.

[Juriaan]

Yep, couldn't agree more with you. That is why I asked of one of the staff members to explain the behavoir or if it is a bug to fill a new ticket

[DusX]

@juriaan

Did you reproduce this on Windows?
Its not happening for me on Win 10 Isadora 2.6.1

[Michel]

@reinhard

I can't recreate this. Tested on macOS Sierra and Isadora 2.6.1.

Best Michel

[jandraka]

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

[Skulpture]

What of you change the keyboard watcher to mode "up" rather than down?

[Maximortal]

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

[DusX]

@maximortal

Can you post a test file? I just can't get this to happen.

[Reinhard]

@dusx

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

[DusX]

@reinhard

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.

[Reinhard]

@dusx

Attached. Counters 'cur value' are initialized to 'MIN' - but it makes no difference if so.

two trigger gate.izz

[Maximortal]

@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)

[Maximortal]

@reinhard also in your patch the sequence switch randomly from even to odd.

 I have to investigate if cycles are involved 

[Michel]

@Reinhard 

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

[DusX]

@reinhard

OK, so your file does it for me.. but building the same in a new file doesn't.

[DusX]

@michel
I saw that, but strangely I can't reproduce it in a new file.