Activity › Forums › Apple Final Cut Pro Legacy › “Unexpectedly Quit” is no longer unexpected
-
“Unexpectedly Quit” is no longer unexpected
Posted by Rip Swan on November 30, 2008 at 11:31 pmI’m using Final Cut Pro 6.0.1 and I am working on a short project, but for the past week or two the program “unexpectedly quits” every time I try to render a clip or simply play the project for more than a minute or two.
Please help because I kind of need to work on my project, which is currently impossible. Any advice is greatly appreciated!
David Fortin replied 17 years, 5 months ago 5 Members · 7 Replies -
7 Replies
-
Eyad Hamam
November 30, 2008 at 11:39 pmThat’s happened to me a few times when I used certain effects on 6 and 6.01. Unfortunately I can’t remember which plug-ins were causing the problem. Are you using plug-ins? You mentioned rendering so I assumed you may be.
-
Rip Swan
November 30, 2008 at 11:43 pmI’m just doing things like adding stock effects or even moving the clip around. The bar above the two clips is now always red when i open the project so i press “command R” or render both and the program quits every single time.
But it is not just rendering. I just now opened the project and watched the sequnce and then was simply scrubbing back and forth when it quit again.
-
Eyad Hamam
November 30, 2008 at 11:46 pmHow come it needs to render all the time? Is your sequence setting the same as the clip?
-
Eyad Hamam
November 30, 2008 at 11:51 pmps… I think FCP 6.01 wasn’t very stable to begin with, so if you can upgrade (free download) to 6.03-6.05 that’s probably a good idea.
-
Rafael Amador
December 1, 2008 at 1:28 amHi Rip,
May be or may not be that the reason of your problem, but I agree with Eyad about updating FC.
FC 6.0.1 was very unstable and full of bugs. I think was updated just few weeks after his release.
Rafael -
Jason Levy
December 1, 2008 at 6:04 amWhen we have had problems like that is has often been due to running out of memory. FCP is very ungraceful when the system gets low on memory. You can check how much free memory is available by running Activity Monitor (in utilities) while the suspect project is open in FCP, and checking the system memory tab. I find having at least 500 megs free is safe.
Usually that problem does not occur on small projects.. but it is possible if you have put a lot of stuff in your project that you don’t need, even though your program is short. For example if you have a large music library it is tempting to put it in your project for easy access but that will inflate your project size a lot.. likewise if you make multiple copies of your sequence.
We had an editor who was making multiple copies of a one hour show sequence each day and popping them in a bin. After a couple of weeks the project was a monster. Took 10 minutes just to load. You can’t do that. If you have a music library or similar it is better to get the elements right from the finder as you work.
How much system memory are you running? I think 2 gigs is really the absolute minimum for smooth operation of FCP these days.. 4 or more is better. If you are editing a one hour program 2 gigs is not really enough.
Good luck..
jason
-
David Fortin
December 2, 2008 at 12:23 amAND if this is something that just starting happening, check to see if you have a bad memory chip. Went through weeks of problems of the system freezing and or quitting during a render. Problem got continually worse until I couldn’t even render a 15 second piece. Come to find out 2 of my 4 1GB memory chips were bad. Replaced the memory and now (knock on wood, I just did it this afternoon) FCP is rendering without a problem.
David
Reply to this Discussion! Login or Sign Up