Render To Disk Memory Problem

[DCools]

Hello,

I think I have found another Bug. I only use Live for remixing. After I'm "done" in Live I export each track to a 24 bits wav file which I import in Logic platinum 5.51. I also use ReWire but not this time.

I have nothing in session, everything is in arranger. I have three tracks. Each track activator is off except the track I'm rendering. Each time I render a track my memory usage goes up. I don’t render in arranger but in session so I can select the length.

Example:

I start Live and the memory in use is: 124 MB
After Render track 1, memory in use is: 227 MB
After Render track 2, memory in use is: 299 MB
After render track 3, memory in use is: 371 MB

I only get my memory back when I close Live

I thought maybe it's a plug-in but I closed live, restarted my workstation and started live again. Then I put a five minute song on track one, one on track two and one on track three, different wav file on each track. Then I rendered each track (Length Bars Beats 16th 166 0 0) to a wav file and the same thing happened!!!

Ableton Live 2.03
Microsoft Windows XP Pro SP1 US
Echo Layla24 Drivers version 6.07

Regards,
Diederick F.M. Cools

[DCools]

Who knows what's goin' on? Am I the only one with this problem. It's still there with version 2.1.1.

[dirtystudios]

nope, same thing here in os9. i think live keeps the recorded sample in ram for some reason. that's the bane of my live existence. it kinda fucked me on a last minute project this afternoon. i couldn't render a 30 minute file to disk 'cause i didn't have enough memory, so now i gotta install a 512 so i can get these people their music, which'll be late now. it supersucks.

k

[dpel]

yeah,
and then after all of that,
you'll have clicks in your render. so be warned!

[Alex]

Hi,

the memory leak problem when using "Render To Disk" is solved within the latest Live version 2.1.2.

regards,
Alex