[Sunflux]

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:10 T:140160032450432 INFO: ID:0x48 Name:1920x1080 Refresh:60.000000 Width:1920 Height:1080
07:37:10 T:140160032450432 INFO: Pixel Ratio: 1.000512

1920 / 1.000512 = 1919,017463059

Yeah, teach your TV to behave better. For the 808 that's not an issue. It is centered and the rest of the surface is black, but the 1919 introduces a ratio change, rescaling and so on. You need the patch I posted above.

...And I just figured out what's causing the 808 pixel issue. Disabling the 1% allowable aspect ratio error fixes the vertical scaling and returns the video to 800 pixels high in a 1080 window (but of course returns the horizontal problem). So, it's a MANDATORY 1% error - enforced if it can be, no matter what..800 + 1% = 808.

So to fix a 1 pixel horizontal scaling issue, I'm expected to accept an 8 pixel vertical scaling issue? If the file's 1050 pixels high, that'll be an 11 pixel error! Gee. I do wish your "rounding error" fix would be made mainstream, because the alternate fix is worse than the problem!

Any way to simply override the screen's PAR without a complicated EDID replacement? Or ignore it?