ProTools Crashy McCrashalot

gardenside · Post by **gardenside** » Wed Jan 17, 2007 7:52 pm

So,..Went down to record at the Ship in Eaglerock had a great time great experience all round. Came back home to my PTle with a digi 002 plugged in external hard drive everythings cool. Transfer all the session files to an internal drive (SATA MAC G5) and everytime I try to open a session protools loads, finds the files, frames out the edit and mix windows then crashes. "Protools has closed unexpectedly". Every once in a while the transfered file will work a couple times then crash. I can work off the external with seemingly no problems but why is this happening? I switched the drive allocation to my internal. I have a dedicated capture drive and am clocking to a Rosetta. I tried switching to clock to the internal (002), made no difference. The complete session file is transfered. I've spent a couple hours trying everything I can think of. I think the ship is running PT ver 5.? but,.......wtf? Again, I can work of the external with no issues so far, but damn it's frustrating? Any ideas?

runrunrun · Post by **runrunrun** » Wed Jan 17, 2007 10:21 pm

probably best for you to ask the same question over at http://duc.digidesign.com

tons of ptle experts over there should be able to help out.

E-Rock · Post by **E-Rock** » Thu Jan 18, 2007 10:34 am

You can't run a session off the internal drive. At least I can't

You need to run it from a firewire drive.

gardenside · Post by **gardenside** » Thu Jan 18, 2007 3:48 pm

thanks for the digi link. I have two internal drives and I work off them all the time. thanks for taking the time to respond.

GooberNumber9 · Post by **GooberNumber9** » Thu Jan 18, 2007 6:35 pm

gardenside wrote:I learned it by watching you.

Totally OT but I can't believe someone else remembers this ad.

Al_Huero · Post by **Al_Huero** » Thu Jan 18, 2007 7:34 pm

The internal drive issue should only be if the Protools program and session files occupy the same drive; this presumably can cause issues.

It may be something in the session file is corrupted. A workaround if all else fails would be to export the individual tracks as files (from the edit window, menu on the right hand side of the screen) and then reimport them into a new session you create. Make sure all the tracks have the same start point so you can line them up when you re-import them.

these_go211 · Post by **these_go211** » Fri Jan 19, 2007 5:40 pm

it can be an internal drive. it just shouldn't be the system drive.

Message Board

ProTools Crashy McCrashalot

ProTools Crashy McCrashalot

Who is online