SendsXnodes memory

    tds2
    Jun 08 2013 | 1:51 am
    Hi,
    Can anyone help with the following? In Max for Live I'm using the Max API Ctrl1 LFO device to automate a SendsXnodes device for a circular panning Quad setup.
    The trouble is that it appears to accumulate data or leak and it slowly just builds up RAM until Ableton crashes. I've tried Max 5/6 and Ableton 8/9 and it appears to be something to do with how SendsXnodes retains data.
    Does anybody know how I might be able to modify the SendsXNodes patch so that no data is built up/leaked?
    Thanks.
    • Stephane Morisse
      Jun 08 2013 | 7:45 am
      What is your OS ? Can you verify this in the activity manager ?
    • tds2
      Jun 08 2013 | 9:31 am
      I've tried it on OSX 10.6/7/8 all with the same result.
      Ableton "Real Mem" count just gradually climbs in the Activity Monitor.
      Any ideas?
    • Stephane Morisse
      Jun 08 2013 | 10:44 am
      There was an issue with live.object or live.remote~ quickly filling up the undo history, don't know if this is related ?
    • tds2
      Jun 08 2013 | 4:25 pm
      Yes Stephane, I think that's it!
      There's a related post here: https://cycling74.com/forums/parameter-modulation-without-adding-to-undo-history/
      Does anyone know how I would modify the SendXnodes device with this information so it doesn't create undo history?
      Thanks.