Using AsObjC for manipulating 64-bit ints, is nothing I have done, nor know how to do. What you write is both interesting, and discomforting, because then AppleScript, “vanilla AppleScript” anyway, can’t be used to perform the calculation. I was just about to perform the ratio-test. Note that last sentence about rounding, and remember that AS doesn’t do 64-bit ints. Using a flag CMTime indicates whether the time been rounded at some point. In addition to a simple time value, a CMTime can represent non-numeric values: +infinity, -infinity, and indefinite. Thus if the timescale is 4, each unit represents a quarter of a second if the timescale is 10, each unit represents a tenth of a second, and so on. Conceptually, the timescale specifies the fraction of a second each unit in the numerator occupies. The frames to time calculator determine the time in seconds by dividing the number of frames by 24. I think what’s being used is a CMTime struct, about which the docs say:Ī CMTime is represented as a rational number, with a numerator (an int64_t value), and a denominator (an int32_t timescale). Depending on the use case, users may define the duration scope. To utilize this tool, first select the appropriate fps, followed by entering the 'Start' and 'End' timecodes. The timecodes it processes must have the same frame rate per second (fps). I suspect it is, though: 41889.04 * 1200 / 50317267 = 0.998997978169. TC Duration is an online tool designed to calculate the duration between two timecodes. The thing is, is that 41889,04*1200 is not the number mentioned, so it is just not about expanding the number by 1200.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |