Counter and null

vvvv beta bug
1

Hi,
Pretty minor bug. But sort of a pain.

if a null is piped into the counter node it seems to permanently lock it in a null output until restart. Tried using the reset pin, and disconnecting everything, couldn’t get it to start outputting again.

Noticed this when piping an OSC message into the ‘up’ pin. The very first frame sends a null, but after that ‘count’ pin was locked in a null.

Only work around that I could find is to run it though a switch and activate it after the first frame.

cheers

2

Try this)-and-read–((empty-spreads).
From your description it´s still a bug though.
A patch demonstrating the problem will help to speed up the bug fixing.

3

Thanks didn’t think of avoidnil since it’s just for a single number.

May be wrong about the bug, tried throwing together a quick example with a nil and it worked fine. So it may be somewhere else in my patch.