-
FCP6 renders duplicate frames…
I seems to be running into too many errors with FCP 6 these last few days. I think we need to downgrade to 5 for the facility…
I have a sequence. DV50 @ 23.98fps. Each clip has a Widescreen filter. When I force render, or export a QT, some of the clips render what looks like 50% of the frames (as if you had you render settings to 50% sequence time).
I’ve tried everything under the sun, switched every preference in rendering that I can think of. No avail. Also moved the project to a G5 FCP system , same problem.
would love any help. Are you having all these issues with FCP 6? We JUST upgraded last week, it seems everyone has been using it happily for months and months.
-
9 Replies
-
How’d you capture the footage?
-
AJA Io. Captured via SDI to 23.98 DV50, no field dominance on clips or sequence.
However, the clip in question is a render from Combustion. DV50, 23.98, no fields.
However x2, I have a couple other clips in the same sequence rendered from the same Combustion workstation with the same EXACT settings, and they render fine. (It’s been a solid workflow for us since FCP 4. that’s why I’m freaking out now)
I’ve exported an XML and rendered in FCP 5.1.4. No problems there.
Thanks Jeremy for helping me out. I feel like the computer is conspiring against me this week.
-
[CharlieX] “I feel like the computer is conspiring against me this week. “
Always does with new software and updates. Fun will ensue (or enrage).
So only that one clip is giving you trouble? The other clips which have the same parameters (dv50, 23.98) and work fine?
-
15 clips in the commerical.
8 clips are from Combustion.
6 of those render correctly.
2 of them don’t.I have 3 other commercials for the same product. Roughly equal amounts of Combustion renders –> roughly equal amounts of bad renders. I can’t find a pattern. Some widescreen filters have an offset, some don’t, but changing it doesn’t make a different.
I’d be happy to post one of these clips on our website.
-
[CharlieX] “I’d be happy to post one of these clips on our website. “
Oh yeah, send it along.
-
https://www.kingcut.com/ch/309_comp3.mov
about 21MB. Plop it onto a timeline, add Widescreen, watch badness ensue!
-
Hi Charlie,
Sorry to come late to the party on this one. I got the same stuttering that you seemed to be having. Then I opened it up in Cinema Tools and conformed it to 23.98. It briefly flashed offline in FCP and then reconnected and now it renders fine. I’ve sometimes seen Quicktime movies improperly tag their internal timebase, particularly when they render out of a third-party app. I think this is the problem that you’re having. For example, I’ve done a little bit of Javascript programming for Quicktime and if I render a 24p file, it sometimes tells me that the timebase is 29.97 (even if Quicktime’s “get info” tells me that the frame rate is 23.98). This is speculation, but I think conforming it to 23.98 in Cinema Tools, in a case like that, basically just resets the tag inside the file so that everything is on the same page.
Hope that helps,
– David -
What do you mean Charlie, it looks awesome over here!
Just kidding!
That looks light shite. David’s fix did work. That is some good sleuthing, thanks David!
Jeremy
-
Yes, thanks a billion David! I did try rendering 23.98 and 23.976 out of Combustion, to see if that made a difference, but it didn’t. Cinema tools never occurred to me.
I hope Apple knows about these little things. It’s the obscure stumbling blocks that often cause the most consternation.
Reply to this Discussion! Login or Sign Up