[PD] accuracy of signal/message-objects (was: Switch and ramp and accurate timing)

[Roman Haefeli]

i made a little vsnapshot~ test patch. it seems that [vsnapshot~] is not
working as expected, though it definitely gives other results than
[snapshot~].
one issue might be introduced by the rounding error of floats. the other
i cannot explain. vsnapshot~ seems to pick sometimes the wrong value.

roman


On Mon, 2007-05-07 at 09:40 +0200, Frank Barknecht wrote:
> Hallo,
> Roman Haefeli hat gesagt: // Roman Haefeli wrote:
> 
> > it would be very cool, if [snapshot~] and [threshold~] (and maybe
> > others) would provide sample accuracy as well (when triggered by [metro]
> 
> Now I discovered something: Pd (at leat 0.40 up) has a [vsnapshot~]
> object!! It should do what the name hints at: Provide clock-accurate
> sample measurements.
> 
> Unfortunatly simply replacing the lower-right snapshot~ with
> vsnapshot~ didn't get rid of the clicks. Strange ...
> 
> Ciao
-------------- next part --------------
#N canvas 546 0 366 477 10;
#X floatatom 12 131 0 0 0 0 - - -;
#X obj 12 109 vsnapshot~;
#X msg 13 53 10;
#X obj 69 79 metro 100;
#X msg 69 56 1;
#X obj 13 76 phasor~;
#X obj 13 20 loadbang;
#X floatatom 12 319 0 0 0 0 - - -;
#X obj 12 297 vsnapshot~;
#X obj 13 264 phasor~;
#X obj 13 208 loadbang;
#X msg 13 241 50;
#X obj 69 267 metro 20;
#X msg 69 244 1;
#X obj 12 348 t f f;
#X text 7 178 is this the rounding error of floats?;
#X obj 11 373 -;
#X floatatom 11 397 0 0 0 0 - - -;
#X text 10 424 why this discontuinities?;
#X text 9 158 phasor (10Hz) and metro (100ms) do drift apart.;
#X connect 1 0 0 0;
#X connect 2 0 5 0;
#X connect 3 0 1 0;
#X connect 4 0 3 0;
#X connect 5 0 1 0;
#X connect 6 0 2 0;
#X connect 6 0 4 0;
#X connect 7 0 14 0;
#X connect 8 0 7 0;
#X connect 9 0 8 0;
#X connect 10 0 11 0;
#X connect 10 0 13 0;
#X connect 11 0 9 0;
#X connect 12 0 8 0;
#X connect 13 0 12 0;
#X connect 14 0 16 1;
#X connect 14 1 16 0;
#X connect 16 0 17 0;