CPU Overload (error 6101) on intel macbook pro

[DigiTechSupt]

Originally Posted by KeithKenny

You're not alone! I have recently upgraded to the mac pro to try to rid myself of these DAE 6101 errors. No Luck. These errors occur about 45 minutes into recording 8 tracks at 512 sample rate. I cant comfortably record any of the jam sessions in my studio without worrying about DAE 6101.

My system is:
Brand New Mac Pro - Quad Core
Snow Leopard OS X 10.6.2
Pro Tools 8.0.3
Project Mix i/o interface (connected via FW400 to FW800 adapter cable)
Latest M-Audio Driver 1.9.3
Recording to secondary internal 620GB Sata Drive (7200 rpm)
8 Tracks Simultaneously
No Plug ins
Buffer Size - 512 (I would prefer 128 to reduce latency)
Firewire networking disabled

Is your audio drive set to Private in the Spotlight control panel?

[Balls Magoo]

I have the same issue i get about 4 or 5 tracks laid down and about 4 or 5 plugins in use and I start getting the 6101 error. I have tried adjusting the buffer to all the different settings. I tried adjusting my cpu usage any were from 70% to 95%. Also removing half the plugins and no luck ! My CPU usage meter sets any were from 30%-50% so I know it's not overloading. ???? Any help would be much appreciated


MacBook Pro 2.26 Dual Core 4Gb Ram 500Gb HD
OSX 10.6.2 (Snow Leopard)
Profire 610
M-Powered 8.0.3

[leprechaun]

Getting exactly the same error here, bought a mac pro as I thought that would solve these issues, was on quad core XP....it hasn't changed a single thing....

I haven't experienced any other DAW that is as unstable as PT.

I've been through the same thing, though my version of the problem might be a little different. I usually don't get this Error Message when I'm recording, probably because I'm only recording one track: my voice. But I often get it during playback. I tried a bunch of stuff from different forums, etc. cshaw's battery solution (resetting the SMU) is intriguing, and I might try that.

In my case, I can usually just ignore the Overload message if it comes up while recording or during brief playbacks.

But when I'm doing extended playbacks, it will sometimes come on repeatedly. So now I've just gotten in the habit of increasing the HW Buffer Size to 256 before I do any extended playbacks, then setting it back to 128 when I record again.

Okay, I shouldn't have posted so soon about how I only get error 6101 during playback.

Today, a couple of hours into a recording session, the error message started coming on repeatedly. I finally had to increase the H/W buffer size to 256 to get it to stop. I would prefer to record with 128.

I will reset my SMU and make sure the audio drive is set to Private in Spotlight control panel (per DigiDesign team rec a few posts ago), but I feel like there's something bigger going on. I mean, I have no plug-ins, have a dedicated FW hard drive, and only record one voice track!

[leprechaun]

I agree, the problem certainly isn't one caused by stressing the system in terms of plug ins or high track counts. I too can get the error when I'm just playing back a project with no plugins and just a handful of tracks.

I wonder if it is related to using a FW audio interface? I'm using a Profire 2626 at the moment which works perfectly with my laptop and Cubase for recording concerts and location work. The same setup with pro tools however is unusable due to these errors???

[JrummerJ]

Originally Posted by leprechaun

I agree, the problem certainly isn't one caused by stressing the system in terms of plug ins or high track counts. I too can get the error when I'm just playing back a project with no plugins and just a handful of tracks.

I wonder if it is related to using a FW audio interface? I'm using a Profire 2626 at the moment which works perfectly with my laptop and Cubase for recording concerts and location work. The same setup with pro tools however is unusable due to these errors???

I actually think that you are dead on with this. I switched from the M-Audio Firewire 410 to the Fast Track Ultra (USB 2.0) mainly for the couple of extra XLR ins. I haven't had any of those annoying messages since I switched. The only thing that changed was the interface and all of the cpu errors are gone. The only time I have had one is when I was playing a session with 12+ tracks, and quite a few plugs at the lowest buffer setting. Not unexpected.

J

[leprechaun]

Originally Posted by JrummerJ

The only time I have had one is when I was playing a session with 12+ tracks, and quite a few plugs at the lowest buffer setting. Not unexpected.

J

That's it, I don't mind it telling me I'm pushing the limits when I actually am, but when I've got a project with a couple of tracks and maybe 2 or 3 plug ins and it gives me a 6101.....aaaargh!!!

Thing is, I really like the Profire 2626 and I'm not sure if there is an equivalent USB interface...

[Wolfgang Eller]

This 6101 error is still going on?
What a bummer!
I have just stopped using PT M-Powered for 2 track recording on my MB Pro with a 2626.

Not reliable enough!

I don´t want to lose money (and a client) cause a buggy software.

[leprechaun]

Just finished recording a string quartet in a nice church today and couldn't afford to use PT M Powered, I used cubase instead, will mix it in M Powered though...