Major memory problems with Logic 9 (and exs too) Please conf

[TTOZ]

Logic 9 over here (6gb ram, only logic running on Leopard 10.5 after fresh reboot. I get the low memory message at about 1.9 - 2gb, and dies at 2.4.. I can't load logic any higher than 2.4. That is no where NEAR 4gb.... It should be 3.3 to 3.8 in reality.... (a 32 bit process should be able to use 4gb per instance theoretically)

 

Live7 on the same machine gets just under 3GB, 2.9 - 2.97 gb before it fries, Studio One about 2.8

 

But the worst thing is, the EXS is NOT using memory outside logic space, either that or it is a bug in the current 9.01... I loaded 3 sampletekk pianos in 3 separate exs instances. Logic uses 955 MB, i check the exs virtual settings and it says "ON - optimized for more exs instances"

 

I change it to "ON - use only the application's internal memory" and it makes no difference! it just stays at 955. in reality it should have gone up when i did that. Anyway I switched back to the "correct setting" where it is enabled....

 

I can prove this is broken... I loaded logic to about 2 GB with other plugins, and i had about 3 GB system ram free. I added just one exs instance and i couldn't load the one piano... because it is still loading it into logic's memory.

 

on the other hand, i can load kontakt 3.5, and load the very same piano, and you see kontakt's memory server using 300 MB roughly and logic's only goes up by a few. so kontakt's memory server IS working, and the exs one is NOT.

 

Logic has got major ram problems.. firstly, i can't drive it as high as i can other 32 bit apps, secondly, the exs memory server is broken, thirdly, there is no option to release ram when freezing which is stupid cause the instrument is totally inaccessible whilst frozen anyway.

 

Man i mean with just a few instruments and no effects i can easily run out of memory.. i'd be fine if 1) the exs worked as it should and 2) i could load 3.5gb per logic instance which is what i should be able to do.

 

I can only imagine a busy project with plugins on top of the instruments.. and remember MAC versions of plugins are always double the size of windows ones, so effectively, we are really getting screwed for memory here.

 

I need someone else to confirm the exs server is not working.

[Ashermusic]

I don't think Activity Monitor reflects what happen with the EXs24s when they are addressing lots of memory. Also, it does not direct the outside memory from the get-go, but after about 2 GB. Just keep loading EXS24s and see how far you can go.

[Ashermusic]

Man, what I do for you guys for re(sigh.)

I am loading up a template with 25 BIG EXS24 instruments and I as add them the amount of Virtual Memory goes up only slightly but the computer's Used memory keeps showing more and more RAM loaded.

I quit Logic and restart the computer. Bear in mind that these are huge Kirk Hunter Ruby keyswitched instruments. If I were to load my old Vienna Instruments and Project Sam EXS24 instruments, I would get probably 3 times as many loaded as they are much smaller.

 

According to Activity Monitor, before I boot Logic Activity Monitor shows my memory use as 1.23 GB. After I re-load this project, I am up to 9.51 of my 13GB used. And yet Activity Monitor shows only3.53 GB of VM used, app. the same as when I only had 10instruments loaded.

 

I now add 3 more, bridging the total to 28. I am using 10.16 GB of my computer's 13 GB of memory. And yet Logic Pro 9 itself is only using 3.55 GB of VM ,according to Activity monitor.

 

 

The bottom line is:

1. You must have a t least 5 GB RAM in your computer for this to work.

 

2. The EXS24 doesn't begin to load stuff into memory outside Logic until after about 2.5 GB.

 

3. The Virtual Memory panel of Logic Pro 9 in Activity Monitor does not reflect added EXS24 instruments. A.M's total memory usage tells the real story.

 

I will have to do a tutorial on optimizing for RAM usage in my new book, "Going Pro With Logic Pro 9", I think.

[63strat]

2. The EXS24 doesn't begin to load stuff into memory outside Logic until after about 2.5 GB.

 

First off, I appreciate the time you've put in on these tests. Question: I assumed that EXS24's virtual memory pref "On, optimized for more EXS24 instances," was directing the sampler to start using external memory earlier (before all available app RAM was depleted). I wonder what's really happening here with this pref.

[Ashermusic]

2. The EXS24 doesn't begin to load stuff into memory outside Logic until after about 2.5 GB.

 

First off, I appreciate the time you've put in on these tests. Question: I assumed that EXS24's virtual memory pref "On, optimized for more EXS24 instances," was directing the sampler to start using external memory earlier (before all available app RAM was depleted). I wonder what's really happening here with this pref.

 

You're welcome.

 

I dunno. I only know that when mixing loading the EXS24 with 3rd party stuff, it seems to load more with it set to prioritize the AUs.

[TTOZ]

I appreciate all the help, but unfortunately for me it's not working.

 

i just get the message that there was not enough memory to load the instrument in exs, even though i have 3gb system ram free outside of logic, and logic itself is about at the 2.3gb mark...

 

kind of pointless to start using outside memory at that point anyway, it should be a combination to begin with. NI nailed it with kontakt, perfectly.

[mconnelly]

I have to agree that the way Kontakt does it is very impressive - I wish EXS and PLAY would do the same thing and load ALL samples to external memory, from the very beginning (or at least provide a preference for it). Even if Logic is still running with a bigger memory footprint, it gets far less stable the more memory it uses.