1 person found this helpful
Read up on NTSC timecode handling and the AE help.
I read up on it and it was quite interesting, I am also guessing that if the box is greyed out, It will have a set 'stop ' or 'non-drop' if that makes sense!
Thank you for your help!
Almost ALWAYS, the following frame rates apply:
30 fps is really 29.97 fps
24 fps is really 23.976 fps
60 fps is really 59.94 fps
I's always good to work in Drop Frame. You get a far more accurate idea of the length of an edited piece. And it DOES NOT drop frames. That's an unfortunate and misleading name for what's happening. Drop frame merely adjusts the time code associated with the fractional frame rates above to accurately reflect time.
Ok cool, So I won't get frames dropping with 24 fps or an whole number?
You NEVER get dropped frames. Not ever.
In drop frame, it's the TIME CODE that behaves oddly.
Here's what I mean: You shoot two minutes of video in 29.97 drop frame. At almost a minute in, the time code reads 00:00:59:59. What's the time code on the next frame? You might think it would be 00:01:00:00. But it is NOT. It's 00:01:00:02. There are no missing frames in your video. But the time code takes a little jump.
Ok... So I am a little confused... Is it best to work in Non-Drop Frame or Drop Frame, because you mentioned that it is a good idea to work in drop frame 'I's always good to work in Drop Frame. You get a far more accurate idea of the length of an edited piece. And it DOES NOT drop frames.'
And why does it go up to 1.00.02 instead of 1.00.00 from 59.59? That confused me a little bit!
Drop Frame time code compensates for the slightly-longer frame of video when it's shot at 29.97 as opposed to 30fps.
If you have video shot at 200 fps, how long does each frame appear? 1/200 sec. At 100 fps each frame appears for 1/100 sec. At which rate do the frames appear longer? 100 fps. Makes sense.
At 30 fps the duration of a frame is 1/30 sec, and at 29.97 the duration is 1/29.97 sec. The difference in durations between these frame rates is miniscule. But that tiny difference adds up over time.
Tell you what -- Open Premiere Pro. Make a custom sequence. Make its frame rate 29.97. Make its Display Format 29.97 fps Drop-Frame Time code.
Then play with it. Observe what happens when you move the timeline cursor frame-by-frame to 1 minute. Or 2 minutes. Or ten minutes. Or an hour.
You'll get the idea.
And here's another way to think about it.
Let's say you shoot a little over an hour of video at 29.97, but you use Non-Drop-Frame time code. NDF is just a frame count, It doesn't take the slightly longer duration of a 29.97 frame into consideration.
Okay, now you have your hour and ten seconds of video or whatever. Make an in point at 00:00:00:00 and an out point at 01:00:00:00.
Put it in that custom Drop-Frame PP timeline you just made -- when you put the timeline cursor at the last frame of the clip, you'll see the timeline's time indicator reads one hour.... and EIGHT SECONDS! Why? Because the frames in 29.97 are slightly longer than they are at 30.... and that tiny difference adds up.
That's why Drop-Frame is good. It keeps you on time.
Ok thanks... I understand that now, but I don't see who 29/97fps is longer than 30?