Ok so I have just encountered a rather strange bug, linked to MUL and METRO but not only. Maybe you have seen it as well then? Try this:
ENC0/VAL -> MUL/A (B=1, TRIG=1)
MUL/VAL -> METRO/PER
METRO/TICK -> WW/CLOCK
If you then modify MUL/B, no matter what you do (let’s say you change it to 2, or even 0) the period of METRO goes to 5, and turning ENC0 won’t change anything - putting up the period directly on the input page will work though. Note this is only the case with MUL/TRIG=1 and there is no problem whatsoever with ADD, for instance. Now it does the same with STEP instead of WW, and you might even wonder why I am stating this… Well, it’s because without a sequencer attached the issue disappears.
My idea was to modify the period from within a sequencer, which I used to do with STEP long time ago and without any problem. When I tried the whole thing started blinking like crazy, and after a while I found it. Any idea about where it comes from?
Edit: in the METRO object I found a modification, line 136, going from “net_activate(metro->outs, metro->value, &(metro->super));” to “net_activate(metro, 0, metro->value);”
Same, in the MUL object I found two modification on line 62, going from “net_activate(mul->outs, mul->val, mul);” to “net_activate(mul, 0, mul->val);”, and on line 71 from “net_activate(mul->outs, mul->val, mul);” to “net_activate(mul, 0, (float) v);”. Unfortunately I can’t tell if any of this is the reason why this problem appeared, only thing I know is those were recent changes. I am therefore putting it up in case it could help see the issue faster. Also, my apologies for not being a better programmer, even though I am working on my C skills at the moment.