Logic "out of memory" error when running VE pro?

[JT3_Jon]

Hello everyone,

I'm still running 32-bit logic due to plugins not being 64bit yet and crashing the bridge, and unfortunately I've run out of RAM in my current project. Whats weird is even though I have Kontakt memory server running, if I try to load another instrument into my project I get the dreaded "running low on RAM" error. 

Thinking this was a problem with my current song, so I loaded a new logic song and tried to see how much I could load into Kontakt hosted in VE pro, and was SHOCKED at my results!! I could only load 3.22GB!!!

Here is a link to a picture of my activity monitor. As you can see, Logic is only show 285MB Ram used, VE pro is showing only 1.6GB ram, yet I got an "out of memory" error! http://www.fieldsfaraway.com/jon/logicvepromemory.jpg

Anyone have any ideas? Please, correct me if I'm wrong, but I thought that VE pro & Kontakt 3.5's memory servers both loaded its samples outside logic? So why if I load ONLY kontakts in VE pro, does logic's give me an "out of memory," error, especially when its only showing only 285MB of ram used?! Is there a setting I'm missing in VE pro or Kontakt? 

Anyone else willing to run tests with pictures?

 

Thanks in advance for the help and reply!

8-core 2.93GHZ Mac Pro (2009) OS 10.6.5, 24GB Ram Logic 9.1.3 VE pro V4.1.7644

[civilization 3]

regardless, a 32-bit app [in a 32-bit OS] has a [theoretical] limit of a 4GB memory address available. From where I stand you're doing great getting 3.22 up at one time (ie., one instance). I often ran into problems around 2GB. Kontakt 4.2 is 64-bit. you could run Logic 32-bit in the x64 kernel and use K4.2 in VE Pro x64 server and get well I think.

I've run into K3.5 out of memory, and BFD2 out of memory in cases [where it shouldn't be true] where restarting cleared that up.

The new memory server when KMS has reached limit is just another 32 bit instance which can access its theoretical limit of 4gb. When that is filled, another is opened etc. To get the extra address KMS provides, I believe you need to boot in x64 kernel.

[mosso]

It sounds like you're loading Kontakt in the 32 Bit VE Pro Server. Try loading it in the 64 bit VE Pro server (I think K3.5 had a 64 bit version). Provided that you're only running Kontakt in VE Pro then you can turn off the Kontakt Memory Server too.

No idea why Logic is giving you the error though...

M

[freeclyde]

Hi, 

I was just getting these errors -- they are different from regular Logic memory errors.  I don't think it has anything to do with sample memory.  

I don't fully understand the "DeCouple" feature but try it.  This fixed the problem for me.

[swpowe]

I'm getting this error now too. I don't understand why. I seem to be having more problems using a slave PC then when I was running everything on a single Mac Pro. I've got a project with only two connected instances of VE Pro (connected to my PC) and when I try to save the project I get an "out of memory" error. I only have maybe 5 midi tracks and those two instances. Shouldn't I be getting better performance? What is this memory error for?

[civilization 3]

if the error is in Logic (or other host) I would say to heed the 'decouple' advice; when coupled with VE Pro, the host is storing data about VE Pro, when decoupled it isn't.

[swpowe]

If I change it to decoupled, doesn't that mean that I lose the ability to have settings saved with my logic project? If it's decoupled then I'd need to save my logic project and also save inside ve pro. Is that right? I also don't understand why I'm having this problem with a Slave PC that should be more powerful then my older mac pro. I could run the same template on my Mac Pro while also running Logic and now my Mac Pro is running logic ( a very basic session ) and I've offloaded the template to a PC slave with 24GB of RAM and a i7 3.2 CPU. Could it have something to do with the network settings between the two?

[swpowe]

Anyone have ideas about this out of memory error?