[PD] triggering vline~ compared with line~

[Frank Barknecht]

Hallo,
Frank Barknecht hat gesagt: // Frank Barknecht wrote:
> In the example posted, there is a [t b b] attached to the metro, which
> first bangs the tabwrite~ then the message to vline~. As messages are
> block aligned, the [t b b] might bang at block boundaries. Still
> vline~ (seems to] correctly follow the [metro 500], which might not
> always bang on block boundaries, as [metro] is driven by Pd's logical
> time. I still wonder, how vline~ knows, when in time the [t b b]-bang
> arrived. 

Krzysztof answered this for me in another thread. Attached is a little
play with a [del] that's actually behaving subblock accurate. 

Ciao
-- 
 Frank Barknecht                 _ ______footils.org_ __goto10.org__
-------------- next part --------------
#N canvas 438 215 543 493 10;
#X obj 146 219 tabwrite~ y;
#N canvas 0 0 450 300 graph1 0;
#X array y 128 float 0;
#X coords 0 1 127 -1 200 100 1;
#X restore 139 266 graph;
#X obj 145 167 vline~;
#X obj 323 69 samplerate~;
#X msg 385 32 bang;
#X floatatom 209 117 5 0 0 0 - - -;
#X obj 323 32 loadbang;
#X floatatom 156 43 5 0 100 2 samples - -;
#X obj 145 120 del;
#X msg 145 141 0 \, 0.4 0 \, 0 0 0.5;
#X text 283 141 go to 0.4 for 0.5 msec.;
#X msg 140 437 \; y const 0 \; y xticks 0 4 16;
#X obj 140 417 loadbang;
#X text 193 376 128 samples;
#X obj 156 67 t b f;
#X msg 116 93 bang;
#X obj 209 94 expr $f1*1000/$f2;
#X connect 2 0 0 0;
#X connect 3 0 16 1;
#X connect 4 0 3 0;
#X connect 6 0 3 0;
#X connect 7 0 14 0;
#X connect 8 0 9 0;
#X connect 9 0 2 0;
#X connect 12 0 11 0;
#X connect 14 0 15 0;
#X connect 14 1 16 0;
#X connect 15 0 8 0;
#X connect 15 0 0 0;
#X connect 16 0 5 0;
#X connect 16 0 8 1;