Activity › Forums › Apple Final Cut Pro Legacy › Crash on render
-
Crash on render
Posted by Scott Davis on June 13, 2009 at 12:29 amI can not render anything over 2-3 minutes that doesn’t cause a crash. No warning; FCP just disappears and when I restart it goes to a default window set up. Only workaround is to baby sit the render and do it in small bits. I see others have had the same problem but there doesn’t seem to be any solution yet. Any ideas?
PS-These are DV media and sequences with a lot of Motion Projects. Very little to no effects applied.
Thanks in advance,
ScottMacPro Quad 2.8
ATI Radeon HD 2600
4G RAM
OS 10.5.7
QT 7.5.5
FCP 6.0.5
Kona 3
CalDigit HDOneJason Levy replied 16 years, 11 months ago 6 Members · 9 Replies -
9 Replies
-
David Roth weiss
June 13, 2009 at 1:52 amHere’s my list if things to do in order of priority:
Trash Prefs
Fix permissions in Disk Utility
Run Disk Warrior on all drives especially your CalDigit HDOne (yes they recommend DW)
Use the Render Manager to delete all renders for the current project
If these don’t work, open a new project and move current timeline to the new project, try to render now.
If that doesn’t work, cut and paste everything from the present timeline into a new timeline in teh new project.
David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los AngelesPOST-PRODUCTION WITHOUT THE USUAL INSANITY ™
A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, and Indie Film & Documentary forums.
-
Aaron Neitz
June 13, 2009 at 2:01 amRendering the Motion Projects in FCP?
I had so many problems with that workflow, I would render out in Motion as a quicktime and bring it into FCP.
-
Scott Davis
June 13, 2009 at 2:18 am -
Scott Davis
June 13, 2009 at 2:34 am -
Alan Lacey
June 13, 2009 at 5:31 amLike Aaron, I’ve had endless problems leaving the motion projects on the timeline. I always render them separately now.
Alan
XDcamHD,XDcamEX,D9
FCS,AE,Combustion,LiquidSilver,Vegas
G5,MBP,XP -
Jason Levy
June 13, 2009 at 1:52 pmSounds to me like you are running out of memory. Try bringing just the one sequence in to a new project and open it fresh with no other project running, then render and see what happens. I assume you have ample memory in your system… (more then 4 gigs does not help though.)
Good luck.
jason
-
Scott Davis
June 13, 2009 at 2:48 pmHi Jason, I thought the same thing. I have 4G of RAM, and tried it with nothing running other than FCP. I can render hour long projects easily when there are no Motion projects in them. At this point I believe it is the Motion projects. In a 40 minute piece we have 100+ Motion projects. For the online I will render out and bring them in as QT. I don’t want to do that now as the editor might still be making changes as we wrap the rough.
-
Jaap Verdenius
June 13, 2009 at 9:15 pmHave you tried decreasing RAM allocation for FCP ? I know it sounds counterintuitive but I have always been wondering if Motion may be running in the background in these situations, desperate for memory
-
Jason Levy
June 14, 2009 at 12:59 amActually since final cut and motion have to run at the same time maybe more than 4 gigs would be helpful.. If you run Activity Monitor when you are trying to do this render how much free memory does is say you have available?
jason
Reply to this Discussion! Login or Sign Up