Logic 9 -- Do you get the Memory-Too-Low-Messages?

[Macaroni]

I haven't gotten the low memory message, but I am getting constant messages re the System was unable to process the audio. I get a bunch of them trying to play through a song I'm working on.

It was created in Logic 8 and after converting to Logic 9 and adding some more audio tracks, it got to the point where I couldn't even start the song without getting the unable to process messages.

So I created a new Logic 9 Project and imported the final tracks into it, and I still get numerous 'unable' messages. Very frustrating.

It's about 40 tracks, with no VIs - just audio and Auxes.

MacPro Quad Intel 2.66, 7 GB RAM, OSX 10.6.1, Logic 9.0.1, UAD-2 Quad (about 75% on this song).

[Ashermusic]

Originally Posted by Macaroni

I haven't gotten the low memory message, but I am getting constant messages re the System was unable to process the audio. I get a bunch of them trying to play through a song I'm working on.

It was created in Logic 8 and after converting to Logic 9 and adding some more audio tracks, it got to the point where I couldn't even start the song without getting the unable to process messages.

So I created a new Logic 9 Project and imported the final tracks into it, and I still get numerous 'unable' messages. Very frustrating.

It's about 40 tracks, with no VIs - just audio and Auxes.

MacPro Quad Intel 2.66, 7 GB RAM, OSX 10.6.1, Logic 9.0.1, UAD-2 Quad (about 75% on this song).

Odd Ron, because I just loaded up 40 audio tracks and am playing back with no problem.

Are yours cut into a lot of small regions?

[author]

Originally Posted by Ashermusic

I have a previous generation MacPro Quad, running 10.6.1 with 13 GB RAM.

You seem to have a few more gigs of RAM than most people.

Mayby these low-memory messages have something to do with, dare I say... low memory?

[Macaroni]

Jay... I've got one drum track comprised of many Apple Loops and a few others with chopped up regions, but the others I bounced in place to consolidate them

When I watch the System Monitor, sometimes the I/O meter spikes and sometimes it's the CPU meters.

[Ashermusic]

Originally Posted by Macaroni

Jay... I've got one drum track comprised of many Apple Loops and a few others with chopped up regions, but the others I bounced in place to consolidate them

When I watch the System Monitor, sometimes the I/O meter spikes and sometimes it's the CPU meters.

I am going to now make a very profound statement

There is something wrong on your rig.

[valis]

Are there background processes potentially causing conflicts with Logic's audio engine? Perhaps keep an eye on the Console and see if there's anything you can identify that's related. Also IIRC you can actually disable audio overload issues in your preferences if you're not doing live recording with effects where you might wind up recording a bad sample or two.

As an anecdote, I had a friend that loved the Fabfilter plugins until he realized that a lot of his Ableton Live issues with his Macbook were related to a combination of the DPC issues with the wireless drivers (which I believe Apple later fixed?) in combination with Volcano & Twin checking home every 20 minutes or so while he was busy with his live set (nasty audio breakup ensued.) Of course someone with more technical understanding would have probably disabled the wireless altogether, but he would have had to give up his iPhone controller fun...

[Macaroni]

There is something wrong on your rig.

Naturally, that's the first thing I thought of, and I've read/seen many of your posts that relate to that.

I haven't changed anything about my rig, since upgrading to Logic 9 and Snow Leopard, and while I did have these issues before, never to this extent.

Thanks!

[shanabit]

Whats up Macaroni????

[Søren Bendixen]

I have the same problem (memory getting low) - it started from logic 9.x
I´ve created a brand new logic 9.02 session and now it comes along when just opening the session
I use Ableton live 8.08 and cubase 5 (and Reason) - no problem - issue only related to logic.
I´ve installed the following plugs around the same time upgrading logic:
VA 1- analog synth
Usb Producerpack (ultimatesound) + UVI workstation
Softtube FET compressor(Demo)
Updated Independence free

Rigth now I´m testing a new session again - loading stuff in - see when i get the message - will get back with results

regards
Søren Bendixen

[Lagerfeldt]

Installing Logic 9.0.2 on a new Mac Pro with 8 Gb of RAM, running Leopard, this week. I am very meticulous when installing and have a good knowledge of OS X so I'm excited to see what happens.

More info in this thread on Logic Pro Help
Logic Pro Help :: View topic - "Memory is getting low / Not enough free memory to cont

I found this post interesting:

was running into the same problem and was told to install Snow Leopard and buy more ram...so I did.

32 GB of ram and a Snow Leopard upgrade later, and I STILL have the same issues. VERY annoying! Is this progress?

Though someone with lots and lots of RAM in this thread didn't experience the problem it seems that excessive amounts of RAM isn't necessarily the solution.

[author]

Originally Posted by Lagerfeldt

Installing Logic 9.0.2 on a new Mac Pro with 8 Gb of RAM, running Leopard, this week. I am very meticulous when installing and have a good knowledge of OS X so I'm excited to see what happens.

Please keep us posted.

I really hope there's a way to fix this, I'd love to upgrade to 9.

[miscend]

Originally Posted by NoVi

I don't know if this is related to OP, but today I discovered a very nasty bug (I guess). Yesterday and today it was really the first time I tried Logic 9 out. Noticed the memory low message and also had a terrible amount of disk too slow messages in Logic.

Yesterday evening I got a system message saying my Macintosh HD was running out of disk space (while there is normally around 40 Gb available). Anyway, moved some large chunks of data to an external drive, but a few hours later the disk space was gone again.....

I dloaded an application (Disk Inventory X) and I could see that there was a problem within the asl files (where Mac OS X stores the system messages). Moved the asl files to another location, restarted the ASL manager through Terminal but noticed that with the fresh asl-file it was spectecular growing again. I watched it in Console (before the reset I couldn't because the file was too large, around 15 Gb) and noticed that Logic was constantly spitting out messages like these :
Sep 27 18:49:49 e-k-mac-pro [0x0-0x63063].com.apple.logic.pro[818]: eventQuantizeFl
Sep 27 18:49:49 e-k-mac-pro [0x0-0x63063].com.apple.logic.pro[818]: oat 28589.951172

Through Google I only could find one similar behavior with Ableton Live:
Ableton Forum • View topic - syslogd spiking, screeds of floating point reports

Anyone has any idea what is going on?

Whats the location of this folder?

[Firechild]

The memory low warning comes when Logic approches the 32 bit limit of 3.2 Gb virtual memory. What is strange with that? Same issue with Logic 8 but with no warning just a crash...There is a difference though that Logic 9 seems to use a bit more memory compared to the same plugin load in a Logic 8 session.
The EastWest Play plugin uses RAM outside Logic but only when Logic starts to come over 2.0 Gb virtual RAM. Kontakt 3.5 uses RAM outside Logic if you activate "Memory server" which I believe is disabled as default. Vienna Ensemble plugin uses RAM completely outside Logic.
I recently updated to 16 Gb in my 8 core and they are all useful when working with Kontakt 3.5, Play inside Logic 9. WHo needs a 64 bit Logic? Just tell the plugin makers to look at Kontakt 3.5 and VSL how to handle RAM.

Memory getting low message comes around 3.0 Gb of Virtual RAM.
I just loaded Black Grand EXS24 and a 800 MB BFD2 kit...


And then the final goodbye box when reaching the 3.2 Gb limit after adding some more plugins. Note that the "KxMemServer0"" is the kontakt 3.5 app which uses RAM outside Logic.

[Søren Bendixen]

I can load and run a session (logic 9.0.2) using 3.70 GB Virtual RAM without getting any warrings - although when I start editing (mainly moving midi around during playback) it sometimes crashes.
I can load another session using 3.61 GB Virtual RAM and if I load it from scratch it says memory is getting low.
If I close the project (using "close project") and open it again i disables plugs ins etc - so something is very strange - It´s like logic doesn´t really close the project when choosing "close project" - or what?

I´ve attached a fig. of systemperformance - and I´ve noticed that some of the things going on is shown in red (usereventagent - not responding, coreaudiod - not responding > something is not right.?

I never experienced this in Logic 8, allthough it sometime crashed, but for sure not as often as Logic 9.

[valis]

Yes it seems that a lot of cached content remains cached until you close the application itself.

[Søren Bendixen]

Originally Posted by valis

Yes it seems that a lot of cached content remains cached until you close the application itself.

strange yes..?

[NoizyNinja]

The really messed up thing is as you record virtual memory gets used and shuts you down as you approach the max. Recording uses virtual memory????

[TEMAS]

I'm running Logic 9 / OS X 10.6.1 / 8 core 2.8ghz / 10gb / 4 x 500gb.

If I open one Vienna Imperial piano (about 1.5gb) and then one Trilian bass (about 2gb) I get warnings from Trilian that I don't have enough RAM and from Logic that my memory is running low. The result is that Trilian won't even play the preset. If I choose a smaller Trilian preset it loads, but thats my limit.

So great, with my £5k MacPro set up I can play one bass and one piano at the same time, well only at 512 buffer size. If I try it at 256 buffer, the CPU reaches max, because Logic can't distribute the load across cores while tracking.

And remember this is with no effects, just two virtual instruments. Apple and Logic is a complete joke. I'm so fed up with software developers selling programs that just don't work in the real world.

[Football]

Originally Posted by TEMAS

I'm running Logic 9 / OS X 10.6.1 / 8 core 2.8ghz / 10gb / 4 x 500gb.

If I open one Vienna Imperial piano (about 1.5gb) and then one Trilian bass (about 2gb) I get warnings from Trilian that I don't have enough RAM and from Logic that my memory is running low. The result is that Trilian won't even play the preset. If I choose a smaller Trilian preset it loads, but thats my limit.

So great, with my £5k MacPro set up I can play one bass and one piano at the same time, well only at 512 buffer size. If I try it at 256 buffer, the CPU reaches max, because Logic can't distribute the load across cores while tracking.

And remember this is with no effects, just two virtual instruments. Apple and Logic is a complete joke. I'm so fed up with software developers selling programs that just don't work in the real world.

I feel your pain. That being said, if you tried that exact same thing on that exact same machine with Pro Tools I think the performance would be at least as poor (probably more so). That type of performance is not exclusively just a Logic issue IMO. Can't speak of any other DAW's other than those two but all might be similar in this regard at this point in time (unless maybe something 64 bit is working well with Trillian and VSL).

Have you thought of running Vienna Ensemble Pro and having those two VI's running outside of Logic?

VIENNA SYMPHONIC LIBRARY > COMPANY > NEWS********* > Vienna Ensemble PRO

[hive]

any updates on this? i'm experiencing the very same issue and it's doing my head in.

[quincyg]

I just skimmed the posts, so sorry if I am repeating.

The memory message is when you are approaching the 32 bit limit as discussed.

Snow Leopard seems to be resolving this issue for people.

[jrubbernek]

go to audio bin, check the unused audio files, and then delete them. have to do it every now and then, cuz if you're recording audio, and you hit ctrl + z, for some reason logic doesn't cancle it, but it saves the audio in the audio bin, and that's why it takes away the memory i guess...well so far if that memory too low appears, I just delete the unused audio files....and it works...

[author]

Originally Posted by jrubbernek

if that memory too low appears, I just delete the unused audio files....and it works...

I don't have to do that in Logic 8. So, I'll update when/if Apple solve the problem.

[ultrasound6]

I myself cannot believe that Apple and Logic could get this so wrong!! Years ago I completed a 13 x 1 hour TV series on an old G4 with 2gb RAM, with Logic 6. I was able to have heaps of 3rd party plugs, in particular the 3 x spectrasonics ones, heaps of audio, video and midi - NO SWEAT !! It seems now that re are regressing with each Logic release. What the ....... :-((

[Ashermusic]

Originally Posted by ultrasound6

I myself cannot believe that Apple and Logic could get this so wrong!! Years ago I completed a 13 x 1 hour TV series on an old G4 with 2gb RAM, with Logic 6. I was able to have heaps of 3rd party plugs, in particular the 3 x spectrasonics ones, heaps of audio, video and midi - NO SWEAT !! It seems now that re are regressing with each Logic release. What the ....... :-((

I guarantee you that if we all could/would go back to using the same software instruments with the same libraries you were using then, it would be the same.

For the 900th time, it is NOT a Logic issue, it is a 32 bit DAW with 32 bit plug-ins on the Mac issue. Now if you want to blame Apple for not getting a 64 bit OS sooner and the software developers for not coming out with 64 bit DAWS and 64 bit plug-ins faster rather than just figuring out how to make it work, then go ahead, have fun.

[zulusound]

Wanted to bump this up, as I am getting these "memory is getting low" messages more now on my new Mac Pro 8 core 10.6.8 with 48 GB of Ram/ Logic 9/ Kontakt 5/ than I was on my old G5 with 6 GB of ram running Logic 8 with a similar plug in count!

I have lowered my Logic undo # to 5

I am wondering how to set up Kontakt 5 especially- in the stand alone prefs, should I Use Memory Server? In the Engine, should it be set up 8 cores for Multiprocessor Support in my case? I read that it should be set to 2 cores even if you have 8 cores.

Any other tricks?

Thanks!

[charlieclouser]

You should definitely use the Kontakt memory server. This will allow Kontakt to use memory outside of what Logic is using - and if you are running Logic in 32-bit mode you will absolutely need to do this.

If you can run Logic in 64-bit mode then Logic can access all of your physical RAM - but using the Kontakt memory server provides other performance enhancements, like keeping common samples in memory when switching songs (which means quicker song loading times), user-controlled purging of memory, etc... so the Kontakt memory server is generally a good thing, even with Logic in 64-bit mode.

If you want to keep Logic in 32-bit mode then the solution is to use Vienna Ensemble Pro to host instruments outside of Logic. This works great, and will allow you to run the VEP in 64-bit mode while Logic is still in 32-bit mode - this lets you avoid using the 32-bit bridge to load old plugins in Logic, and you still get all of the QuickTime functionality (like export audio to movie) which are not available when Logic is running in 64-bit. This solution also allows you to run memory hogs like Omnisphere without any memory hassles at all.

I run gigantic Logic templates in 32-bit mode because I want to use my old PowerCore plugins which are 32-bit only - but I use VEP in 64-bit mode to host the big Kontakt, Vienna, and Omnisphere stuff. I am on a three-year-old 8-core machine with 32gb of RAM.

[valis]

Sadly I think you'll need more ram, in the states OWC has upgrade kits that I've put to good use myself. 4GB is getting tight with Snow Leopard and should you move to Lion it'll be tighter still.

[davey boy]

Originally Posted by zulusound

Wanted to bump this up, as I am getting these "memory is getting low" messages more now on my new Mac Pro 8 core 10.6.8 with 48 GB of Ram/ Logic 9/ Kontakt 5/ than I was on my old G5 with 6 GB of ram running Logic 8 with a similar plug in count!

I have lowered my Logic undo # to 5

I am wondering how to set up Kontakt 5 especially- in the stand alone prefs, should I Use Memory Server? In the Engine, should it be set up 8 cores for Multiprocessor Support in my case? I read that it should be set to 2 cores even if you have 8 cores.

Any other tricks?

Thanks!

You said 48 gbs ram and not 4, correct? Are you running Logic in 64 bit mode? You shouldn't be getting any error messages. I only have 10gbs and never have memory problems running Kontakt, Spectrasonics, Toontrack, etc.

[valis]

Hah I read that as 4GB, thanks for pointing that out.