2014-12-21, 15:34
Hmm, interesting. Taking a screenshot of a 1920x800 file being played, it's actually occupying 1920x808? Thus why the doubled lines every 100 pixels in Nearest Neighbor? Properties in debug log show:
07:37:26 T:140159228024576 INFO: ffmpeg[7F795CFF9700]: Stream #0:0(eng): Video: h264 (High), yuv420p, 1920x800, SAR 1:1 DAR 12:5, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)
07:37:32 T:140158590506752 NOTICE: fps: 23.976024, pwidth: 1920, pheight: 800, dwidth: 1920, dheight: 800
07:37:32 T:140158590506752 DEBUG: OutputPicture - change configuration. 1920x800. framerate: 23.98. format: VAAPI_NV12
07:37:32 T:140158590506752 NOTICE: Display resolution ADJUST : HDMI1: 1920x1080 @ 23.98Hz (22) (weight: 0.000)
And yet a screen capture clearly shows the viewable window as 808 pixels high:
http://i59.tinypic.com/20i6hl5.png
That seems way too much to account for the PAR error.
07:37:26 T:140159228024576 INFO: ffmpeg[7F795CFF9700]: Stream #0:0(eng): Video: h264 (High), yuv420p, 1920x800, SAR 1:1 DAR 12:5, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)
07:37:32 T:140158590506752 NOTICE: fps: 23.976024, pwidth: 1920, pheight: 800, dwidth: 1920, dheight: 800
07:37:32 T:140158590506752 DEBUG: OutputPicture - change configuration. 1920x800. framerate: 23.98. format: VAAPI_NV12
07:37:32 T:140158590506752 NOTICE: Display resolution ADJUST : HDMI1: 1920x1080 @ 23.98Hz (22) (weight: 0.000)
And yet a screen capture clearly shows the viewable window as 808 pixels high:
http://i59.tinypic.com/20i6hl5.png
That seems way too much to account for the PAR error.