TONS of errors: crashing when saving 9092, 9094, 9129 - critically low on memory, etc

[lemieux]

Hello there. I am having a huge amount of errors of many different types on a brand new and powerful mac pro system so I'd welcome any assistance. Thanks!

Mac Pro 2 x3.06 GHz 6-Core Intel Xeon
OSX 10.7.4
48 GB 1066 MHz DDR3 Ram
Avid HD Native Card (errors happen in every slot I've put it in)
HD Omni Interface (latest firmware installed today)
Pro Tools HD 10.2
4 Internal drives:
Dedicated Boot Drive 2Tb SATA Disk
Dedicated Sample Library Drive 1 Tb SATA Disk
Dedicated Audio Recording Drive 2Tb SATA Disk
Backup Drive 2Tb SATA Disk
M-Audio Axiom 49 via USB


I am having a wealth of errors on this brand new system. The computer is blazing fast and brand new and I just did a fresh install of Pro Tools HD native 10. I literally can not figure out what is happening. I've repaired permissions. I've trashed preferences. I've changed hardware buffer, plug-in streaming, ram cache, and every other setting to every different way imaginable and NOTHING helps. I've removed plugins. I've run digi-test and everything is fine. I just tested the computer's ram and all tests passed. I've changed cables. I've moved the native card to ever slot. Nothing I have done has helped. CPU is never going past 25%. most of the time looking at the activity monitor and pro tool's system window the meters are barely moving... still everything crashes CONSTANTLY forcing 30 restarts of the whole system in an 8 hour day and countless playback stops (no matter how high i have the h/w buffer)

As for the majority of the errors, here is what I am getting at the moment. They all seem to happen when I have virtual instruments running (in particular omnisphere and/or kontakt):

I get nonstop errors of the following (all of which stop playback and record)
9092 Error
9094 Error
9129 Error

I also get both of these errors constantly:

"pro tools critically low on memory" error

"panic. could not allocate enough memory"

AND
Sessions freeze when pressing "save" if the session is playing.

there's certainly enough processing power and ram in this system to not crash when i have a few VI's up and running...
any help would be greatly appreciated. and the sooner the better! :)
THANK YOU!!!

[amolin]

Kontakt sucks when used as a VI. It sucks even more when using some of the pianos in the package.

If I have a midi track and want to use one of the grand pianos in kontakt, I can ONLY get it to work if I go into playback settings, in pro tools, and set it to only use a single cpu. I have been using kontakt for years, but I honestly think that the problems with it is getting bigger and bigger.
But try to set pro tools to only use a single cpu, then kontakt works.

Your memory problems might be that some VI's is using the same memory space as pro tools, do you use kontakt's own memory manager?

[RyanC]

Sounds like you are maxing out PT's 32bit memory limit. Make sure to turn on Kontakt and Omnisphere memory servers and that should help. Even at that PT still sucks with VI's. From there the best bet is VE pro, or some people host VI's in Reaper via rewire.

[nst7]

Also make sure you have set Protools to use less than the maximum processors available. It should show 24 available, try setting it to various other combinations, such as 21, 15, 11, 5, etc.

[Marsdy]

Originally Posted by RyanC

Sounds like you are maxing out PT's 32bit memory limit. Make sure to turn on Kontakt and Omnisphere memory servers and that should help. Even at that PT still sucks with VI's. From there the best bet is VE pro, or some people host VI's in Reaper via rewire.

Exactly.. Pro Tools will start getting screwy as soon memory usage gets to around 2.3 GB. (Keep an eye on memory usage with OSX's Activity Monitor.)

Kontakt works just fine if treated right. Omnisphere works too but as you audition patches, it doesn't free up memory properly and you can soon start eating into PT's memory allocation even if you're using the Omnisphere memory server. Same thing happens with RMX and Trilian. (I wish Spectrasonics would fix this!)

[Marsdy]

Originally Posted by nst7

Also make sure you have set Protools to use less than the maximum processors available. It should show 24 available, try setting it to various other combinations, such as 21, 15, 11, 5, etc.

Exactly again... My 6 core works best with PT set to use 6 of the 12 available cores. (I think it defaults to this after installation/prefs trashing.)

[lemieux]

thanks everyone... let me try some of this stuff!

[lemieux]

Originally Posted by amolin

Your memory problems might be that some VI's is using the same memory space as pro tools, do you use kontakt's own memory manager?

Thank you! It seems to have worked WORSE when I tried this... but I wasn't really sure how to set pro tools memory and kontakt's memory along with one another. what works for you?

[Darryl Ramm]

The old bugbear with Kontakt was having multiprocessor support enabled in Kontakt. That could cause things exactly like this. I'm not sure of the latest behavior, I think you should get a warning if multiprocessor support enabled when running as a plugin, or a warning when you try to enable it, I am not sure. Try double checking multiprocessor support is disabled. Search here and the NI forums for 'multiprocessor Kontakt'.

[lemieux]

thanks again.

a tiny bit off subject but totally related... and i've already searched this here and in google but since some of you are having similar issues I am wondering if any of you have had experience with East West's PLAY. as in, is it worse or better than Kontakt as far as stability inside pro tools is concerned? if it's much better I just might switch for all of my orchestral stuff. THANKS