The Not Enough Memory Issue

[2neffoo]

I removed the kontakt.dll from the vsts folder and the song is at least opening now (takes ages to open). There was 3 instances of kontakt, should it be able to run 3 instances?

[2neffoo]

^ i've got other songs with 3 instances.

[[mid]]

Hi,

sure that should work. It always depends on *how much* you load into Kontakt in dependence on how much memory you've installed.

Check the XP taskmanager for your actual RAM usage.

Best,
Michael
Ableton HQ

[2neffoo]

They're not 'huge' kontakt instruments with long sustaining crash cymbals or anything like that. just a whole lot of 1-hits organised into kontakt instruments. a similar thing happened with one of my other songs. I had to export everything and rebuild it.

Its a bad bug if it leads to an export/rebuild, it takes ages to rebuild a song and it never quite sounds the same.

How is it possible for me to send the set to your support address when the .als file is 36mb? By the way, the other problematic song was 49mb before I did the export/rebuild - it jumped up from about 5mb as soon as I started saving it in live 8.

[[mid]]

Hi,

Kontakt reserves also memory. Check this in the settings of Kontakt -> DFD and lower the amount.

It also sounds that your sets contain many small clips. Consolidating them lowers the RAM usage.

If you want to send big sets use yousendit and send us the link.

Cheers,
Michael
Ableton HQ

[forge]

this bug has been reported a while ago: http://forum.ableton.com/viewtopic.php?p=857057#p857057

I think I started noticing it as soon as the looper was added in one of the Alpha versions, it seemed to go away for a while but came back with 8.01

[2neffoo]

i haven't used looper yet.

@Michael, How can you tell I've got many small clips? Is it because of the file size, is it just small audio clips that causes RAM usage or midi as well? Consolidating is cool as a work around for now but in future I think it will be a major work flow problem because I like to drag and drop small clips around freely.

Kontakt DFD setting was 60mb.

[forge]

i haven't used looper yet.

that's interesting because I was sure that was the one thing common to all sets where I experienced this

what other Ableton devices are you using (collision? Corpus?)

[2neffoo]

other than kontakt there was an ableton compressor in each of the problematic sets. but thats it.

[2neffoo]

hmmm.. just discovered I had installed the new .dlls from the latest kontakt update in the wrong folder so I was using kontakt 3.0 - I've re-installed correctly and now the song seems to have come back to life.

we'll see how that goes.

[[mid]]

@forge:

thanks for the info. Is this still valid for 8.0.2?

Best,
Michael
Ableton HQ

[forge]

@forge:

thanks for the info. Is this still valid for 8.0.2?

Best,
Michael
Ableton HQ

Hi Michael

I can't be sure, but will let you know if it happens

cheers

Craig

[[mid]]

Hey Craig,

i' d really appreciate to get any infos about that.

Cheers,
Michael
Ableton HQ

[circuitb]

hi
same Not Enough Memory error here!!! (laptop / xp / 4Go ram)
8.0.2 with 8 looper's
when i check the memory in the task manager..
around 600 Mo allocated to ram
and around 800 Mo allocated to virtual memory
with the /3GB parameter in the boot.ini

[circuitb]

after some testing
the not enough memory message appear when i edit
the midi mappings...
for me this issue is related to the looper (depending on the number of instances... eg > 6 looper's)
and the midi map mode