FCP 5.1.2 Unexpectedly quits during p2 log

boy_afraid

boy_afraid

Member
Has anyone else experienced the problem in FCP (5.1.2) that trying to preview some CONTENTS folders causes the program to unexpectedly quit?

This happens to me only occasionally, and honestly I only have 500 mb of free space on my internal HD (everything else is on a nearly full external HD).

I expect this is the problem, but please let me know if anyone else has had this happen!

thanks,
brooks
 
Some information would be helpful.

OS and QT versions.

CPU, RAM?

What media drive and interface?

Where do the p2 contents reside?

Where is the scratch/capture disk set to?
 
You need a couple gig free on your system hard drive for OSX to work right. If your system disk is 500 meg, that's your problem.

I run FCP5.1.2 and P2 log and have never had an issue.
 
I had a similar problem when trying to import one particular card folder (with contents and lastclip.txt file inside). Whenever I would drag that folder into the P2 import window in 5.1.2 the application would suddenly quit. Only one of my P2 cards did this to me out of about 44 cards for this project.

I found my solution by accident. Before I bought FCP I happened to bring in that particular card (burned to DVD) to an Apple retail store to try out the new version of FCP (5.1.2). Some of their computers had FCP 5.1 (not yet updated) and some had 5.1.2, but for whatever reason, the problem application quitting problem only happened when importing this card on the newer 5.1.2 computers. So, I uninstalled 5.1.2 on my home computer and tried it again with version 5.1 that comes out of the box. And it worked! Because my footage is 720PN I was a bit paranoid reading about this duplicated frames rendering problem in 5.1 so I followed the Apple instructions on exporting these clips so I won't have that problem. Just in case. I hope it worked.

Looking at the clips after importing this card in 5.1, I noticed something strange. There was one clip that had no footage, it had a start timecode and end timecode that were the same. I guess somewhere along the line something got messed up somehow. I'm just glad I stumbled on this solution by accident.

I hope it works for you as well.
 
You must log in or register to reply here.
Back
Top