Hey Folks –
Okay, thank you for all the responses, I appreciate it very much. I thought I made it pretty clear in my post that I understand that 23.976 is actually a ratio (24/1.001):
[James Heliker] “23.976 (more accurately 24/1.001, or 23.97602397602398)
120.1201201201201 x 23.97602397602398 = 2880.00288000288
This is great! Exactly as expected.”
I also thought it was obvious in my original post that I understood that 23.976fps was not equal to real time:
[James Heliker] “Now, I exported a file from this sequence with an actual timecode track, (ProRes 422 HQ Quicktime file), running @ 23.976fps, comes out with a duration of 2880000mu /23976ts (120.1201201201201 seconds).”
Where things start to go gray for me is why 23.976 exists – I’ve been told that 23.976 exists so that there can be an easy math conversion to NTSC for monitors, broadcasting, etc. That makes sense as 23.976 converts to 29.97 (30/1.001!) mathematically (every fourth frame), whereas 24 does not.
If this is the case, I’m left with why we don’t use 23.976 timecode with 23.976 material?
My original two questions are this:
[James Heliker] “However, why is my timecode running at 24fps on a 23.976fps video file? In true 23.976fps math, my final frame (2879) should be at TC marker 00:02:00:03.
1. I was under the impression that 23.976fps video should be accompanied by 23.976fps timecode??
2. Why can’t I set the TCG to run at 23.976fps? What am I missing here?”
Please correct me if I am wrong, but it appears the answer to both of my questions is that 24 frame timecode is the industry standard, even for 23.976 fps material. ie. the TC addresses are simply sliding over time to account to for the difference in speed?
Thank you for your help!
Kind Regards,
-James Heliker
james.heliker@gmail.com