On Fri, 2015-03-13 at 04:51 -0300, Alexandre Torres Porres wrote:
> I'm aware that CPU can choke on an absurdly fast control rate. > Nonetheless, the concern and question is not to how much the CPU can > take, but how small a period of time Pd could consistently and > steadily send messages. To make it simple, the smallest time an object > like [metro] is able to operate. In practice, it seems that the smallest time interval measurable by [timer] is dependent on how long you have Pd running. Attached is a patch that sends two bangs with an interval of 6.8e-11 every second. It seems that the first 1217 seconds you get a non-zero result from [timer] (though the result changes during the first few seconds). After 1218 seconds of running Pd, [timer] measures 0. To give your question again a different answer, it seems that there is no absolute minimum time interval in Pd, but it increases over time of running Pd. Roman p.s.: Make sure to open the patch right away like this: pd -open shortest_time_intervall.pd if you intend to get consistent results with the numbers above.
#N canvas 953 226 474 348 10; #X msg 27 79 1.35e-10; #X msg 89 78 6.8e-11; #X msg 145 78 6.7e-11; #X floatatom 27 128 10 0 0 0 - - -, f 10; #X obj 27 147 t b a; #X obj 27 190 timer; #X obj 54 168 delay; #X floatatom 27 217 10 0 0 0 - - -, f 10; #X obj 89 11 loadbang; #X obj 89 40 metro 1000; #X obj 167 272 timer; #X floatatom 167 314 5 0 0 0 - - -, f 5; #X obj 27 243 sel 0; #X msg 248 67 0; #X obj 167 293 / 1000; #X connect 0 0 3 0; #X connect 1 0 3 0; #X connect 2 0 3 0; #X connect 3 0 4 0; #X connect 4 0 5 0; #X connect 4 1 6 0; #X connect 5 0 7 0; #X connect 6 0 5 1; #X connect 7 0 12 0; #X connect 8 0 9 0; #X connect 8 0 10 0; #X connect 9 0 1 0; #X connect 9 0 10 1; #X connect 10 0 14 0; #X connect 12 0 13 0; #X connect 13 0 9 0; #X connect 14 0 11 0;
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
