Quote:
|
Originally Posted by stickboy
If only AviSynth used doubles instead of floats, then it more easily could rationalize 23.976 to 2997/125.
|
I don't see how that would help...
Users generally mean 24000/1001 when they put 23.976 and not 2997/125.
Besides FPS is rational, not float or even double, every api with some sense use it like that.
VFW certainly does, avs should do the same (3.0 does)
Quote:
|
but then you still have the problem of educating people to use it
|
Easy : add overloaded *FPS functions and change all the old ones to throw a message reporting them deprecated and asking to use the new ones.