-
problems with 24fps frame display in Viewer
Hi all – has anyone run into a weird thing in the viewer where it displays onlyY 29.97fps timecode (as opposed to 23.98), and seems to do strange conversions if you change it to display frames? I am working on a 24fps project and whenever I open a clip or a piece of footage in the viewer, the timecode/frames display there is completely off. ie – the very first clip in my timeline is a quicktime file I rendered out of After Effects. In AE it is 284 frames long. When I import it into FCP, in the Browswer window it says the duration is 284 frames. When I double-click that clip (in the Browser window) and open it in the Viewer, it still gives the duration as 284 frames (in the little window at the top left of the Viewer window) but the frame count (at the top right) goes all the way to 354. If I enter frame 284, it brings me to a point about 80% of the way through the clip rather than to the last frame, as if it’s doing some weird conversion to 30fps before displaying those frames.
If I switch those boxes to display timecode instead of frames, I can go through frame-by-frame without anything that makes me think that some sort of pulldown is happening, but the current time box displays 30fps timecode! (Frames 00-29 instead of 00-23). And now the final frame is still wrong, but it’s only off by 4 frames (displaying 00:00:11;24 as the final frame instead of 00:00:11;19).
Have I got a setting wrong somewhere? Is this a PEBKAC error (Problem Exists Between Keyboard And Chair)? Or is it just one of those things that’s weird, and that’s that?
Thanks in advance for your help!
Steve -
4 Replies
-
Well, if that means right-clicking on the clip in the Browser, selecting, “Logging Info…” and changing the “TC Rate” option from 30 to 24 (which has solved my problem) then yes.
Bigger question though – why does FCP look at this 24fps file and assign it a TC Rate of 30? I checked all my output settings in AE and it all seems to be in order there, but I haven’t done that much work at 24fps so I could be wrong. AE output is more-or-less generic “Best Settings” (at 23.976fps) with output to QT ProRes4444.
Other clips in this same project, which are QT ProRes422(HQ) files converted from Targa sequences using QuickTime Pro, seem to have come in fine (and have no “TC Rate” assigned at all), but anything out of AE has the “TC Rate” set to 30fps.
Thanks for prodding me to look more closely at it!
-
No problem on the typing.
What I shot it on is irrelevant because I didn’t *shoot* any of it. The problem shots were rendered out of AE. The other shots (without problems) have been rendered out of a combination of 3DMax and Fusion then the Targa sequences compiled into .mov files using QuickTime Pro. All the .mov files are ProRes4444 in the case of the AE renders, and ProRes422(HQ) in the case of the 3D stuff.
There are some clips in this project that I did shoot using a Canon 5DMkII at 1080p24, and then ingested using the Log and Transfer window. I have not run into any problems with the shot clips – just the stuff out of AE.
Sorry if I wasn’t clear about this before.
Cheers,
Steve -
I am aware I must have the precise frame rate in AE.
Perhaps I’m not explaining the problem properly, Dave, and I appreciate your efforts but I’m still not getting an answer to my question. That is: somehow, FCP decided that the “TC Rate” on this file was “30” rather than “24” and I’m wondering if I did something to give it that idea, or if this is some default that I’ll just have to deal with when taking a file from AE into FCP. Or, is there something in my AE output settings that is writing metadata to the output file that tells FCP that the TC Rate should be set to 30?
I’ve been working with AE and FCP for 10 years, but have done very little work at 24fps until recently, and I’m just trying to figure out if this is a quirk, or something I did wrong in either creating or importing the .mov file.
I have solved the problem – I just want to make sure it doesn’t happen again.
-
Quite so!
QTX was once installed on my system but has long since been removed.
Reply to this Discussion! Login or Sign Up