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