"PT cannot access more than 4GB and PT 8 will not change this"

[goga]

So... why are plugs like Omnisphere, Amplitube, T-Tacks, still crashing my computer?
I do have 4G RAM and everything is updated, done by the book and all legal plugs.
I changed from Cubase to PT about two years ago. I still cannot see the benefit of it. More money spend, more problems!
The reason I chose PT was exactly the stability of the system. Everybody called it " industry standard". IT'S NOT. Not sure HD is still or how long they can sustain it.
Too many problems.

[Craig F]

and what do your Crash Logs tel you?

[goga]

It says that I run put of CPU: "...increse buffer.." bla bla bla.
And I did studied the "Troubleshoting Thread", I did reduce the nr of processors to seven, and all the other things.
And I do have an ok equipment and computer (more than enough for a home studio), as you all can see.
Still...

[barry1]

one quick solution is to process all your audio tracks with effects into a track one by one then delete that track which had them on it, previously....this way u r dealing with finished audio tracks with no effects...this saves cpu power...yea i realize its the long road but it works.

[goga]

Thank you Barry.
Your solution, of course, would work.
But then again, you would call that "the industry standard", would you?

[barry1]

nope but on the LE or M version is best u can do....digi has not found the way like apples logic pro studio......so its the best u can do...i think digi's theory is to process everything into a audio track b4 adding anything on...i know that disrupts the creation process..

[Keybeeetsss]

I say its ur computer; if u know me & the way I push my rig, Stylus, Omnisphere, Mini Grand, 20+ Auto tune instantiates, many plugs, Structure, Vienna, etc. is a normal session for me & always without problem & usually always @ 64buffer setting... With no crashes or hiccups...

[albee1952]

Originally Posted by barry1

one quick solution is to process all your audio tracks with effects into a track one by one then delete that track which had them on it, previously....this way u r dealing with finished audio tracks with no effects...this saves cpu power...yea i realize its the long road but it works.

I'm with KB here, and while the above method can help, DON'T delete the original tracks!! You don't need to as you can simply make them inactive and hide them(so you can still call them up if you need them). Inactive tracks don't chew up resources.

[KRAFT]

I too agree with KB and albee on this. My old imac with only 2 gigs of ram can withstand quite a few plug-ins, VI's, and still keep going. Maybe check to make sure you have turned off bluetooh, airport, dashboard and any other un-needed software. Also, try cutting back on the number of processors even more. I read on a thread not long ago that less is sometimes better when it comes to this. Something about allowing more processors to do other things with some plug-ins. Just a thought.

[Dism]

This issue really has nothing to do with how much RAM PT can access anyway. Several of the heavy VI's and other plugins depend on resources outside of PT. So while PT is accessing 4GB for itself, there are other resources that even background processes require for stability. This is why it is typically recommended to reduce the number of processing cores PT is using, and to use plenty of RAM, etc. This way your system can breathe, your plugins have spare resources outside of PT, and overall stability improves. Makes sense?

PT accessing 4GB of RAM has only to do with the fact that is based off 32bit architecture, and it simply means that PT itself can only access 4GB at a time. But that doesn't mean more RAM won't help PT run more smoothly. In a 32bit environment, EACH application can access up to 4GB of RAM. Which means more RAM will improve OS performance, VI performance, and various other tasks where your computer is running multiple programs at once (which is always).

But... I'm with the majority on this one. A Mac Pro, even an early generation, should have NO issues blasting away with tons of tracks and plugins. Considering that my early 2008 Macbook Pro can handle 70+ tracks with 90+ plugins all running together...