Device makes Live Undo dirty
I have this most simple device (1 live.path and 1 live.observer objects), and when I load it, it marks Live's undo history with a "Undo change" message.
I have absolutely no idea what's going on.
Could someone confirm this, maybe explain it, and even better, help me fix it ?
(I am using Live10)
Thanks !
I'm having the same issue with Ableton Live's undo history that is full of "Undo Change " to my M4L devices' parameters, when they're actually not being changed at all.
Not sure why this is happening. If someone has an idea...
try to set parameter mode enabled to 0
Thanks for your feedback
@hollyhook : there's no parameter at all in my patch, just a live.path and a live.observer
In another forum, someone mentioned to me that when unchecking the "Use Persistent Mappings" box in the live.observer, the problem disappears.
But on a larger patch, even with all the live.object and live.observer's persistent mappings disabled, I still get those "Undo Change" in Live's Undo history.
Let's continue investigating !
@PAG
I've tested your example and can confirm the dirty flag after saving and reloading the Live set. But when replacing [loadbang] with [live.thisdevice] the flag disappears. So it seems a matter of initialisation order.
Notice that [live.path] is an active object initialising itself.
So you could also just send [live.path live_set view] to the observer.
I'm having issues with Undo cloccing up Ableton Live. Are there any rules of thumb to stop this happening?
I’m having the same problem. Not sure if disabling ”Use persistent mapping” is the way to go. Any other solutions, or explanations to why an ID change adds “change“ to Abletons undo history?
EDIT: Looking at the "native" LFO M4L device from Ableton, I see that ”Use persistent mapping” is disabled.