Approriate Automation Update Limit
Sep 29 2019 | 11:40 am
So I'm trying to bug test and bug fix some M4L Devices (some my own, some stock from Ableton) as I keep having crashes when automating M4L Parameters, so my question is:
Is there an appropriate way to set up a live parameter in M4L for accurate automation, that doesnt overload the object with unnecesary data.
Should the update limit (ms) be greater than 1ms?
Should automation output be defered?
Any insight would be helpful!
james.
- Oct 02 2019 | 12:01 amI’d be curious about best practices info on this as well. I‘ve pretty much always just left it at 1ms and don’t recall ever having used the deferred option. (I don’t often stream continuous values to individual controls though unless via live.remote~).
- Oct 02 2019 | 1:43 pmare you talking about the GUI or the actual parameter? for GUI stuff a "frame rate" of 20-25 milliseconds is all you need. (thresh & some magic to repeat the last value when there is a break) and deferring should not be required in max4live.
