-
Mixed Framerates?
Hey there,
I’ve got a bit of FCP weirdness I could use some help with. I’m cutting a reel of spots using mostly 10-Bit Uncompressed footage at 29.97 fps. However, a few of the spots were incorrectly handed-off to me as 10-Bit Uncompressed 23.98 fps. No biggie, right? In FCP 5.4 I just rendered it and moved on. Now that I just upgraded to FCP 6, I shouldn’t even have to render, right?
Here’s the weird part, though; quicktime believes these spots are 29.96 fps, according to the movie info, while Final Cut tells me there’s 23.98 in the item properties. And somehow, between QT and FCP, I’m getting weird results. Only about 80% of the spot will play back in the viewer. (It ends well before the client logo, which is not quite what we’re after.)
If I didn’t put an out-point on it, it was all there when I pasted it into the timeline in FCP 5.4. In FCP 6.0, however, I get spots that end 80% of the way through, even though they are 60 seconds in length. (The audio is completely out of synch by the end.)
I burned a DVD of one of the spots from the timeline, and it was all present on the DVD. (Presumably because compressor uses the original QT media, right?) But when I play the timeline, these spots all end about 80% of the way through.
Obviously FCP and QT are having a frame-rate disagreement. And ideas as to how I might correct this little oddity? Is this something super-simple? I did try creating a new sequence and having FCP 6 match the settings of the 23.98 clips, but I still don’t get to see the endings.
Thanks for your help. This minor headache has eaten up a fair chunk of my Friday afternoon so far.
Steve
-
1 Reply
-
So, oddly, this issue turned out to only exist on my edit station, the one we refer to as being “haunted” by the ghost of the previous editor. The other editor’s station played the spots back normally.
We did come up with a work-around, though, which was to take the spots into After Effects and re-export them from there, with a corrected frame rate. Then my machine played them normally. Just mentioning it, in case anybody has similar problems and needs a workaround.
Steve
Reply to this Discussion! Login or Sign Up