CPU Overload (error 6101) on intel macbook pro

[JrummerJ]

So, a follow up. I've tried a few things:

Reinstalled OS 10.4.9, PT 7.3.1 cs5, M-Audio driver 1.8.2. Still exp problem.

I bought a siig fw 400 expresscard to get the external hd on a different bus. CPU usage seemed better, but still got the error.

Tonight I copied over a few sessions to the internal drive, and was unable to get the error on a session with 12 tracks including: 9 audio, EZdrummer, Xpand, and a master fader...even adding up to 16 D-verbs and lowering the buffer to 128! Oh yeah, and airport and bluetooth were on, too.

At this point, I would have to chalk it up to either the drive or the inability of the mac to have multiple firewire devices connected at the same time. Both of these are a little hard for me to accept. The same drive worked flawlessly on my AMD desktop even chained through the 410. As far as the mac goes.....it should just work

Next steps: borrow another firewire drive to try, or just get a glyph or Lacie.
So, what do you guys think?

Thanks for those who tried to help.

J

[bradch00]

I would try another drive, I mean you've really done almost everything else. I don't know what chipset WD puts in their drives, but if you do try another one, make sure it has a compatible chipset (Oxford 911 for FW400 drives). I know people have had success with the additional FW card, so this really does point to a drive issue.

[brian5258]

i'm having the same problem on a brand new mac book pro intel 2.4ghz on 10.5.3

i'll have like two tracks open and i'll get that error randomly. the cpu usage has never gone above 25%

[milan cutlac]

Hi Brian,

Did you solved the problem ? I'm using PT since 3-4 weeks now and I cannot get rid of the same error under same circumstances : a 2 track session. I read about less powerfull Macs than mine that work very well with PT, so this is very confusing.

Regards,
Milan

[axisrecording]

Same Problem here -just got a macbook pro, after killing my powerbook. running 7.4.2cs or whatever is current. current everything. checked through all the docs on install. been through a lot of threads, I sent a client home today it was so bad, Trying to make a living. DIGI?? I had better performance on an old G3

[DigiTechSupt]

Originally Posted by axisrecording

Same Problem here -just got a macbook pro, after killing my powerbook. running 7.4.2cs or whatever is current. current everything. checked through all the docs on install. been through a lot of threads, I sent a client home today it was so bad, Trying to make a living. DIGI?? I had better performance on an old G3

We're going to need a lot more info - see the Help Us Help You thread for details...

[Wolfgang Eller]

OK, next one with the same Problem.

Recording 2-8 Tracks with a 2.2 Ghz Macbook Pro and 4 GB Ram.
7.4.2 CS2, 10.5.5, external FW 800 drive and a M-Audio 2626.
Buffer set 1024, DAE 4, no plugins at all.

I always get the message after a fresh start of the Mac within 10 and 30 minutes.
When it happened once it´s OK till the next time I have to start the Mac again.

And I´ve tried really everything.

Digi, please can you help me?

[JrummerJ]

Originally Posted by Wolfgang Eller

OK, next one with the same Problem.

Recording 2-8 Tracks with a 2.2 Ghz Macbook Pro and 4 GB Ram.
7.4.2 CS2, 10.5.5, external FW 800 drive and a M-Audio 2626.
Buffer set 1024, DAE 4, no plugins at all.

I always get the message after a fresh start of the Mac within 10 and 30 minutes.
When it happened once it´s OK till the next time I have to start the Mac again.

And I´ve tried really everything.

Digi, please can you help me?

I'd bet money that it is because you are using an external drive @800 speed and an interface that is @ 400 on your macbook pro. There is known issues doing this, since both ports share the same bus. Try chaining your drive with a 800 to 400 cable or with a standard 6pin 400 cable if it has other ports. I put my external drive on a siig expresscard and the interface on the macbook pro port and I really only experience this problem when I load up the session with VIs, which can be resource hogs.

J

[DigiTechSupt]

external FW 800 drive and a M-Audio 2626.

You can't do that. M-Audio devices are not compatible with FW800 drives. If your drive has FW400 ports, please use those, otherwise you would probably be best served by getting a Siig 2-Port expresscard and connecting the 2626 to that and the FW800 drives to the native FW800 port on the computer. Please see the M-Audio website for more info.

[Wolfgang Eller]

OK, but why do I have the same problem with a FW400 drive?

And why do I have NO problems after the first half an hour, anyway if FW400 or 800 drive???