Hacker News Reader

I agree with your line of thinking, but since they give 1/30 fps frame as 23520000 flicks, I get 1 NTSC frame = 23520000 * (1001 / 1000) flicks = 23543520 flicks.

I was all set to file a doc PR but noticed you have to file a CLA. newp.

View on HN

It is worth noting that while you can represent single NTSC frame time exactly in Flicks, it still does not fulfill their goal of representing "also 1/1000 divisions of each" for NTSC. To get there you'd need 1 Flick to be 25 times smaller, i.e. 1/17640000000 seconds. Although this would go below 1 ns, which was also one of their constraints, but I'm not exactly sure what importance that really has.

Possibly range? At that scale the max representable duration is about 16.5 years (assuming they're 64 bits, IIUC the standard mandates that as a minimum) which could be limiting - although that seems unlikely to be a concern in the framerate domain, but who knows what it might get used for when that might become an issue.

CLA?

Usually: contributor license agreement.

newp?

Diminuitive of 'nope' :)

Ahh like this: https://goo.gl/images/eRKmN4

Thanks.

Reply on news.ycombinator.com