Forums > Max For Live

SendsXnodes memory

June 7, 2013 | 6:51 pm

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.


June 8, 2013 | 12:45 am

What is your OS ? Can you verify this in the activity manager ?


June 8, 2013 | 2: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?


June 8, 2013 | 3: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 ?


June 8, 2013 | 9:25 am

Yes Stephane, I think that’s it!

There’s a related post here:

http://cycling74.com/forums/topic/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.


Viewing 5 posts - 1 through 5 (of 5 total)