|
  |
 Just Another Optimization Question, Protools LE 6.7 under OS 10.3.7 |
|
|
|
|
 Sat 15 Jan 2005, 08:32
|
Newbie
Group: Members
Posts: 3
Joined: 15-Jan 05
From: Lawrenceville - US
Member No.: 58,478
|
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.
|
|
|
|
|
|
|
|
Sat 15 Jan 2005, 14:43
|
Newbie
Group: Members
Posts: 13
Joined: 13-Jan 05
From: Melbourne - AU
Member No.: 58,389
|
Is that a DAE - 9128 error? The "official" fix is to set the buffer size to 512. This issue should be explained in the software update release notes. Most of these are online @ Digidesign. - Have you tried searching in the "Pro Tools LE Systems" section @ the DUC forum? http://duc.digidesign.com/Otherwise your setup looks like it could handle large 24/96 projects with no trouble at all.  I hope that helps in some way!
|
|
|
|
|
|
|
|
Sat 15 Jan 2005, 21:12
|
Newbie
Group: Members
Posts: 3
Joined: 15-Jan 05
From: Lawrenceville - US
Member No.: 58,478
|
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.
|
|
|
|
|
|
|
|
Sun 16 Jan 2005, 05:20
|
Newbie
Group: Members
Posts: 13
Joined: 13-Jan 05
From: Melbourne - AU
Member No.: 58,389
|
OK, you are still in PT Hell! Yep, with each error you can Google the code (e.g. search term = "error -6086, Pro Tools") and sure enough, you'll see a few links. But this could go on for weeks and you might not get anywhere....  If you want to save time, some real face to face to consultation on your whole steup could be a good thing. I clicked on your profile - just to see where you live - so maybe talk with the in-house techie at a local recording studio such as The Loft. A good techie usually has a lot of solid contacts. Anyway, its just a thought...
|
|
|
|
|
|
|
|
Sun 16 Jan 2005, 07:28
|
Junior Member
Group: Members
Posts: 125
Joined: 25-Sep 03
From: Brookfield, IL. - US
Member No.: 25,398
|
Tree Leopard has given you some excellent advice ..and the techie, (if he knows his stuff), will undoubtedly start off by asking you some simple questions. Questions like: Are you in the habit of keeping your hard drive clean and free of unnecessary files? Note: ..Some folks let ..third party downloads, ..PDF files, ..picture files(jpeg), unneeded/unused files, etc. pile up over time. And/or they don't organize/label their files. Over time, your hard drive gets more and more bogged down, thus having to sift through more and more of those files and especially those old third party downloads which may cause conflict and/or inevitably slow your computer down considerably. Have you run permissions?(Location: Applications/Ultilities) http://docs.info.apple.com/article.html?artnum=106214After upgrading your ram, did you make sure that it was recognized in your System Profiler? Did you zap your PRAM? Sometimes needed after installing new ram modules/sticks, in order for it to be recognized. http://docs.info.apple.com/article.html?artnum=2238.......On the apple site there's alot of helpful maintenance tips and solutions. If the techie guy can't come to your rescue right away, ..while you wait, you might want to put a day aside(no distractions) to do the above, along with some serious reading and testing, so that you may finally resolve, once and for all, what I know must be a frustrating issue for you. ....Be prepared to possibly uninstall and then reinstall Pro tools. My personal opinion: ...If indeed you are organized with your files and you use that little trash can, in the lower right hand portion of your desktop, on a frequent basis, then I would say that it is most likely 1 or 2 or all of 3 things. 1. The ram you purchased could be bad. 2. You have a software conflict. 3. Sometimes it can be driver, or the lack of a driver update. On a sunnier note, ...I can tell you with great certainty that once this is all behind you, your set up is up and running as it should and you've gotten to know your Mac a bit more, ..you'll never look back. Hopefully the above was at least a little helpful. ......Good luck to ya!
|
|
|
|
|
|
|
|
Mon 17 Jan 2005, 03:01
|
Newbie
Group: Members
Posts: 3
Joined: 15-Jan 05
From: Lawrenceville - US
Member No.: 58,478
|
Hey Guys
I realy appreciate all the info. I'm gonna try these things out and check back and let you know how it all went down. If there is anything else that anyone would like to add please feel free.
|
|
|
|
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
|
|
|
