live.object produces "changes" in Ableton Live Undo History
Hello all,
I am building a Max4Live devices that querries regularly clips' start_time and name with the "get" method via live.object.
I've realized that setting the ID in the live.object introduces a "change" in Ableton Live's Undo History. This scalates quite quickly and if using many devices, the undo history is unusuable.
Is there a reason for this? It is the first time I've seen this, though I've used live.object already a few times before.
So in the patch excerpt, I am first getting all arrangament clips, and then iterating through them to get start_time and name. The first live.object is ok and is not causing any changes. The second one, as soon as I set the ID, will produce a change. It happens the same with live.observer (and I can't call the start_time method like this).
I'm really lost here and the issue is quite heavy, since it really renders the undo history unusable.
Any help will be deeply appreciated!
You can try to turn off the "Use persistent Mapping" box in the inspector window. That's mostly the issue with these kind of problems.
This really did the trick! Thank you very much, Stevon.
I'm not sure I've fully understood it's impact on performance, but so far everything seems to work just fine.
Thank you again!