One project gives me the beach ball, help!

D

DM_rider

Veteran
Alright, so I am working in FCP, v 6.0.6, 15" i7 mac book pro.

I have one project that gives me the spinning beach ball as soon as it loads. I have trashed prefs, repaired permissions, all the typical fixes, nothing has worked. I am able to open every other project and edit completely fine. The last time I opened the project was about 2 weeks ago, went on vacation, and now it wont open, not even the back up. I was also able to open the project on another computer and edit fine. So, it's not the project file, but my mac. Any ideas other than completely re installing FCP?
 
What are the sequence settings for the project, and what does it consist of?

All what dedicated external media drive are you using?
 
have you tried saving a new project file from the computer that will open it up and bring that back to the original computer and open it?
 
David S. said:
What are the sequence settings for the project, and what does it consist of?

All what dedicated external media drive are you using?
Click to expand...

I am working off a rugged 320gb drive for the project, backups are on 2 usb 2 drives, neither of those will let me edit either.

All sequences are pro res, all 7d footage. I have opened 2 other projects with the same settings and they open fine. Both were on different hard drives.

I opened the project that was giving me trouble on an 8 core tower, same version of FCP, no issues at all.

Before I left town, I had the project open and it was working fine. I left the hard drive with the troubled project behind, but was working on other projects while on the road. Got back, tried to load the troubled project, no go.

Here is what I get when I repair permissions. I am guessing this has something to do with it. I get the same erros each time.

Repairing permissions for “Macintosh HD”
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/Contents/Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/deploy.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/Contents/Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/deploy.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/deploy.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/deploy.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/libdeploy.jnilib", should be -rwxr-xr-x , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/libdeploy.jnilib".
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconfig" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writeconfig" has been modified and will not be repaired.

Permissions repair complete
 
How did you transcode the 7D footage to pro res? What version of pro res to did you transcode to?

Is the pro res footage stored on the rugged drive? Are you using the Firewire 400 or Firewire 800 connection to your Mac?

How much free space is on the media drive?

Is there a reason you are editing off an external FW drive rather than an internal SATA drive?
 
How did you transcode the 7D footage to pro res? What version of pro res to did you transcode to?
Log and transfer with EOS plugin, Pro Res 422

Is the pro res footage stored on the rugged drive? Are you using the Firewire 400 or Firewire 800 connection to your Mac?
800, and yes, the entire project is contained on the drive

How much free space is on the media drive?
145 gb

Is there a reason you are editing off an external FW drive rather than an internal SATA drive?
No reason really. I've always worked this way, just how I edit I guess.
 
I trashed the prefs one more time, thinking it would never work after doing it 10 other times, and I was able to playback footage for about 30 seconds, then the project crashed again.
 
Consider copying the project to an internal SATA drive, and try opening it from there.

At least that eliminates the HDD as the issue.
 
You must log in or register to reply here.
Back
Top