Strange LFO behaviour

when setting Period to 0.0000s the Cycles Output behaves a bit strange.

bug or not?

see attached patch

LFObug.v4p (5.2 kB)

what should be the desired behaviour? stop and do nothing?
hey, you just shouldn’t put 0.0000s into it?!
normally it should run infinitely fast, since our LFO can’t it just runs as fast as possible.
better than doing nothing, isn’t it?
seb

the iobox display seems to have smaller value range than internal processing. if you set the lfo time to a very small value like 0.000000001 you will see the iobox running fast out of range …

LFObug2.v4p (7.1 kB)

sorry for replying that late…

hey, you just shouldn’t put 0.0000s into it?!

but in fact it IS possible to put 0.0000s into it…

normally it should run infinitely fast, since our LFO can’t it just runs as fast as possible.
better than doing nothing, isn’t it? what should be the desired behaviour? stop and do nothing?

thats logical to me like it was before. but when you need the cycles information and put (perhaps accidentally) your 0.0000s into it your cycles information stops. for at least a long, long time.
so my opinion is “better stop” …

another one for the top of priorities
i know that ;-)

seb