You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Drop Frame Timecode is a method that blender and all video editors use to automatically skip a timecode entry, at an appropriate time, when using non-integer framerates like 23.98, 29.97, or 59.94. They do this by dropping a timecode at certain intervals so the video will display the correct ending time and frame number when using those framerates.
That's right, this has no effect on integer framerates like 24, 25, 30, or 60.
You can see for yourself if you set milliseconds_to_frames = True option in this script, and you are rendering using one of the aforementioned, non-integer, framerates. the frame number timestamps will fall out of sync with the Timecode in the blender Timeline at the moment that blender decides to skip a timecode entry.
The text was updated successfully, but these errors were encountered:
mikeycal
changed the title
Drop Frame Timecode is not yet supported... Help?
Drop Frame issue when rendering 23.98, 29.97 and 59.94 fps video
May 18, 2017
#Read this, if you have no idea what I'm talking about but would like to look into it:
https://en.wikipedia.org/wiki/SMPTE_timecode#Drop_frame_timecode
Drop Frame Timecode is a method that blender and all video editors use to automatically skip a timecode entry, at an appropriate time, when using non-integer framerates like 23.98, 29.97, or 59.94. They do this by dropping a timecode at certain intervals so the video will display the correct ending time and frame number when using those framerates.
That's right, this has no effect on integer framerates like 24, 25, 30, or 60.
You can see for yourself if you set milliseconds_to_frames = True option in this script, and you are rendering using one of the aforementioned, non-integer, framerates. the frame number timestamps will fall out of sync with the Timecode in the blender Timeline at the moment that blender decides to skip a timecode entry.
The text was updated successfully, but these errors were encountered: