> Does vline also have to wait for a block boundary when first triggered?

this is probably cleared out and not sure if this is the question, but vline~ will respect the schedule timing of events with a delay of one block, meaning that it'll convert the events to audio rate but only for the next block.

now I wonder what happens for blocks that are smaller than 64

cheers

2015-09-26 9:24 GMT-03:00 i go bananas <hard.off@gmail.com>:

Thanks,

I guess here is my question put better:

If i make a line and a vline object, and feed them both a [1, 0 50( message, they perform differently. The line object jumps around, presumably cos it is tied to block boundaries.
But the vline always triggers exactly the same.

It's as if somehow the vline~ works outside of the block structure. Does it actually do that? Say you're at sample 47 of a 64 sample block, does vline jump the queue and trigger right then?

Or i guess, even more succinctly, i was assuming that everything in pd got triggered in blocks. Is that the case? Does vline also have to wait for a block boundary when first triggered?

Sorry, there's obviously some 'aha' moment i'm failing to have here.

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list