![]() ![]() ![]() Thanks hello_hello for running the numbers. ![]() However, 00:13:54:04 coming out as "drop-frame" timecode adds to my confusion, TBH. Is the "drop-frame" timecode the same as "Human time" then (other than the last frames are written in frames in stead of milliseconds)? It's 13 minutes, 54 seconds, plus four more frames.Ī colon means frame numbers at the end. ie 13:54:04Īt the 20,000 frame mark, SMPTE would be about 0.2ms off. NTSC doesn't display a whole number of frames each second, so you can't count the frame numbers after "seconds" and have them "line up" for want of a better description. Back when the frame rate was 30fps there was, naturally, a whole number of frames every second, but after the change to 29.97fps, the solution was to ignore the frame rate difference and keep counting at 30fps (or 24fps as the case may be). To keep it accurate in relation to human-time, SMPTE drop frame timecode counts frames at 30/24fps most of the time, but every now and then it only counts 29 or 23 frames in a second. It's not frames being dropped though, it's their timecodes. It's people-time, but counting at the same incorrect rate as the non drop frame timecode immediately above it (24fps).Īnd I'm already confusing myself thinking about this. Non drop frame SMPTE timecode counts all the frames and slowly goes out of sync with people-time because it's counting them at a slightly incorrect rate (assuming it's 23.976 or 29.97fps). I am one of the developers who wrote TcCalc. Darren Blackham alerted me to this thread and I though I would chime in. NDF - use every frame (would be accurate if 29.97 was 30, but isn't at 29.97)ĭF - approximate the actual rate (30/1.001) by dropping 2 frames every minute, except the 10s For basic frame rates like 29.97 DF/NDF, 25 and 24, there were known rules everyone followed that made things very clear:Ģ4/Film - use every frame, always 24 a secondĢ5/PAL - use every frame, always 25 a second TcCalc was designed to be broadcast video calculator that work, at it's base, in frames. It was originally a great compromise for film vs NTSC TV production. You could use simple 2/3 drop/add methods to convert between the two, and the hours. All you had to do was essentially a 24 Drop Frame calculation, and everything would work out. Unfortunately, when Sony released the first 1080p/23.98 cameras, they decided to use 24 fps timecode. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |