[PD] precise milisecond/second counter

ilya .д errordeveloper at gmail.com
Tue Nov 20 05:52:00 CET 2007


hello list.

i was terribly surprised the way [metro] behaves -

checking it agains [timer] of coruse doesn't give any latency ever!

but with [realtime] and [cputime] - the result is is far from acceptable
and even unproportional, (icresing twice doesn't give any aproximatable
result).

how ever the system load was quite hight -
/proc/loadavg: 3.29 3.31 3.54 6/268 22074
and even > 5.0  at some point..

i run linux 2.6.20 with built in RT_MUTEX ..
i never noticed any latency while interacting via gui..
how ever there was a bit of acceptable audio latency when i was
programing some effects using live input and comparing to pd's streight
wire from adc~ to dac~ (inside a busy patch) there was a noticable delay ..

however i assumed [metro] to be closer to ideal , really ..

so i have actually made a patch which give a very precise ticking.

please have a look ..

-- 
cheers, 
ilya .d
-------------- next part --------------
#N canvas 113 339 691 362 10;
#X obj 256 143 bang~;
#X obj 301 160 i;
#X obj 369 177 + 1;
#X obj 369 222 mod 1000;
#X floatatom 535 298 5 0 0 0 - - -;
#X obj 468 194 sel 1000;
#X obj 468 222 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144
-1 -1;
#X obj 418 105 block~ 96;
#X text 288 19;
#X obj 498 31 samplerate~;
#X msg 498 8 bang;
#X obj 498 58 / 1000;
#X msg 498 88 set \$1;
#X connect 0 0 1 0;
#X connect 1 0 2 0;
#X connect 2 0 3 0;
#X connect 2 0 5 0;
#X connect 3 0 1 1;
#X connect 5 0 6 0;
#X connect 9 0 11 0;
#X connect 10 0 9 0;
#X connect 11 0 12 0;
#X connect 12 0 7 0;


More information about the Pd-list mailing list