Activity › Forums › Apple Final Cut Pro Legacy › ProGraphics Plugin Crashing on Render, Export
-
ProGraphics Plugin Crashing on Render, Export
Posted by Ace Baker on July 29, 2009 at 8:58 pmI’m trying to render my timeline and export a quicktime in ProRes (HQ). Trying either one causes a crash, FCP quits with a message that it might be related to ProGraphics plug in.
Any help is greatly appreciated. Thanks.
Seems Matt Code is having the same trouble.
Kevin Clark replied 16 years, 8 months ago 3 Members · 7 Replies -
7 Replies
-
Ace Baker
July 30, 2009 at 3:00 amNobody responded to Matt either.
I wonder it it’s only on ProRes(HQ).
-
Alex Bluffield
August 20, 2009 at 1:02 pmHi guys,
It’s not only ProresHQ as I experienced this crash today whilst trying to render a Motion file on my timeline in XDCAM HD. It was a big Motion file with embedded video, graphics etc about 30 seconds long. I rendered less complex motion files fine, but this one kept crashing with the ProGraphics Plugin Crash message. I’m working on an iMac, 2.66 GHz, OS 10.5.6, 4GB RAM NVIDIA GeForce 9400 graphics card. Perhaps it’s an iMac specific issue related to the graphics card?? I exported my file as a MOV from Motion and re-imported back into FCP – that solved my problem. Is it Motion files you were trying to render or a whole load of stuff?
Best,
Alex.
Alex Bluffield
Final Cut Pro Editor
W: https://www.a2bpostproduction.co.uk -
Ace Baker
August 20, 2009 at 1:59 pmI had several Motion files on the FCP timeline, along with regular clips. Yes, the problem seems to be related to trying to render Motion files from FCP.
I found the same solution as you, render quicktimes from Motion and use those on the FCP timeline. Except you’re not supposed to have to do that. Oh well.
-
Alex Bluffield
August 20, 2009 at 3:49 pmThat’s interesting Ace. Possibly we’ve tried pushing the iMac’s gfx card beyond it’s capabilities. I don’t know enough about the various gfx cards in the different Mac models, only that the Pro models have better ones.
Exporting your Motion file as a MOV is the doing the same thing as what FCP does when it renders it on the timeline. With the benefit that you can watch it in real time immediately when it import it into fcp. We still haven’t got a definitive answer on the crash though, have we!! Apple!
best,
Alex
Alex Bluffield
Final Cut Pro Editor
W: https://www.a2bpostproduction.co.uk -
Kevin Clark
September 12, 2009 at 1:39 pmI’ve been receiving this same error. I designed a template in Motion and am using it in FCP. The first show i did with this template rendered to H.264 ok, but the second one has crashed 4 times, and these are long renders (6-8 hours.) And of course it waits until the very end of the render to crash.
MacBook Pro 2.16 GHz Intel Core Duo
1 GB 667 MHz DDR2 SDRAM
FCP 6.06
Motion 3.02 -
Alex Bluffield
September 18, 2009 at 8:38 pmWhat machine are you on Kevin?
Alex Bluffield
Final Cut Pro Editor
W: https://www.a2bpostproduction.co.uk -
Kevin Clark
September 18, 2009 at 8:47 pmhey alex… i’m on a macbook pro… but i figured out a work around to fix the problem… glad you responded to my post because i forgot to post the solution here.
the first time i rendered to a H.264 file, i had already rendered the timeline within FCP and the H.264 render went through. the second time, i figured i’d skip that step (rendering the timeline) and go straight to rendering the H.264. that was the problem, once i let the timeline render in FCP, i was able to make the H.264.
thanks
kevin
Reply to this Discussion! Login or Sign Up