Flicks

Reminds me of Facebook's Flicks, which are a super short tiny common denominator time unit: > A flick (frame-tick) is a very small unit of time. It is 1/705600000 of a second, exactly. > 1 flick = 1/705600000 second This unit of time is the smallest time unit which is LARGER than a nanosecond, and can in integer quantities exactly represent a single frame duration for 24 Hz, 25 Hz, 30 Hz, 48 Hz, 50 Hz, 60 Hz, 90 Hz, 100 Hz, 120 Hz, and also 1/1000 divisions of each, as well as a single sample duration for 8 kHz, 16 kHz, 22.05 kHz, 24 kHz, 32 kHz, 44.1 kHz, 48 kHz, 88.2 kHz, 96 kHz, and 192kHz, as well as the NTSC frame durations for 24 * (1000/1001) Hz, 30 * (1000/1001) Hz, 60 * (1000/1001) Hz, and 120 * (1000/1001) Hz. Guess the project got archived. Seemed like a semi sensible high res time format that was very media friendly. https://g

alas facebook archived their "flick" time unit, which promised to unify this all. ;) 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

Do you mean the facebook/oculus flicks? Wonder why the repo is archived... https://github.com/facebookarchive/Flicks ninjaed :(

Looks like it's archived? https://github.com/facebookarchive/Flicks via https://gizmodo.com/facebook-invented-a-new-unit-of-time-182...

"A flick (frame-tick) is a very small unit of time. It is 1/705600000 of a second, exactly. 1 flick = 1/705600000 second This unit of time is the smallest time unit which is LARGER than a nanosecond, and can in integer quantities exactly represent a single frame duration for 24 Hz, 25 Hz, 30 Hz, 48 Hz, 50 Hz, 60 Hz, 90 Hz, 100 Hz, 120 Hz, and also 1/1000 divisions of each, as well as a single sample duration for 8 kHz, 16 kHz, 22.05 kHz, 24 kHz, 32 kHz, 44.1 kHz, 48 kHz, 88.2 kHz, 96 kHz, and 192kHz, as well as the NTSC frame durations for 24 (1000/1001) Hz, 30 * (1000/1001) Hz, 60 * (1000/1001) Hz, and 120 * (1000/1001) Hz.* That above was one hell of a run-on sentence, but it's strictly and completely correct in its description of the unit. This makes flicks suitable for use via std::chrono::duration and std::ratio for doing timing wor

While humans can't hear higher than 48kHz, the higher sample rates are used for working audio files which might later be resampled or retimed. 48 kHz? Someone probably got confused between Nyquist–Shannon sampling theorem and the human ear... And someone beat me to it hehe https://github.com/OculusVR/Flicks/issues/2