I feel this is a head-slappingly stupid question, but is there any way to tell when vline~ has finished its run?
like a bang at the end, or something? i am feeling quite dense right now.
(ditto with line, or line~)
thanks
~s
Hallo, Scott Fitzgerald hat gesagt: // Scott Fitzgerald wrote:
I feel this is a head-slappingly stupid question, but is there any way to tell when vline~ has finished its run?
It will end when it's done with doing what you told it to do. ;)
You always know when a vline~ (or line~ or line) object ends, because at some point in the past you have started it with a certain desired duration. When that duration has passed, the line ends.
E.g. you send a "10 1000" to vline, then that segement will end after 1000 msec. No need for an extra bang.
If you still want that extra bang, just duplicate your delay time to a [delay] object as well, scheduled with a [trigger].
Frank Barknecht
You can follow all those complicated methods (which get more complicated
if you're planning to use lists), because pd isn't max, and therefore some
objects must behave differently in order for pd to be independent.
Or, if you don't really need the extra precision in the line, you can use
Line~ from cyclone. there you have the bang in the end of the line, just
like max.
Hallo, Scott Fitzgerald hat gesagt: // Scott Fitzgerald wrote:
I feel this is a head-slappingly stupid question, but is there any way to tell when vline~ has finished its run?
It will end when it's done with doing what you told it to do. ;)
You always know when a vline~ (or line~ or line) object ends, because at some point in the past you have started it with a certain desired duration. When that duration has passed, the line ends.
E.g. you send a "10 1000" to vline, then that segement will end after 1000 msec. No need for an extra bang.
If you still want that extra bang, just duplicate your delay time to a [delay] object as well, scheduled with a [trigger].
Ciao