Multiplex & Not together - bug?

[Nowhk]

I'm not really an hero with mathematical logic, but this makes no sense at all:

Immagine.png (111.58 KiB) Viewed 6549 times

I want that, when I'm not playing DAW (Is Playing=false, so with "not" true) and when the two values are equals (the first Multiplex output and the 0.5 float), get TRUE as output to that boolean in the top (that I'll link later with a Selector and edit manually a value).

The problem is that that field never get true (even when I'm stopped and IN F is 0.5).
Also (this suggest to me a bug): once I stop the daw and I click on the FS area with mouse, the first MULTIPLEX float output reset to 0 (magically).

If I remove the "not" module, this won't happen (but I lost my boolean logic).
If I preserve "not" and I remove the Multiplex module (keeping as example a fixed 0.5 float) the same: no "bug" (but I need dynamic input).
If I remove Wireless and I put a static Module IN, nothing change (it's the same).

So the problem seems to use "not" and "multiplex" modules together.

What's happening? Am I on drugs or its a common bug? Thanks for helping.

bug multiplex not.fsm

(132 KiB) Downloaded 747 times

[Tronic]

what is the logic?
What you should do, unfortunately I did not understand?

[Nowhk]

:? what is the logic?
What you should do, unfortunately I did not understand?

When I stop the DAW, I want to read/process the last value I get from "IN F" module: if its equal to 0.5, I want to change it a little bit (let say +0.0001).

So:

if 0.4 and stop=>0.4
if 0.5 and stop=>0.5001
During playing, nothing must change.

I need Multiplex because when I stop DAW, my plug will reads/swap automatically to another value (the first in the sequence), without keeping the current one (the first float on multiplex will be linked to an output port, so change will be ignored; that's why I put it on the chain).

So I don't output the first one when I stop, and I change a little bit the last. When I'll restart the sequence, it will be different from the real value of it, that is 0.5).
Its a problem related to this trouble, about retriggering a same value: if it won't be the same (but a little bit different) it will be retriggered as well.

Is it more clear now?