Earlier quoted context omitted.
CLA?
Usually: contributor license agreement.
newp?
Flicks – A unit of time defined in C++
41–50 of 55 posts
Re: Flicks – A unit of time defined in C++
#42Its always amazing to realize how big 2^64 really is. 2^32 Flicks is about 6 seconds (which can be enough, but still not that useful), but 2^64 is over 800 years, which should be quite enough for anything needing this sort of precision. It would be actually pretty nifty to have this in eg. `struct timespec` and overall base rtc around Flicks
> It would be actually pretty nifty to have this in eg. `struct timespec` and overall base rtc around Flicks I disagree. We already have enough confusion with time and another unit at the level of timespec is not helpful IMHO. The SI unit of time is the second and 1/sec is Hz, which are used everywhere in science and engineering. I don't want another non-SI time unit getting thrown around and messed up in calculation…
> There is already enough confusion if someone is in TAI,
> GPS, or UTC time
Re: Flicks – A unit of time defined in C++
#43Re: Flicks – A unit of time defined in C++
#44This reminds me of how MIDI files [0] represent time offsets, in integral "delta-time" units which can be set to either an arbitrary unit fraction of a quarter note, or an arbitrary unit fraction of an SMPTE frame (which itself can be specified in frames per second). Combined with an ability to dynamically set tempo (at any delta-time offset) in microseconds per quarter note, this allows practically any (Western) mus…
you could just break out a calculator
Hold on while I break out a calculator to operate my computer. As a former sound engineer I have to tell you nobody liked Logic, they tolerated it as the affordable alternative to Pro Tools until other tools came along. People appreciated its reliability and depth but not the UX.
Re: Flicks – A unit of time defined in C++
#45Re: Flicks – A unit of time defined in C++
#46Re: Flicks – A unit of time defined in C++
#47This reminds me of how MIDI files [0] represent time offsets, in integral "delta-time" units which can be set to either an arbitrary unit fraction of a quarter note, or an arbitrary unit fraction of an SMPTE frame (which itself can be specified in frames per second). Combined with an ability to dynamically set tempo (at any delta-time offset) in microseconds per quarter note, this allows practically any (Western) mus…
you could just break out a calculator Hold on while I break out a calculator to operate my computer. As a former sound engineer I have to tell you nobody liked Logic, they tolerated it as the affordable alternative to Pro Tools until other tools came along. People appreciated its reliability and depth but not the UX.
Never claimed Logic had anything more than a tolerable UX - just that it got the job done! As someone approaching it not as a sound engineer (for which Pro Tools was/is the gold standard for a reason!) but as an amateur composer wanting to actually have a modicum of control over both notation and the sound of my demos, Logic straddled both worlds in a way that nothing else really did - certainly Pro Tools barely even touched notation.
Though maybe I was just too stubborn to re-input things in different software for each purpose. Needless to say, on the coding side, I was very excited when Node.js was first released!
Re: Flicks – A unit of time defined in C++
#48Earlier quoted context omitted.
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.
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.
Re: Flicks – A unit of time defined in C++
#49Can you "invent" a definition?
Most freshman undergraduate mathematicians have had their fair share debating whether you "invent" or "discover" definitions and proofs. The general consensus is that you "discover" things that are very natural, and you "invent" things for which different mathematicians would have perhaps come up different ideas. But only one thing is shared between both sides of the debate: the distinction really doesn't matter and…
According to half the linguists, both might be right, just a figure of speech, while the other half would help them find the right word.
Re: Flicks – A unit of time defined in C++
#50To solve a similar problem FFMpeg uses fractions. So the unit of time is defined by two numbers, time_base.num and time_base.den.