While boucing a stereo mix down to a stereo track (via sending all tracks to a bus and then using that bus as the input to a stereo track, then sending that track to the main outputs), I get the following message after about two minutes:
"DAE can't get audio from the drive(s) fast enough. Your drive may be too slow or fragmented, or a firewire drive could be having trouble due to the extra firewire bandwidth or CPU load."
The firewire drive has 14 Gigs of space left, and I am running on a Mac laptop to a LaCie Porche drive. I have a Pro Tools 002 system that is less than two years old.
I have three tracks that I'm recording down, and have a reverb plugin and MaxI'm running on the aux track I have the entire mix on.
I've tried saving copy in... and copying all audio files to the main drive of the laptop, then dragging the copy onto the Firewire drive. This did not work. I tried a 3rd party Mac defragging program on the drive that finished in a minute. That did not work.
Any ideas, folks?
Comments
Need more info, model Mac, Ram installed, free disk space on sys
Need more info, model Mac, Ram installed, free disk space on system disk.
Version of the OS, ect.
8)
Will Do. Any quick thoughts?
Will Do.
Any quick thoughts?
Turn off journaling, if it's on (even though Digidesign suggests
Turn off journaling, if it's on (even though Digidesign suggests otherwise).
Check in (i think) hardware settings and make sure the drive is set to Record.
Increase the Hardware Buffer Size in the Playback Engine.
The firewire drive has 14 Gigs of space left, What size drive??
What size drive??? On a 100 gig drive you're pushing it. On a 200 gig drive, you're going to lose you're work.
You need to leave 10% for overhead.
Also in Protools, do not record with open ended disk allocation.
Limit the disk allocation to just a little more than you need.
Also, why do you bounce to disk?? Record to track takes the same
Also, why do you bounce to disk?? Record to track takes the same amount of time, you can always stop, do a fix, and keep going using destructive record. Then export/convert.
Record to track uses less CPU resources than bounce to disk.
If you insist on BTD, then uncheck the convert during bouce option.
Lastly try removing a plugin at a time to see if there is a plugin causing too much load.
I AM recording to a track. "While boucing a stereo mix down to
I AM recording to a track. "While boucing a stereo mix down to a stereo track (via sending all tracks to a bus and then using that bus as the input to a stereo track, then sending that track to the main outputs)"
When I try to bounce to disk, I get the same error, except it takes about twenty seconds.
I also bypassed the plug-ins, and it did the same thing. I forgot to put that in the original post, sorry.
OK, that confused me. Dont use the term bounce to disk when reco
OK, that confused me.
Dont use the term bounce to disk when recording to track.
Bounce to disk is a separate function in Protools, record to disk is the term used to rerecord through buses to another track. Yes, that is the preffered method.
Is it a 9073 error???
Dont "BYPASS" the plugins to isolate, remove the plugin completely.
Save your plugin settings, and remove the plugin, if that doesnt solve it, reinstate the plugin, and remove the next one.
If you use more than one instance of the same plugin, on whatever separate tracks, then remove ALL instances of that said plugin to diagnose completely.
Did you also verify you DO NOT have open ended recording set in your allocation preference??
And, are you near the last 10% of your available drive space??
You never mentioned what CPU you are using. Try turning off the second processor allocation in Protools.
Verify your firewire chain is correct, are you daisy chaining off the 002?? Switch to drive first then chain to 002, and vice versa.
Is your version of Protools commpatible with your OS version??
The error never specifies a number-- it is exactly as I typed it
The error never specifies a number-- it is exactly as I typed it in above, nothing else.
Here's what my Audio drive is:
Capacity: 232.75 Gig
Avaible: 45.3 Gig
Used: 187.4 Gig
Computer:
OSX 10.4.2
2GB DDRZ SDRAM
Pro Tools LE v. 7.0
I've never had this problem until about two weeks ago; the only other error I have gotten before was due to having the playback engine set too high to bounce to disk (as my client wanted to do).
How do I check the Open Ended Recording setting? Preferences?
I'll try removing the plug ins tonight. I'll be back online Monday.
Download the PTLE 7.1 updater, I think it's free for 7.0 users.
Download the PTLE 7.1 updater, I think it's free for 7.0 users. 7.0 was buggy and was replaced with 7.1 almost immediately. Check this forum.
http://duc.digidesign.com/
Lets us know, are you "bouncing to disk" or "recording to track"
Indeed seperate functions.
I get the error on both (as my clients expect me to bounce to di
I get the error on both (as my clients expect me to bounce to disk in front of them, as other studios around have done just that), but I am recording to track in the instance where it takes a minute or two to mess up.
as my clients expect me to bounce to disk in front of them, Why
Why would they?? Boucing has been proven to be flawed in Protools.
I personally have seen (heard) automation problems while bouncing.
And thats on an HD3!!!
Record to disk takes no more time, one hiccup, and you need to start over, will that client pay you the extra time to start over??
So what order is your firewire chain?? 002 -> drive or drive-> 002
I woul personally also update to OSX 10.4.9 and PT 7.3, including updating plugins.
Laptop-->Drive-->002. I'll update when I can; internet access t
Laptop-->Drive-->002.
I'll update when I can; internet access that'll allow me 100+Mb download is very sporatic (sp?).
And I'm in Mississippi. The clients expect conformity, or they go somewhere that will conform to their expectations.
Does the amount of space left on the hard drive look sufficient, or should I remove about ten gigs?