x264 r1391 changed avs info

[prOnorama]

r1376 (input .avs)

avs [info]: 1280x720 @ 23.98 fps (187966 frames)

r1391 (input .avs)

avs [info]: 1280x720p 0:0 @ 2500000/104271 fps (cfr)

I guess 2500000/104271 is about 23.976 FPS, and cfr stands for constant frame rate but what does 0:0 stand for?

(PS: The first thing I thought when I saw that "250000/104271" was: that looks weird, is x264 changing my avs input? I guess it's not the case)

[Dark Shikari]

Avisynth is likely reporting a very slightly wrong framerate to x264; and now you know that it is ;)

0:0 is the reported SAR (i.e. none).

[kemuri-_9]

yes, i unified all the info reports from all the input demuxers.


avs [info]: 1280x720p 0:0 @ 2500000/104271 fps (cfr)


the break down is:
width
height
interlaced (i)/progressive(p)
sar width
sar height
fps numerator
fps denominator
constant/variable frame rate

some source filters I've seen give weird FPS rates are DirectShowSource (likely DSS2 as well) and FFVideoSource

[prOnorama]

Avisynth is likely reporting a very slightly wrong framerate to x264; and now you know that it is ;)



some source filters I've seen give weird FPS rates are DirectShowSource (likely DSS2 as well) and FFVideoSource

Aha, yes I've been using DirectShowSource. (DirectShowSource("C:\x\x.grf",audio=false,fps=23.976)

If I pipe the source .m2ts file directly to x264 (r1391), I get a slightly different # of frames: 187968

ffms [info]: 1920x1080p 1:1 @ 45000/1877 fps (vfr)
[0.7%] 1350/187968 frames...

And now it uses vfr :confused:

If I use FFmpegSource2("C:\x\xxxxx.m2ts") in .avs it's 187966 frames again.

So I'm a bit confused now about using AviSynth, if piping straight to x264 (FFMS) will give accurate framerate. But I use AviSynth for cropping/resizing, don't know how to do that with x264 (FFMS). Or maybe I'm seeing it wrong and the 2 frames difference is not noticable in practice (probably isn't).