How does nums dems works and affect on performance?

So, no difference in performance (only nanodifference) , only for nanoseconds?

Performance? AFAIK the SVP project create new interpolated frames and increase the fps, to obtain the same time when play (smoothly) and preserve the sync with audio. You must preserve exactly constant the NumFrames/FPS to avoid async, it is not related with performance.

When it comes to dividing one number by another, the size of the numbers makes no difference to the computer. It will take slightly longer to read and parse a longer decimal number, but when I say slightly I mean millionths, maybe even billionths, of a second. And it only has to do that part once.

maybe not, cause in potplayer I did not get any frac, so 1000/1001 is equal as num 999001 den 1000000 zero=float(1000)/float(1001) whoareyou=zero*10000000 debug==1? eval(""" Subtitle( \ "fps="+String(whoareyou)+"\n" + \ ""+super_params+"\n" + \ ""+part1+"\n" + \ ""+part2+"\n" + \ "Source Aspect="+String(SourceAspect)+"\n" + \ ""+resize_string+"\n" + \ ""+smoothfps_params+"\n" + \ "Threads:"+String(threads)+"\n" + \ "Info:"+String(info)+"\n" + \ "PPcheck:"+String(PPcheck)+"\n", \ font="Comic Sans MS", size=40*width/1920, lsp=10) """) : ("")

2997 / 125 is exactly same as 23976 / 1000 Float(2997*8) / (125*8) You can play with below Code:

I guess the frame rate shown by Info() is rounded to 4 decimal places. Which is probably fair enough. The docs do say "framerate" is approximate. Edit 1: There's always one mistake to fix..... Edit 2: It seemed remiss not to make the clips 24 hours long to see how far Avisynth says they would have drifted apart. Code: