Delay object bug?
Hi,
I found out that delay object stops sending out bang when delay time is bigger than 1000ms (1000.1ms, 1001ms).
I had the same issue with both Max 7.3.5 and Max 8.0.2.
It doesn't seem to be the expected behaviour and I can't figure out what I'm doing wrong.
Did I miss something regarding the delay object preferences?
Notes: I tried to set delay time with integers, floats and messages. But I had the same results.
If anyone can help me, that would be greatly appreciated.
I ran another test and I realize that my explanations were not sufficient enough.
What I'm trying to do is to feed a delay object with a metro.
And while the metro object is running, it looks like the delay object can't accept delay time bigger than the metro interval.
For instance if metro interval is 800ms, the delay time can't be greater than 800ms.
Is it a kind of safeguard for the delay time?
Quote from the reference page: "If a bang is already in delay when a new bang is received in the left inlet, the first bang is forgotten."
But you could use [pipe] instead (replacing bangs by numbers).
Oups!
Thank you BROC.
I completely missed this detail.