Not spamming Live's undo history vs. automation and preset storage abilities
Kind of more of an ethical/philosophical topic, but was curious how some of you feel about these things.
Understanding live.remote~ is great for controlling Live API/LOM elements, there is still a lot of leeway for spamming the undo history.
According to Ableton's own guidelines we are to give everything the ability to be automated and stored and at the same time not populate the undo history.
It seems almost impossible especially when doing really off the wall things. Aside from some ugly PITA workarounds, how do you manage this?
Is it on a device to device basis?
If it's meant for live performance, is undo history not a concern?
If it's meant for the ability to create cool sounds/midi patterns etc. etc. that can then be bounced/used in live directly is having all parameters hidden the best option?
If you download a device that has some really cool functionality but you can't automate anything do you throw it away? On the opposite end, if it clogs undo history do you throw it away?
Is there a happy medium anywhere?
Just curious.
Just wanted to mention that you can create M4L Device Presets (top right button), avoiding possible undo history problems of the Max preset/pattrstorage system.
There is still the issue of automation though.
I'm not as worried about this after looking at other devices. Even premium devices from the Ableton shop.
Hello, I am interested in this topic too.
As soon there are automations (both clip and arrangement automations) with my M4L devices (which do not use any live.object), it becomes impossible to use the regular Ableton's undo/redo functions as they're filled with "Undo Change in "mydevice"".
This makes it really hard to work because it is impossible to undo the simple changes in a midi clip or moving clips around.
I am wondering if there is a workaround or how do people deal with that issue.
any leads would be greatly appreciated!
Florent