what about setting metro default argument to same as delay?
just for awkward windows users like me
$ diff -uw x_time.c.old x_time.c --- x_time.c.old 2010-04-28 11:16:06 +0000 +++ x_time.c 2010-04-28 11:16:30 +0000 @@ -107,7 +107,7 @@
static void metro_ft1(t_metro *x, t_floatarg g) {
- if (g < 1) g = 1;
- if (g < 1) g = 20;
x->x_deltime = g; }
On 2010-04-28 13:19, colet.patrice@free.fr wrote:
what about setting metro default argument to same as delay?
just for awkward windows users like me
$ diff -uw x_time.c.old x_time.c --- x_time.c.old 2010-04-28 11:16:06 +0000 +++ x_time.c 2010-04-28 11:16:30 +0000 @@ -107,7 +107,7 @@
static void metro_ft1(t_metro *x, t_floatarg g) {
- if (g < 1) g = 1;
- if (g < 1) g = 20;
x->x_deltime = g; }
but this does not only effect the default the arg, but also any time set through the right inlet. so if you decrease the metro time with a ramp from 100ms to 0.1ms, it will suddenly jump (..., 1.02, 1.01, 1.00, 20.00, 20.00, ...) which i think worse than saturating at "1".
i'm not opposed to raising the "default", but it should only affect the arguments.
fgmasdr IOhannes
On Wed, 28 Apr 2010, IOhannes m zmoelnig wrote:
but this does not only effect the default the arg, but also any time set through the right inlet. so if you decrease the metro time with a ramp from 100ms to 0.1ms, it will suddenly jump (..., 1.02, 1.01, 1.00, 20.00, 20.00, ...) which i think worse than saturating at "1".
When the goal is to ramp down to 0.1ms, saturating to 1ms is just as unusable as jumping back to 20ms. In that case, a Pd user would just avoid [metro] anyway.
This to say, that I don't care whether the change is applied or not. It could as well turn itself OFF as soon as you go below 1ms, I wouldn't care.
i'm not opposed to raising the "default", but it should only affect the arguments.
If I say [metro 0.5], I'm not using a default value. Furthermore, if I send 0.5 to [metro], right inlet, I'm not using a default value.
[metro] doesn't respect the principles that you want Patrice to respect.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
On 2010-04-28 22:14, Mathieu Bouchard wrote:
i'm not opposed to raising the "default", but it should only affect the arguments.
If I say [metro 0.5], I'm not using a default value. Furthermore, if I send 0.5 to [metro], right inlet, I'm not using a default value.
[metro] doesn't respect the principles that you want Patrice to respect.
i don't understand what you want to tell me. your examples with 0.5 are both true, but i can't see how they are related to what i understand to be patrice's proposal.
that metro cannot go down below 1 is - imho - a separate issue than the default time for a [metro] without arguments.
we have briefly touched the issue of "default argument" vs "explicit arguments" (even if they backup the default) on IRC the other day. in the case of metro i think: [metro] (without args) should default to a "safe" value. "1" is not very safe (it triggers messages quite often), so i'd say "something higher" (20, 100, 1000?) or (as you seem to suggest) nothing at all.
as for the range of valid values for metro (not the default argument), i'd vote for going right down to "0". i would then make a difference between [metro] and [metro 0]
fgmasdr IOhannes
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
----- "IOhannes m zmoelnig" zmoelnig@iem.at a écrit :
"safe" value. "1" is not very safe (it triggers messages quite often), so i'd say "something higher" (20, 100, 1000?) or (as you seem to suggest) nothing at all.
after reflexion, 1000 or even 500 (120 BPM) sounds like good default value for that kind of object.
On 2010-04-29 10:01, colet.patrice@free.fr wrote:
----- "IOhannes m zmoelnig" zmoelnig@iem.at a écrit :
"safe" value. "1" is not very safe (it triggers messages quite often), so i'd say "something higher" (20, 100, 1000?) or (as you seem to suggest) nothing at all.
after reflexion, 1000 or even 500 (120 BPM) sounds like good default value for that kind of object.
actually, i don't think the default value should be readily appliable. else all music made with Pd will end up being 120bpm techno, which would be a sad moment...
fg asdmr IOhannes
-
colet.patrice＠free.fr -
IOhannes m zmoelnig -
Mathieu Bouchard