Make a device invisible to Live's undo history.

    Dec 10 2012 | 12:11 am
    Hi. Is there a way to make a device completely "invisible" to Live's undo history? I'm having a problem with a device which I use to control the selected track (solo, mute and arm, mainly) with shortcuts. It just sits on my master track and is key-mapped. It works great, but it had a lot of unwanted data in my undo history. Why? (I think) Mainly, because I've patch "kill" functions. If I have muted let's say 3 tracks, I can just hit "M" and the patch unmute all the tracks. Actually it does it by scanning through each track of the set, and "set mute 0" for all of them sequentially. It might be a little bit brutal technique, but... BTW I can't use live.remote. If I could just made this device out of the undo eyes. Due to its function, I don't need its states/actions to be remembered at all !! But I need its few live.toggles to be "automated and store" to key-map them. Thanks for your help.

    • Dec 16 2012 | 4:07 pm
      Nobody knows?
    • Jul 04 2013 | 8:33 pm
      I'm interested in solving this too. I'm working on a device that triggers clips for recording. I mainly use javascript to fire clips on armed tracks but after that, if I undo in Live the clip creation happens again because it's in the undo history...It feels really weird that a simple undo action can trigger a clip for recording. I also have the same issue because I want the buttons in that patch to be automated and stored (so I can trigger them by mapping to keyboard or midi).
    • Jul 04 2013 | 9:04 pm
      Replace live.remote~ with a live.object.
    • Jul 07 2013 | 4:11 pm
      Hi Stephane, I'm not using the live.remote anywhere. I'm Just coding in javascript using the LiveAPI. It seems that live.remote can be used to change parameters without affecting the undo history but can it be used from javascript? And can it be used to trigger clips?
    • Jul 11 2013 | 8:27 am
      not sure if this is possible, i think if you use live.object, it gets stored in undo without being able to get around this (this is my experience anyway).
      it's not possible to launch clips from a remote~, the remote~ can only attach to a parameter.