Logic Pro 9 Logic 9 Memory Issue

RTD

New Member
Hello,

I'm having a huge problem. All I can find on the internet about is this problem is even more people who has this problem. No solutions...

My problem:
I bought a new Mac Pro with 14 gb memory along with Pro Tools 9 crossgrade and Logic 9 upgrade.

Pro Tools upgraded easily and works like a charm. I can use all my processors and everything is works better then before.

Now... Logic 9 is a real pain in the ass. Before Logic 9 I worked with Logic Pro 8 on an old Mac Pro with 6 gb memory. It worked really good. But for bigger sessions it became to slow.

With Logic 9 on my now Mac Pro all the sessions keeps on crashing because of low memory. Even the old Logic 8 projects who worked PERFECTLY on the old mac...

What is going on here? Why can't I use my full 14gb of memory on the newest Mac Pro. And why is Logic 9 crashing and telling me that there is low memory with even a few plugins?

Can anyone help me out? This really frustrating for such expensive software. At the moment I can not work with Logic and I really need it for the people I work for.


Greets,
RTD
 

Roy_L

Logician
Logic 9 needs more memory than Logic 8. In my case with 6 gb memory, switching Logic 9 to launch as 64 bit (in the Finder Get Info window) is the workaround.
 
I'd second that emotion: run Logic Pro in 64 bit mode, and be sure to upgrade as many of your plug-ins to 64 bit versions. You will be happy to find that Logic can finally access all your ram. The soso issue is how 32 bit plug-ins require the 32bit bridge app to "see" a 32 bit plug-ins interface, easier for you to do than for me to explain.

Goodluck...
 

Eli

Logician
Hi George (or anyone else...),

Do you know if the 32 AU Bridge takes advantage of the extra ram when running Logic in 64 bit mode, but still using 32 bit plug-ins via the AU bridge?

I had 6 GB of ram in my tower and was running into memory issues running lots of instances of Miroslav Philharmonik. I switched to 64 bit mode and it seemed like it was a bit better, but I still came up against a ceiling. Then I added 4 more GB of ram. Now with 10 GB of ram, it _feels_ like I'm getting more mileage. But I'm not absolutely certain.

Looking at the Activity Monitor seems to be a bit inconsistent. It seems to show varying amounts of real and/or virtual ram usage based on variables that don't seem to be tied to what I have loaded into the Logic project currently open.
 
That IS a great question. I would guess that the 32 bit plug-in would still have a limit due to the nature of the issue: 32 bit HAS a limit. And wether it's in a 64 bit app would not make a difference. the thing I'm wondering is this: what if you have multiple versions of the same 32 bit plug-in. Are they seen as one "pool" of ram for all instances, or as a single amount per single instance, meaning that, if you add 2 instances of a 32 bit plugin in a 64 bit app, do you double the overall amount of ram available.

I know it sounds damn confusing, it is.

As for the activity monitor, one thing to understand is that if you close one Logic song and open another, the ram amounts don't clear out from one song to the other... so the numbers one sees is completely confusing.

More ram is going to help regardless with 64 bit Logic... the system, uses more, Logic needs some, so you end up with more for the samples to go too.

So the Miroslav libraries are IK Multimedia, right?
 

Eli

Logician
Hi George,

Yeah, I was wondering about the same thing. Is the 32 bit AU bridge ram limit global for the project, or per instantiation?

Yes, Miroslav Philharmonik is from IK Multimedia. And AFAIK, there isn't a 64 bit version yet. I sure hope there will be!
 

Markdvc

Administrator
Staff member
My understanding is that the 32 bit Audio Unit Bridge, being a seperate 32 bit Program with its own memory adress room, allows the user to run as many 32 bit Audio Units as the 32 bit memory limit of approx. 4 GB will allow. This is in addition to any 64 bit AUs running natively within logic. They benefit from the practically unlimited memory space 64 bit Apps can adress.

FAQ 9 links to an Apple KB article dealing with this.

HTH, kind regards

Mark
 

Eli

Logician
Thanks Mark. That does explain ir very clearly. The AU Bridge is a 32 bit app with the same 4 GB limit. But of course we all know that the 4GB measurement is a fantasy. It's more like 1.7 - 2 GB in reality.
 

Jay Asher

Logician
Thanks Mark. That does explain ir very clearly. The AU Bridge is a 32 bit app with the same 4 GB limit. But of course we all know that the 4GB measurement is a fantasy. It's more like 1.7 - 2 GB in reality.
Actually I would say 3-3.33 GB.
 
Maybe 64 bit, but not 32 bit. I get "out of memory" errors almost as soon as I hit 2gb, and in Protools 9 1.7 gb is closer to the "crash and burn" area.
 

Jay Asher

Logician
OK, I just loaded my big template in 32 bit with 2.50 GB real memory and 3.82 Virtual Memory

I get the low memory warning initially but then I proceed to work and it is fine.
 

Eli

Logician
FTR, I am also getting out of memory errors, to the point where it interferes with the ability to continue working, at a bit under 2 GB of RAM when running in 32 bit mode

The performance does seem to be a bit more robust - with regards to this ram limitation at least - when running the AU Bridge in 64 bit mode. OTOH, it does seem to crash regularly on me. But to be fair, I am principally using Miroslav Philharmonik in these current situations. So, the behavior I am experiencing may be plug-in specific.
 
Hey Jay,

As you and I both know, there are many things that come into play. I have one client who has a template with about 350 tracks, both midi and audio, 64 live inputs going all the time. If we go over 1.7 to 1.8 GB or real memory (that is the section of memory that is important) we get the warning, or just get freezes, etc.

This client does major films, and cannot have any issues with crashes where they could loose cues, or worse yet, have a cue get corrupted.

Sure, a person can ignore dialogs, or even turn them off to a degree, but at their own peril, and this person (or any of the other people I work with/for) have to have systems that are stable as close to 100% as we can get.

If you are getting different results than I, or you feel comfortable recommending your clients do different that I, that is fine.

I can't afford to be unconcerned about this stuff, and will take the road of caution every time.

I suggest that, in this case, we are both entitled to our own opinions, and that, for our specific reasons, correct. Because really, I'm just as sure I can prove to you that what I suggest is true as well, in my experience..

That said, I'm satisfied with the results with this "conversation"... when a situation is a "no win" like this, any energy spent to convince the other person involved that either is correct is a waste of time.
 

TmHuud

Logician
OTOH, it does seem to crash regularly on me.
Not running Miroslav here and yes it crashes regularly. PITA. I'd suggest trying to dump all 32 bit plugins and use only the 64's.

C'mon developers-get with the program. :errr:
 

shreddersinc

Logician
I'm not sure if this is pertinent but I was reading quit awhile back about people having problems with certain brands of RAM...Not working correctly, with their mac's.
just a shot in the dark :) And it's really dark being no one else brought it up.
 

Jay Asher

Logician
Hey Jay,

As you and I both know, there are many things that come into play. I have one client who has a template with about 350 tracks, both midi and audio, 64 live inputs going all the time. If we go over 1.7 to 1.8 GB or real memory (that is the section of memory that is important) we get the warning, or just get freezes, etc.

This client does major films, and cannot have any issues with crashes where they could loose cues, or worse yet, have a cue get corrupted.

Sure, a person can ignore dialogs, or even turn them off to a degree, but at their own peril, and this person (or any of the other people I work with/for) have to have systems that are stable as close to 100% as we can get.

If you are getting different results than I, or you feel comfortable recommending your clients do different that I, that is fine.

I can't afford to be unconcerned about this stuff, and will take the road of caution every time.

I suggest that, in this case, we are both entitled to our own opinions, and that, for our specific reasons, correct. Because really, I'm just as sure I can prove to you that what I suggest is true as well, in my experience..

That said, I'm satisfied with the results with this "conversation"... when a situation is a "no win" like this, any energy spent to convince the other person involved that either is correct is a waste of time.

It is indeed a "pick your poison" at this time. Fortunately with using VE Pro as a supplementary host, the only 32 but AUs I am running is my UAD stuff and they just don't seem to crash the bridge often.
 

compose777

New Member
crashes with loud noise

I am having a problem with my logic 9 crashing with a very loud blast and then it quits saying I don't have enough memory. I have 15 gigs of RAM.

Anyone know what I should do?

I have Ivory
East West Platinum
Vienna Strings
 
U running in 64 bit mode? Select the Logic Pro app and press command i to get info. there is a checkbox there to turn on and off 64 bit mode. If you are not in 64 bit mode you are not accessing all the ram you have.

Ivory is SUCH a memory hog that I will not run it inside Logic, preferring to use VEPro to host it in 32 bit mode.

Let me know if that works for you.
 
Top