It’s designed for people who find that a nanosecond is too short, but a microsecond is just too long. Facebook calls it a “flick,” and it’s one 705,600,000th of a second. The word “flick” is actually a contraction of “frame tick,” which offers clue about what a flick is and who really needs a new unit of time.

Well, Facebook, for one, needs it as part of its interest in virtual reality content produced for its Oculus VR division. Christopher Horvath raised the issue it resolves as a question posted to Facebook in 2017. (He now works for Facebook’s social virtual reality division.)

Christopher Horvath

Is this the face of a time lord? Well, yes. Here’s Horvath holding his Emmy for the Oculus film “Henry.” (FACEBOOK)

It’s all about, as Horvath explains on GitHub, the gnarly math often required in the production of film and video. As you know, both create the illusion of movement with a succession of still images, or “frames,” played back in rapid succession too fast for the eye and brain to process as separate stills. The number of frames per second is referred to as its “frame rate.”

horse-movement

(ABEADEV) via SHUTTERSTOCK

There is a dazzling array of different frame rates a person working in film or video may encounter. They range from the traditional movie-industry standard of 24 frames per second (fps), in which each frame lasts for 1/24th of a second, to digital video that supports high-resolution audio of 192 kHz and thus a frame length of just one 192,000th of a second.

The problem is, as Horvath explains, “When working creating visual effects for film, television, and other media, it is common to run simulations or other time-integrating processes which subdivide a single frame of time into a fixed, integer number of subdivisions. It is handy to be able to accumulate these subdivisions to create exact 1-frame and 1-second intervals, for a variety of reasons.”

Working with single frames has been a mathematical nightmare. A frame at 24 fps, for example, expressed in decimal form is roughly .04166666667 seconds, or 41666666.669 nanoseconds. And when you multiply or divide what are essentially estimates like these, your results inevitably become increasingly inaccurate. 

Horvath figured out that there’s a number that would allow content creators to work with full integers whose products wouldn’t degrade over successive operations, and that’s a 705,600,000th of a second, AKA the flick.

Using the flick, the math is so much tidier and simpler:

  • 1/24 fps frame: 29400000 flicks
  • 1/25 fps frame: 28224000 flicks
  • 1/30 fps frame: 23520000 flicks
  • 1/48 fps frame: 14700000 flicks
  • 1/50 fps frame: 14112000 flicks
  • 1/60 fps frame: 11760000 flicks
  • 1/90 fps frame: 7840000 flicks
  • 1/100 fps frame: 7056000 flicks
  • 1/120 fps frame: 5880000 flicks
  • 1/8000 fps frame: 88200 flicks
  • 1/16000 fps frame: 44100 flicks
  • 1/22050 fps frame: 32000 flicks
  • 1/24000 fps frame: 29400 flicks
  • 1/32000 fps frame: 22050 flicks
  • 1/44100 fps frame: 16000 flicks
  • 1/48000 fps frame: 14700 flicks
  • 1/88200 fps frame: 8000 flicks
  • 1/96000 fps frame: 7350 flicks
  • 1/192000 fps frame: 3675 flicks

All complete integers. Facebook agreed, and on January 22, Oculus VR announced the new unit on their Open Source page. Just in the flick of time, one might say.