Hi all,
i'm a bit surprised that i haven't found anything in the archives, so
what is the reason that the period of metro can't be lower than 1 ms?
(it's limited in the source code).
If it's a security thing, so that it prevents cpu overload it should
at least be much lower (or even better, just > 0).
gr~~~
On Sat, 2008-05-17 at 17:49 +0200, Thomas Grill wrote:
Hi all, i'm a bit surprised that i haven't found anything in the archives, so
what is the reason that the period of metro can't be lower than 1 ms?
(it's limited in the source code). If it's a security thing, so that it prevents cpu overload it should
at least be much lower (or even better, just > 0). gr~~~
i am pretty sure, it has been discussed already. though, i am not sure, if ever anyone came up with a good reason for that behavour. to me as well, it seems to be a pretty arbitrary choice. ([until] shouldn't exist, if cpu usage, respectively turning pd unusable, is considered an issue).
after all, you could make your own [micrometro] abstraction based on [del], which hasn't such a built-in limit.
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Hi, Thomas,
I'm looking at the code right now, and I can't see what you're referring to. Is it the x_clock which is limited?
Chuck
On Sat, May 17, 2008 at 10:49 AM, Thomas Grill gr@grrrr.org wrote:
Hi all, i'm a bit surprised that i haven't found anything in the archives, so what is the reason that the period of metro can't be lower than 1 ms? (it's limited in the source code). If it's a security thing, so that it prevents cpu overload it should at least be much lower (or even better, just > 0). gr~~~
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
ok, nevermind I see it now
from x_time.c:
108 static void metro_ft1(t_metro *x, t_floatarg g) 109 { 110 if (g < 1) g = 1; 111 x->x_deltime = g; 112 }
On Sat, May 17, 2008 at 11:41 AM, Charles Henry czhenry@gmail.com wrote:
Hi, Thomas,
I'm looking at the code right now, and I can't see what you're referring to. Is it the x_clock which is limited?
Chuck
On Sat, May 17, 2008 at 10:49 AM, Thomas Grill gr@grrrr.org wrote:
Hi all, i'm a bit surprised that i haven't found anything in the archives, so what is the reason that the period of metro can't be lower than 1 ms? (it's limited in the source code). If it's a security thing, so that it prevents cpu overload it should at least be much lower (or even better, just > 0). gr~~~
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Thomas Grill wrote:
Hi all, i'm a bit surprised that i haven't found anything in the archives, so what is the reason that the period of metro can't be lower than 1 ms? (it's limited in the source code). If it's a security thing, so that it prevents cpu overload it should at least be much lower (or even better, just > 0).
i totally agree.
in the meantime you can use [delay] to build your own metro. frank has posted a patch once.
here is another one.
fmgasdr IOhannes
#N canvas 0 0 450 547 10; #X obj 98 135 t b; #X obj 146 135 t b; #X obj 196 137 != 0; #X msg 98 159 1; #X msg 146 158 0; #X obj 98 186 t f; #X obj 130 408 delay $1; #X obj 98 387 t b b; #X obj 98 207 select 1 0; #X obj 98 227 t a b; #X obj 156 264 t f f; #X obj 98 361 spigot; #X obj 156 285 > 0; #X obj 156 242 f $1; #X obj 156 306 t f f; #X obj 188 328 select 0; #X obj 188 348 t b b; #X obj 220 421 print dmetro; #X msg 150 388 stop; #X obj 316 87 inlet rate; #X obj 98 87 inlet control; #X obj 98 437 outlet bang; #X obj 98 112 route bang stop float; #X msg 220 400 refusing rate <= 0: stopping; #X connect 0 0 3 0; #X connect 1 0 4 0; #X connect 2 0 5 0; #X connect 3 0 5 0; #X connect 4 0 5 0; #X connect 5 0 8 0; #X connect 6 0 7 0; #X connect 7 0 21 0; #X connect 7 1 6 0; #X connect 8 0 9 0; #X connect 8 1 18 0; #X connect 9 0 11 0; #X connect 9 1 13 0; #X connect 10 0 12 0; #X connect 10 1 6 1; #X connect 11 0 7 0; #X connect 12 0 14 0; #X connect 13 0 10 0; #X connect 14 0 11 1; #X connect 14 1 15 0; #X connect 15 0 16 0; #X connect 16 0 18 0; #X connect 16 1 23 0; #X connect 18 0 6 0; #X connect 19 0 13 0; #X connect 20 0 22 0; #X connect 22 0 0 0; #X connect 22 1 1 0; #X connect 22 2 2 0; #X connect 23 0 17 0;