Forums > MaxMSP

how save are delay's bangs?

Dec 09 2008 | 11:46 am

I discovered some strange behaviour of delay. Sometimes bangs are not delayed anymore.
Yesterday I had the case, that a "delay 1000" outputed a bang without any delay ("loadbang" -> "delay 1000" -> "bang"). After reloading delay it worked. It happens not that often (nearly never), but it seems to happen?

macbook, OSX 10.5.4
2GHZ Core Duo

Dec 09 2008 | 12:06 pm

I’ve never experienced this myself. If it works correctly after reload, are you sure you aren’t sending an unwanted number to the right (or even left) inlet at some point in time?

Dec 09 2008 | 12:32 pm

no, I had the problem in a more complex patch first, where some delays were delaying some loadbangs. Then I just copied the part "loadbang" – "delay 1000" – "bang" in a new patcher (nothing else) for testing. The problem still existed there, until i reloaded the delay-object.

Dec 09 2008 | 12:33 pm

and yes, there were only bangs in the left delay inlet

Dec 09 2008 | 5:22 pm

I don’t know much about that all, but could there be some situation in which the bang from the loadbang object is sent before the argument of delay object is taken into account?? I remember having encountered a situation in Jitter where I had to delay my loadbangs a few ms to get the proper attribute values of a jit.pwindow or something like that…

Checking your stuff with a timer object, I don’t encounter your problem anyway. The timer value is the same as the delay argment.

All the best

Dec 09 2008 | 5:35 pm

make sure you bang and delay bang from the right side in your patch eventually?


Viewing 6 posts - 1 through 6 (of 6 total)

Forums > MaxMSP