Pad w. framecounter won't work without monitoring. WTH??

[marduk]

I wanted to make scripted button(s) that send continuously while pressed (x=1), but not too fast you know - it's sysex after all.
But now the frameCounter script will not reset without monitoring the button output. I don't have the slightest idea what's going on... You'll see when commenting out one (or both) Monitor objects' values,
Also one button sends 2x slower than the other. With exactly the same script. And the behaviour is intermittent (between buttons).
Does this have to do anything with different scripts changing the same variable (not simultaneously, tho)? Do I have to make different framecounters for different knobs? Sounds bit backwards...
And yes, I'm rather new to this, thanks.

[marduk]

OK, just doubled every script and expression and the button output speed went equal.
(I also contacted and called the department of redundancy department)

But the frameCounter still won't reset without monitoring the button output script

[MrCorba]

I don't know what that problem is, there is an issue like that with a while-loop, but I think I've found a work around for you. There's 1 script continuously counting frames and sets a variable to either 1 or 0 every x times. Then there's a pad that also has an on frame script checking if the variable is 1 and if the pad is pressed. It's not a memory friendly if you've got a lot of them but it should do the trick.

Cheers