Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Flicks – A unit of time defined in C++

github.com

Post reply on HN
Print view View original

51–55 of 55 posts

Re: Flicks – A unit of time defined in C++

#51

Post by jcelerier »

vortico wrote: post #18
mshook wrote: post #11

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

>humans can't hear higher than 48kHz Well, it's a true statement! (But yes, I agree)

Actually not that true, there were some experiments in the 50s that shown that through bone conduction a human could hear up to 100khz. Likewise, babies hear much higher frequencies than the "common" 20khz.

sources:

* https://www.ncbi.nlm.nih.gov/pubmed/10848570

* https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5285336/

* http://asa.scitation.org/doi/full/10.1121/1.2761883

Re: Flicks – A unit of time defined in C++

#52

Post by clord »

morio wrote: post #20

Failure to handle NTSC frame rates is exactly why no one uses a time definition like this. ISO/MP4 gets it right: Using a time scale with sample durations. If you work with tracks or files with different time scales you just use the smallest common multiple of those to become your working time scale. Works every time, even for NTSC frame rates. For instance for a file with 48Khz sound and 30000/1001 (29.97...) frame…

I agree with you but what you describe is exactly what a flick is, except with more stuff thrown in.

Re: Flicks – A unit of time defined in C++

#53

Post by robotresearcher »

lomnakkus wrote: post #17
robotresearcher wrote: post #15

Earlier quoted context omitted.

> Who cares, the point is they own it. The header file they provided is BSD licensed. You can use it freely, forever, for anything you want.

IIRC the BSD license doesn't say anything about trademarks or patents? (EDIT: Obviously, this doesn't invalidate your conclusion, but your conclusion doesn't follow from the premise, at least.)

It does not. But did you hear anything about patent or trademark protection sought by Facebook for flicks? Does releasing a BSD licensed implementation suggest to you that they intend to protect flicks this way?

I don't love Facebook's products, but I struggle to see the downside in them publishing this idea.

Re: Flicks – A unit of time defined in C++

#54

Post by dahart »

everdev wrote: post #2

Can you "invent" a definition?

All definitions were invented. What alternatives are you suggesting exist?

It is fascinating to dig into definitions and conventions that we know, and to realize that much of what we think of as universal fact is actually an arbitrary choice of history, canonized by time.

It happens often in math that people decide on arbitrary definitions. One fun example is Donald Knuth was fond of defining 0^0 = 1, while some other mathematicians prefer to define 0^0 = 0.

Post reply on HN