"Update Limit (ms)" in live.dial, etc, inspector... ?

[LOFA]

Since there is no reference information (clue window or within the objects reference manual) could someone please confirm / describe this functionality?

Is this a delay or something for similar to a speedlim?

Thank you

[LOFA]

Tested it out with staccato envelope data consisting of values 0 and 127 at 20bpm with this:

<pre><code>
----------begin_max5_patcher----------
725.3oc4XssiaBCD8YxWAxOmFg4RCpu09aTsJxfcR7VvFAlzrc09uWaCNAZg
DmjVx1zHECLiwyYNdlir30YNfD9dREv8Ste00w40YNNZSJCNsO6.xQ6SyPU5
oARpEBNCLuwEuVjQDhWJHMqAHAw1.bep0cARjtkx1rpjjJZlQf+xEdyciCUi
9dlwCuBEqCCO44O36YBCqNmxjARCA3QiMguwpx3ayloFlaYtHWgDRoIHq4LQ
E8G5LAp.1HoHkI.ysOS+XjZLRmov3QxTXWPvP45XA9bIEk49EdF9BHB+2qDA
Lv2BlH3NyDjuKggIHBxdcN.R40LAoTRGxeWIOY9qdzF5BFntrL9jz0xqgthF
jtBuB55VUC7CCsUM.F+WVM3lyEOOqykn+oU1ZyTaT1fAOxJasDgUJaP3+8Ja
F5xFks36qvVFcGYAVFLSb1gJOfB48TTRFYTsBEYrNiirSnWO1HDFtbX13z5E
EnRIzj6hqHLMtFuvo0ZEZGAuBIDkTorG43cUsbRKonx6rZBeswrwd2fxKwxV
L4DZqS54DSVOtypBBAmQy06cdGJz5MGJaGsh1lUCtHBRQ0XNQLFWfDTNa0Xa
e8Iv8EbFgo2gfChmZFUTIdYb7jKKjzutd6cH+Tl9cGzqoJZXpfJjkjc1kGjO
1xKEVkr4b7YvZFmsw5k5ToUFk8M0B0st82V.NVGnvAS80bMH.iskz3swotY2
b4OYmepTLpjmciM9FcPKZ7Cd7a7gSTae+8tG6t9SjqWXS+YVIq648tG875NJ
YGM6W+FG5lRk89BAU75xTSub6oPbO1WhIUBJSWV0YNpC10YRaoXLg0IkA4Tb
AWd1nVL39zfpR1BI0IpOOlhlVLEYAlhmTHYEKELsrTrkrTvjAI0mX6rPR8QF
lPZxGZCl7lVLszFLMskS1zy4Ce+Ugq4xKnD2OJXQj7zRd5iKED6sXo4wdvU9
vay9ITSG7kH
-----------end_max5_patcher-----------
</code></pre>

Seems that it simply looks for a given value at a specific interval, as changing either the bpm or "Update Limit (ms)" creates different displayed values between the dial clips, when sharing the same envelope data.

[pid]

this was added in max 5.1.5 if memory serves me correct. it is based on speedlim and defer, as mentioned in these forums somewhere by the developers at the time. it is for automation purposes in case many fast changes are targeted at a control parameter etc. and so on. works pretty great in my experience. sorry i did not look at your patch. i agree these things should really be better documented (i.e., documented).

[LOFA]

this was added in max 5.1.5 if memory serves me correct. it is based on speedlim and defer, as mentioned in these forums somewhere by the developers at the time. it is for automation purposes in case many fast changes are targeted at a control parameter etc. and so on. works pretty great in my experience. sorry i did not look at your patch. i agree these things should really be better documented (i.e., documented).

Thanks for the data and for confirming my experience. Yes, this is really helpful. Just deleted about 50 speedlims from a project and I appreciate knowing that this was added later, and that it was not an oversight.

[eshaa83]

I am happy that you have get your answer...
I like this forums so much where people really helped...