Delay Simply Doesn't Work
I have been losing my mind. I need to use the delay object and I feel like I'm doing it all correctly but when I put the delay in, nothing happens. Nothing can get through.
I have tried creating a new device, restarting my computer, restarting max.
Someone please tell me what I'm doing wrong lol
there are two user errors which happen to people regulary:
the signal [delay~] requires two arguments to work, and the [del] object works for bang only, while for numbers you need to use [pipe].
what i see in picture 1 should work, and it should work no matter the runtime version or settings.
I have the same issue, seems to be some kind off bug. It also works sometime. It just stops working at some point.
Not really a bug. [del] delay usually works, but has never been 100% reliable. I dont know about in LIVE.
Best to use [pipe] - never need [del]
Don't know why both objects even exist. I find this same in other object like [t] arguments.
Dont really need [t i] or [t f] when [t l] works for all.
have you set the delaytime in ms? when set to ticks or bbu the transport have to run to output after x ticks.
del exists because pipe could only do numbers back in the days.
i think it is correct to say that del kinda "does not buffer the input", which makes it faster.
@WIL They're quite different, since pipe passes through output for all input and delay resets its timer on every input. I use delay routinely as a way to coalesce notifications and output just one trigger when all the inputs are done.
Which is not to say that I never found the differences between delay and pipe mildly confusing or unintuitive!
