Activity › Forums › Apple Final Cut Pro Legacy › Under deadline. Weird Render issues!
-
Under deadline. Weird Render issues!
Posted by Max Frank on June 6, 2008 at 11:33 amHi,
I’m working on a feature-length documentary – DV NTSC codec.
Lately my renders have been getting messed up – either the screen goes black, or strobes red and pink and other colors, etc etc etc.
This doesn’t happen to all renders, though – just some.
I’ve tried trashing the prefs, to no avail.
Any ideas?
FCP 6.0.3
MBP 2.4 Duo
OS X 10.5.2Thanks,
Wayne
Max Frank replied 18 years, 3 months ago 6 Members · 8 Replies -
8 Replies
-
Steve Eisen
June 6, 2008 at 12:42 pmTrash all your render files and re render. There is a render manager in FCP.
Steve Eisen
Eisen Video Productions
Board of Directors
Chicago Final Cut Pro Users Group -
Max Frank
June 6, 2008 at 2:20 pmHi Steve,
Thanks for the feedback.
Rerending this project is going to take hours and hours and hours because it is so big and complex.
So, before I do, I wanted to just be sure that it is the right thing to do. Basically, I just wanted to understand, from a technical perspective, how redoing ALL the renders will solve the issues.
Thanks in advance,
Wayne
-
Jeremy Garchow
June 6, 2008 at 2:32 pmDue to FCPs less than stellar media management/tracking, render files can sometimes get confused as the render files are named after the sequence.
Deleting those render files breaks any weird links to extraneous render files and re-rendering creates all new ones. If you are having trouble rendering, it’s the best thing to do.
Jeremy
-
David Bogie
June 6, 2008 at 3:05 pmCan you not right-click on a bad section and “remove attributes” to force a fresh render?
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
Jeremy Garchow
June 6, 2008 at 3:18 pm[david bogie] “Can you not right-click on a bad section and “remove attributes” to force a fresh render? “
Yes, you can. There’s many things you can do to force a fresh render (the easiest is to select the clip and toggle control-b), but the point is that since FCP names it’s render files after the sequence name, it can sometimes get confused especially if you have had a sequence name duplicated at some point in time in the project (for instance you can have two or more “Sequence 1″s in any project), or copying and pasting since the sequence name can now be different than the render file.
If the project is long and versioned, it’s bets to clear them all out and start anew…
-
Arnie Schlissel
June 6, 2008 at 6:05 pm[Wayne Marx] “Rerending this project is going to take hours and hours and hours because it is so big and complex.”
Start the render as you’re leaving for the night.
[Wayne Marx] “I just wanted to understand, from a technical perspective, how redoing ALL the renders will solve the issues. “
While there’s no guarantee that it will solve the problem, it usually solves these kind of problems, it’s relatively easy to do, and it won’t hurt anything.
Arnie
Post production is not an afterthought!
https://www.arniepix.com/ -
Colin Mcquillan
June 6, 2008 at 6:38 pmIf trashing/ re-rendering doesn’t work, take a look at the plug-ins you have on the clips.
I’ve seen some plugs that will cause interlace bleeding through to lower clips when stacked, some that cause field shifts, and others that give back funky color shifts and such when used in combination with other plugs, render settings, codecs…..
Let us know if the re-render doesn’t work, and what plugs you are using on the clips.
Make sure you have the latest versions of the plus-ins you are using.Colin McQuillan
Van BC
Octo 3.2, 8gig, 8800GT, 2×23″ ACD, 2TB G-Speed eS, Kona LHe, JVC DT-V24L1UA, Mackie 1202-VLZ3, KRK Rokit5’s….
MBP 2.4, 4gig , 2xLacie Quadra 500gig…. -
Max Frank
June 7, 2008 at 7:46 pmThanks all for replying and for the explanations.
I’ll heed the advice and let you know what transpires.
Wayne
Reply to this Discussion! Login or Sign Up