6101 error Pro Tools 8 :(

avrinder

Member
May 25, 2009
535
0
16
Canada
www.myspace.com
I'm trying to record 7 drum tracks on my Macbook (black edition, last generation) 4 gm ram. I keep getting error 6101 on my DAW. Sometimes after a few minutes...sometimes right away.

This happened with Logic Pro, as well (stopped recording, with an error) :( Any insight?? thanks a lot. :worship:

Below I've listed my set-up, etc

My specs:

-Macbook (Black) Last generation
-4 gb ram
-Leopard OSx 10.5.8
-M-powered Pro Tools 8
-Profire 2626
-Latest M-Audio Driver
-Recording to Lacie 301313EK Firewire (daisy-chained to Profire...no other choice, my laptop only has one firewire port...also made it MAC OS EXTENDED)
-7 Tracks Simultaneously
-No Plug ins
-Buffer Size - tried all, to no avail)
-Firewire networking disabled
-Airport turned off
-Bluetooth turned off
 
That would suck. Are they any other potential solutions? And if it IS the FW chip, is there a way I can test it before I take it in?

thanks a lot for the reply, by the way. :D
 
I search the DUC for you and found this:

"A CPU overload error occurred, if this happens try increasing the buffer size or removing some plug-ins -6101"

Every reference of this error it was a m-audio firewire device.
 
Haha, it could very well be the M-Audio driver as well. It sucks but M-Audio's drivers and support fucking SUCK. Luckily my 2626 has been absolutely rock solid with zero issues on my G5 so far. I know on Windows if you turn the 2626 off while the comp is on it will make some computers crash :loco: So this wouldn't surprise me to be the fault of the M-Audio drivers.
 
Ah, man! haha. I'll try again this weekend with our drummer. With all the steps I had taken to optimize recording...I still got the error haha.

thanks everyone! Hopefully it'll be ok this weekend. -avi
 
I'm trying to record 7 drum tracks on my Macbook (black edition, last generation) 4 gm ram. I keep getting error 6101 on my DAW. Sometimes after a few minutes...sometimes right away.

This happened with Logic Pro, as well (stopped recording, with an error) :( Any insight?? thanks a lot. :worship:

Below I've listed my set-up, etc

My specs:

-Macbook (Black) Last generation
-4 gb ram
-Leopard OSx 10.5.8
-M-powered Pro Tools 8
-Profire 2626
-Latest M-Audio Driver
-Recording to Lacie 301313EK Firewire (daisy-chained to Profire...no other choice, my laptop only has one firewire port...also made it MAC OS EXTENDED)
-7 Tracks Simultaneously
-No Plug ins
-Buffer Size - tried all, to no avail)
-Firewire networking disabled
-Airport turned off
-Bluetooth turned off

it's the daisy-chaining that's doing it. I had the same problem for a long time. I switched to the mbox 2 instead of a 002 and I don't have any problems. Remember as well that the firewire 400 and 800 ports run on the same buss, so on macbooks it's always a good idea to have a usb interface and firewire drive...or like I'm going to do...get a Esata card for the expansion slot.
 
Try a USB external hard drive. Everyone recommends firewire but I record to USB all the time with no problems and more tracks than you are trying to do.
 
it's worth a shot, I have it laying around. thanks for the tip. At this point, I'll try anything. Me being the pessimist, I'm just thinking "AHHH, I just want to record...why is this so hard?" (that's what she said)

thanks again
 
I just picked up an Mbox Mini and am having the same "CPU overload error" when playing back 10-15 tracks without any plugins running. I've got a iMac 2.8Ghz dual-core with 4GB RAM, MBox running in USB and hard drive FW800. Daisy chaining shouldn't be the issue here, as that they're not on the same buss. Any ideas?
 
I just picked up an Mbox Mini and am having the same "CPU overload error" when playing back 10-15 tracks without any plugins running. I've got a iMac 2.8Ghz dual-core with 4GB RAM, MBox running in USB and hard drive FW800. Daisy chaining shouldn't be the issue here, as that they're not on the same buss. Any ideas?

go to digidesign.com and make sure you've installed the latest drivers for the mbox's. Digi did a hardware update a year ago or something that not all mbox's ship with.