PT8 with iMac 10.6.8, 4GB RAM (All optimizing DONE) Still Getting CPU Overload-HELP?

  • Thread starter Thread starter Athos
  • Start date Start date
Ram seems to have helped a little bit. Still stopping, but not as often.
I do not believe that the auto backup is on - though I have to check to make sure (at work right now).

I have ProTools running off the internal hard drive with the session file on an external FW800. This is how I've always done it. I'm not recording to the computer's internal hard drive.

My audio is through the interface, an M-Audio Fast Track Ultra (I miss my little upright LE MBox SO badly).

I was running about 23 tracks last night with about 8 plug ins, and it still stopped. Also, it's doing weird things like not playing a track, or not kicking in where the automated mute turns off. I have to stop it, and replay it, sometimes twice, before it finally kicks in.

I'll tell you, I NEVER had these issues with my old Dell. If this is how Macs run - weak - then I'm becoming less of a fan. I've tried every setting on the playback engine. Always the same thing: stops with the stupid CPU overload, or the elastic audio... Stupid.
If I was pushing like 33 - 36 tracks, I'd understand. But this is rediculous.

If anyone has any other ideas, please share. There is no reason I should be having these issues.

Makes me wonder if I should just change DAWs altogether...

Thanks for everyone's input. Sorry for my frustration.
 
It's not how macs run.

I can understand your frustration, but dude, do everything in the thread before asking for more.

Have you run apple diagnostics yet?

If you run it and find out you have a hardware fault I'll piss myself.


edit.
Avid.com specifically lists 10.6.8 as compatible with 8.0.3 m-powered, but there is an 8.0.5 out now. Would be worth trying.

I know you said you're up to date on drivers, but to be certain, are you on this version?
 
Yes, I have 2.1.1. for the interface.
As far as I can tell, I've done everything in the thread.

Being relatively new to Macs, perhaps you could tell me where I run apple diagnostics. Sorry, but I don't know where to find that operation. I assumes it's in the tools folder... ? Not at my comp right now. I'll run it when I get home. This may be the only thing I haven't done yet.
There's a lot of stuff here recommended, and I've tried to do it all. If you think there's something I haven't done, let me know.
Thanks for your patience and help.
 
No probs. I'm sorry you haven't really got anywhere yet.



Are you on Pro Tools version 8.0.5 as above and as per other thread?

To run the diagnostic tests (as in post 8) reboot your mac holding the 'D' key.

If that doesn't work, insert the original install disc and reboot holding 'D'



EDIT.
Hey athos. I've just noticed, in your other thread you talk about a red spike on the memory usage graph.

There is no memory usage graph! Are you talking about the disk activity graph?
 
Yes, just updated PTs to 8.0.5 last week. I'll try diag. tonight. Anything in particular that I'm looking for? Or will it be obvious if it finds a problem?
When I was on my pc, I was a wizard. Still learning Apple environments. Generally similar, but different names for things...

and yes, I probably meant that for the red spike. Was not at my mac when I typed that.
Could have been the disc activity graph. It's not the one with the green and red squares that stack up. It's the one with the green and red lines... The red line is the one that spikes every so often. Not too often... but when it does, it shoots all the way up.
 
Ok cool. That graph you describe is disc activity.

A peak in itself isn't a bad thing. It will give you the exact speed above. It will say "Peak = 4.5mbps" or something like that.

Find out what the exact value is when your sessions is running and crashes.

If it's high, you'll know that it's the problem.



The diagnostic thing is fully automated. There's a quick scan and a thorough scan. Run whichever you like but the be aware that the full scan takes a long time.

The quick one takes a few minutes. As far as i know, it will test your ram, cpu, hard disk, and maybe graphics, idk.

It is the easiest way to find out if you have a defective ram module.


Something else that came to mind is unlikely but try it anyway. Download a tool called temperature monitor, or hardware monitor for osx.
See if your temps are running high when it crashes. It's a long shot but again, worth ruling out.
 
OK, cool. Thanks.

I thought about that too. Sometimes it does heat up pretty good.... I'll try it.

Catch ya later.
 
Didn't have time to do the temperature thing last night. But I ran diagnostics, and it found nothing. It said everything is good. That was the quick run. I'll do the longer one tonight.

Was mixing some tunes for a little while last night and had no issues. Weird.

I'll just keep digging until I find out what it is. I'll see what I can find this weekend.

Cheers!
 
You must log in or register to reply here.
Back
Top