Just Another Optimization Question, Protools LE 6.7 under OS 10.3.7 Options

[deziderota]

Hey Guys , I'm not sure if I'm posting this in the right place but I sure hope some one can help me out.

So here's my deal...... I'm pretty new to the whole MAC world but far from new in dealing with PCs. I'm running a Dual 2ghz G5 with 1.5 gig of ram. I've got the latest version of OS X which I believe is 10.3.7 and I'm also using Pro Tools LE 6.7. My problem is I'll load up a session with a few soft synth plugs and sampler stuff and what have you... start to play the stuff but 20 seconds or so into the song the stuff will give me an error. To be exact it will be a -9128 error which basically says i'm running low on process power and that I should take out some of the plugs. Now I'm not sure but having the specs that I have tells me that I shouldn't be having those problems at all especially since I was getting those same errors when all I had was 512mb ram. All my samples and audio are being stored on their own drive and its a SATA 10000 rpm drive so that shouldn't be thr problem either. I'm lost!!!!!! LOL. Is there anyone who could point me in the right direction. I don't want these issues especially since I was using a 2.8ghz PC with about the same size ram and HD specs and getting the same problem. I was under the impression that moving to the mac would solve this. I almost feel as if I should have just stayed where I was but since I'm here now I'm sure there has got to be a solution. Please SomeOne AnyOne .....LOL..... Help. I would greatly appreciate it.

[deziderota]

Well...... It doesn't say its a DAE error althoug it may very well be. I remember getting errors like this on the PC as well but it would specify. The official wording goes as follows: You are running out of CPU power. Remove some RTAS plug-ins or increase the CPU Usage Limit in the Playback Engine dialog. (-9128). Funny thing is my CPU usage is 65% and the H/W buffer is 512. Sux that I would have to keep it so high for it not to crash. That latency sure as hell sux. The DUC is kinda hard to search most times cause all you have there are people bashing the program as opposed to giving solutions. I'm not for that. I encountered another error last night after I posted this too. It was a (-6086). I'm not sure how familiar you are with all these error codes but that was the 1st time I'd seen it. I'm going to do a search to see what I come up with but as of now my system is not doing what both you and I feel it should be doing. AGGGGGH. LOL. $2500 seems like it has gone to waste. Well not entirely but you know what I mean. Thank you for your input so far though. I really appreciate it.