[x265] My bug reports for rev. ~400-450

Mario *LigH* Rohkrämer contact at ligh.de
Tue Oct 22 10:37:15 CEST 2013


Am 22.10.2013, 09:02 Uhr, schrieb Mario *LigH* Rohkrämer <contact at ligh.de>:

> One more bug: Although the video was set to exactly 24.0 fps, x265  
> reports "23Hz":
>  +----
> y4m  [info]: 640x272 23Hz, frames 0 - 1252 of 1253
> +----

Well, the reason here is a little strange.

The file "sintel_trailer_360.y4m" contains the following header:

+----
YUV4MPEG2 W640 H272 F72070:3003 Ip A0:0
+----

which results in a framerate of 72070/3003 ~ 23.999333 fps, whereas the  
file "sintel_trailer_1080.y4m" contains the following header:

+----
YUV4MPEG2 W1920 H1080 F24:1 Ip A0:0 C420mpeg2 XYSCSS=420MPEG2
+----

I believe the tool avs2yuv will have its reasons to use such different  
headers, maybe the AviSynth script returned inexact values. I'll try to  
rebuild the Y4M with forced 24.0 fps.

So the only small piece to nitpick is that x265 truncates to the next  
lower integer framerate, instead of reporting a useful decimal resolution.

-- 
__________

Fun and success!
Mario *LigH* Rohkrämer
mailto:contact at ligh.de
 


More information about the x265-devel mailing list