sixtin

Or am I doing something obviously wrong. Max 5.1.3, OS 10.6.3

clocker-and-problem

Ok, so in my case, a delay object would just do what I wanted for this (I always forget about the really simple objects) but can anyone still shed some light on why this may not work?

The [t b stop ] object is being triggered by the output of > even when the comparison output is 0. You need a [sel 1 ] between them. And then you will need to adjust the argument of > to give you the right amount of delay.

The [t b stop ] object is being triggered by the output of > even when the comparison output is 0.  You need a [sel 1 ] between them.  And then you will need to adjust the argument of > to give you the right amount of delay.


OF COURSE! For some reason I had it in my head that > only triggered a 1 when the expression was matched, not 0 and 1. Feeling foolish.

clocker and > problem