-
Huge rendering problems with ETT today
Ok, help… I’ve been using FCP for *years* and consider myself a very informed user…. but today….
I get a FCP project file from the offline editor. I Media Manager it and get a sequence for 8-bit UC conform.
Simple piece. 12 minutes. Cuts and dissolves. a couple Text’s for title.
1) Cross dissovles to black (or rather, to blank timeline) are NOT DISSOLVING. I have dim green RT – so basically full res RT. RT settings at High and Full. If I force render the dissolve still doesn’t work! ARGH! I ended up using additive dissolves in their place. Why is cross dissolve not working? I’m flummoxed.
2) the entire piece has a 1.78 widescreen filter on it. But again it’s dim green RT, and it looks perfectly fine for this project, so I am going to lay it off without rendering (I know you’re going to say: you should ALWAYS render no matter what. But we had a 4 hour turn around and it’s not a commercial for the new BMW…so…). I have it set to ETT with “playback settings”…. and it renders for 15 minutes before laying off. Huh? I’ve done this before and it would render for 30 seconds and then ETT no problems…. I can’t figure it out what in the hell it’s rendering. I DO have it set to Fields = none so that the edges are crisp. In Lower they have that half field mess on the edges.
3) there were a couple moving Text that I rendered. Looked beautiful when playing back. As soon as ETT I got those little pops and shifts you sometimes see with Preview quality RT.
It’s almost like FCP is assuming some other codec and sequence settings when it goes to ETT. Like I said, I’ve been doing this for years, it’s a simple 8bit UC sequence using Blackmagic hardware. Maybe I’m just being stupid and forgot something…. any suggestions would be great because I’m fuming mad at my Final Cut right now.
FCP 5.1.1
OS 10.4.7
QT 7.1.3
Dual 2.3 G5, 4 GIG RAM
Blackmagic HD+ with current drives -
5 Replies
-
Man, save yourself the hassle and render. Delete all the render files first, and then re-render. It’ll be much simpler in the end process, cutting corners now always bites you in the butt at the end, but you know that already.
And as far as rendering with no fields on, that could cause problems if your video is interlaced. If you are watching this on a tv there won’t be any ‘half field mess’, but you know that already.
Jeremy
-
So I force rendered the ENTIRE thing. 25 minutes. But still 8 minutes of “Writing Video” on ETT. So about half the wait.
WTF? I know it’s always been something FCP does, but it’s never taken so long on such a relatively short piece.
I did a quick forum search…. has anyone ever found an answer to what FCP is doing during this process? I can go sit at our Avid Media Composer, have a 12 minute piece at 1:1, and hit Digital Cut – and bam it goes straight to tape with no hesitation. It’s almost like FCP has to do a video mixdown it order to get accurate ETT?
Cross dissolves STILL don’t work right.
egghhhh… someday it’s a drag.
-
Well scribble my dribble…… I had the roughcut on V7, but the video track was turned off…. deleted V7 and suddenly ETT is back to speed. Some bad code I guess.
-
This bug has bitten me many time. Even though a clip, or clips in the timeline is turned off, when you go to ETT FCP thinks it has to render them. Very annoying. You just have to remeber to delete all clips that are turned off.
What really gets me boiling is when I go to render a timeline before outputting to tape and FCP tells me it’s going to be 20 minutes, when I know it should only take 2. I then quit FCP, restart the app and bam, only 2 minutes to render the same timeline. It would seem FCP has some kind of memory leak. I’ve had this issue going back as far as I can rememer. We’re on 5.1.2 now and the problem persists.
Michael Alberts
Ambidextrous Productions, Inc. -
I’ve gotten into the habit of doing this:
1) lock picture
2) FILE>EXPORT>QUICKTIME MOVIE>CURRENT SETTINGS (self-contained)…to get a single flattened Quicktime file for layback
3) create a new sequence and import this new file, then ETTSaving out the flattened file has always been quicker than waiting for the ETT render.
Reply to this Discussion! Login or Sign Up