Animation times are stored internally as 1/4800 of a second.  If you are
making animations long enough for scaling of normal frame rates to make
a difference, you really ought to consider chopping up into smaller
pieces.

No times are ever stored as frames - frames are always stored as time.

The choice of 1/4800 is actually taken from Max, and is a sensible one. 
Almost all of the normal FPS values divide out evenly, resulting in not
precision loss as you change.

If you scale time by something other than just changing FPS, you will
have some loss of precision.  But with more than four digits of
precision per second, it will be pretty small (for a normal length
animation).

Xander

Alex Wolff wrote:
> 
> hi rick,
> i think, you missunderstood me:
> i don't want to type in mathematical functions in moray. if you want to
> do this, you really better do it in pov.
> i don't want xanders plugin to write out one pov-file with all
> animation-infos.
> what i want is: going away from quantizing the animation-time
> check this problem to understand what i mean:
> you are doing an animation of a creature who is walking three steps
> forward.
> beginning with a 100-frame-animation you set the keys at frame nr. 0,
> 33, 67 and 100.
> you see: the positions of the second and the third frame are a little
> bit wrong (the exact positions are 33.333333.. and 66.666666..). with a
> 100-frame-animation, these errors are small and do not matter much. But
> if you scale your animation-time later, these errrors are scaled, too.
> and they do matter...
> 
> alex

Post a reply to this message