What I mean is that both [line~] and [vline~] receive their messages on block boundaries.

But unlike [line~], [vline~] can start/end ramps and jump to the values you give it without being

limited by block boundaries.

Another example with my day-long block sizes:

At noon on Monday you send a bang to [metro 150]--[tgl]--[vline~].  You'll have

to wait until noon Tuesday to hear the result, but you _will_ hear that same pattern of ones and

zeros spaced 150ms apart that you were sending on Monday, even though the block size lasts a

day.  That's the strength of [vline~].

On the other hand, the [line~] object would just take the last [tgl] value it received on Monday

(before it begins computing Tuesday's block), and it would just repeat that value the entire day of Tuesday.  If you had sent it a ramp time, you would get your ramp Tuesday, but it would necessarily

stretch across the entire day of Tuesday because that is the block size.

Essentially-- you can't send a message that would interrupt the [vline~] object's perform routine

and feed it new values.  But because block sizes are usually small, I can't think of a

situation where you'd need to do that.

It occurs to me I could be wrong about any or all of this.  If so I'm certain Matt or Miller can set

me straight.

-Jonathan

-Jonathan

On Saturday, September 26, 2015 10:24 AM, i go bananas <hard.off@gmail.com> wrote:

In that case, maybe an even simpler question:  

What is the difference between sending a [1, 0 50(  message to vline as opposed to line ?  

Why does line exhibit jitter, if both only trigger on block boundaries?