4 ms·
alas facebook archived their "flick" time unit, which promised to unify this all. ;) https://github.com/facebookarchive/Flicks https://github.com/facebookarchiv
by rektide 5y ago
alas facebook archived their "flick" time unit, which promised to unify this all. ;) https://github.com/facebookarchive/Flicks https://github.com/facebookarchive/Flicks
even this was an appropximation though:
> NTSC IS NOT EXPLICITLY SUPPORTED IN ALL OF ITS SUBTLE NUANCES, BUT: The NTSC variations (~23.976, ~29.97, etc) are approximately defined as 24 1000/1001 and 30 * 1000/1001, etc. These can be represented exactly in flicks, but 1/1000 divisions are not available.*
> Many folks online have pointed out that NTSC technically has a variable frame rate, and that this is handled correctly in other media playback libraries such as QuickTime. The goal of flicks is to provide a simple, convenient std::chrono::duration to work with when writing code that works with simulation and time in media, but not explicitly to handle complex variable-rate playback scenarios. So we'll stick with the 1000/1001 approximations, and leave it at that!