Memory error question for those TDM users running 10.3.8 on Mavericks 10.95

[anodecathode]

As we all know 10.X is not supported on Mavericks but it's been rock solid for me for the last 5 years. No issues whatsoever until my memory upgrade today.
I'm running a 2009 Mac Pro Nehalem 2 X 2.26GHz Quad-Core Intel Xeon with OS 10.9.5 Mavericks - 128GB ram.
The ProTools system is a TDM HD6 using a Magma Expansion Chasis, PTHD 10.3.8 with an Avid I/O.
I just upgraded the system memory from 32GB to 128GB via OWC's memory upgrade kit. https://eshop.macsales.com/item/OWC/85MP3S9M128K/

Everything was working great until I launched ProTools, I got the following error:
"The current Playback Engine requires more system memory than currently available. The Playback Engine dialog will automatically be launched."

I assumed this meant ProTools couldn't access any of the 16GB sticks and the only way I was able to fix the problem was to swap out the last two (5 & 8) slots of ram (16GB 1066 DDR3 sticks) with the previous ram sticks that I had in there (4GB 1066 DDR3) reducing my memory total to 112GB. This is fine as I will mostly be using the additional ram for Kontakt & Play (piped in via Source Connect Nexus) but I'm curious why ProTools couldn't "see" the 16GB sticks. (if that is the problem??.) I’m thinking ProTools is ignoring the other 112GB of memory and that it may have something to do with ProTools 10, a 32bit application having to run on Maverick's 64 bit kernel?
Any info would be greatly appreciated.
Thanks!

[JFreak]

First of all PT10 is 32bit application and can only see 4GB of memory so installing 128GB is pretty steep...Nehalem that I use (with Mavericks) has 48GB and cannot use it all. Maybe you could try installing PT10.3.10 and see if it fixes your issue?

[anodecathode]

Originally Posted by JFreak

First of all PT10 is 32bit application and can only see 4GB of memory so installing 128GB is pretty steep...Nehalem that I use (with Mavericks) has 48GB and cannot use it all. Maybe you could try installing PT10.3.10 and see if it fixes your issue?

Thanks for your response JFreak! Great suggestion. Was using 10.3.10 at one time but I think I read (possibly on gearslutz?) that the co-install works better with 10.3.8 (weird I know.. and it could be baloney.)
But have to say that 10.3.8 plus 12.8 co-install has been problem free for me for since the install, so I guess if it ain’t broke.. So I may keep what I have going. The extra 106GB is only for Kontakt, Play, AudioMulch and several other 64bit soft-samp/synths that I’m piping into PT via Nexus. So far it seems to be working well! Seems like ProTools is just utilizing the two 4GB sticks for GUI/RTAS etc.. TDM processing is of course handled in the Magma and remaining memory utilized by system and my soft-samps/synths.
I’ll run it through some tests and let everyone know back in a few weeks. (For those running into the same issue.)

[crizdee]

Hi,


I get the same problem sometimes. but i just have to reboot once or twice and it settles down for a while.


I never seen this issue ever in Mountain Lion, it started when i updated to Mavericks.


Ive also noticed that pro tools on mavericks is less capable of accessing ram than it was on mountain lion. on mavericks i get to about 3gig and PT will quit. on ML i could go beyond that and rarely got quits due to memory.


Just means i have to be careful and occasionally bounce things that use lots of ram, trigger 2 is a hog and some delay plugins etc. i keep the mac system usage window open and keep an eye on memory.




Chris

[groovebrother]

no problems here with 80go of ram installed on mavericks and using the last tdm pro tools version available.


But if i boot the mac on high sierra using pro tools 2021 with the hd native card, when booting back on mavericks i get that same memory adjustment problem if i leave my HD Native card in the mac with the magma card.
Pulling off the native card makes it work again.


Sometimes when booting back on mavericks it all works with a simple pro tools prefs cleaner but mostly i have to pull off the native card

[anodecathode]

Originally Posted by crizdee

Hi,


I get the same problem sometimes. but i just have to reboot once or twice and it settles down for a while.


I never seen this issue ever in Mountain Lion, it started when i updated to Mavericks.


Ive also noticed that pro tools on mavericks is less capable of accessing ram than it was on mountain lion. on mavericks i get to about 3gig and PT will quit. on ML i could go beyond that and rarely got quits due to memory.


Just means i have to be careful and occasionally bounce things that use lots of ram, trigger 2 is a hog and some delay plugins etc. i keep the mac system usage window open and keep an eye on memory.




Chris

Thanks for the reply Chris!
That’s interesting, I haven’t run into the 3GB cap yet in Mavericks. I always felt like it gave me more RTAS bandwidth but I could be wrong. I’ll keep an eye out for that now that I’ve upgraded my memory.
Last night my system did have a Kernel Panic while working on a medium to large session. I’m hoping it was a fluke. If I start running into a bunch of problems/shut downs I may go back to 32GB memory.
Scott

[anodecathode]

Originally Posted by groovebrother

no problems here with 80go of ram installed on mavericks and using the last tdm pro tools version available.


But if i boot the mac on high sierra using pro tools 2021 with the hd native card, when booting back on mavericks i get that same memory adjustment problem if i leave my HD Native card in the mac with the magma card.
Pulling off the native card makes it work again.


Sometimes when booting back on mavericks it all works with a simple pro tools prefs cleaner but mostly i have to pull off the native card

Thanks groovebrother!
Very strange that having the native card in your chassis would cause that error.
I tried using the prefs cleaner with no luck.. I also zapped PRAM, repaired permissions reset NVRAM and no luck. Only fix for me was replacing the last 2 ram slots with 4GB sticks and leaving all of the others 16GB. So far so good.. Have had one Kernel Panic but it seems to have been a fluke.
I’ll keep you posted if I found out anything else about this error.
Scott

[groovebrother]

Originally Posted by anodecathode

Thanks groovebrother!
Very strange that having the native card in your chassis would cause that error.
I tried using the prefs cleaner with no luck.. I also zapped PRAM, repaired permissions reset NVRAM and no luck. Only fix for me was replacing the last 2 ram slots with 4GB sticks and leaving all of the others 16GB. So far so good.. Have had one Kernel Panic but it seems to have been a fluke.
I’ll keep you posted if I found out anything else about this error.
Scott

well in fact the HDN card is in the mac not the chassis.
In order i have video, HDN, Sonnet card, Magma card.


Have you tried a clean install ? (boring but often efficient)


Watch out that all your Ram is from the same company, that often causes issues if not.
In some cases restarting the mac with original ram only might solve the problem.
Before that : install applejack, launch pro tools prefs cleaner and select all options (just make sure all your HDD where the audio is, are online), shut down the mac, look out if there isn't too much dust in it, pull off all pci cards + clean the dust, pull off all usb connectors, reseting SMC, restart & after 1st gong press ALT + CMD + P + R till you hear 4 more gongs.
Once on your desktop, empty the trash, shut down the mac, add all additional ram, pci cards, usb, restart and launch applejack (CMD+S after 1st gong).
When maintenance has completed hit "R" for restart, launch pro tools and see what happends.

If none of this works, i would go for a clean install. Especially if all worked fine before you started having ram issues. But again if your ram isn't from the same brand you may have issues again.


The app applejack has a memory test fonction so you may want to check if your ram is all good. (i have done if long ago and it's a very long test).
If you install applejack : before entering your password you can personnalize installation by selecting the memory test program


This app is way more efficient than any osx disk utility including the apple's disk utility to repair permissions and much more. Be aware once you have started the mac with CMD + S your keyboard will be QERTY

[JFreak]

PT locks to first core card it finds, so if you have HDN in host computer and HDX in expansion chassis, there are two possibilities: on best case scenario it finds HDN and ignores HDX, on worst case scenario it gets confused unless you disconnect the chassis (for HDN) or remove HDN (for HDX)

[groovebrother]

Originally Posted by JFreak

PT locks to first core card it finds, so if you have HDN in host computer and HDX in expansion chassis, there are two possibilities: on best case scenario it finds HDN and ignores HDX, on worst case scenario it gets confused unless you disconnect the chassis (for HDN) or remove HDN (for HDX)

Hello JFreak in the chassis there are TDM cards not HDX. But believe me i think have tried all i could and it always ends with pulling off the HDN.


My only solution is to get me another mac pro which i will do and everything will be fine.


Thank you anyway