Quote:
Originally Posted by rainspell
Thanks for the clarification about 23.976 and 23.98. After some more investigating - I found that the I was looking at the real time counter - ugh. After I loaded the actual frame counter into the transport it worked. And it would stand to reason that the real time does drift based on that frame rate. Good safety tip - and sorry for not noticing before.
It seems that the only way to set the sequence start time is in real time(?) which is a little challenging for time code/post production video users. Hopefully added in a future update?
Thanks!
|
As long as the main time unit is set to 23.976 then the offset will be in that format. The drift happens because 23.976 is what is known as a magic frame rate. These rates, 29.97, 23.976 etc. count back at 1.001 seconds for every real second. The names describe how many frames transpire in an actual second. They still count up 30 and 24 frames respectively, just over a longer period of time.