2014-01-20, 05:54
Ok. I think the point is that it's better to simply key on the pixel ratio being close to 1.0, rather than hardcode specific display aspects. (Otherwise you would also have to add 5/4, 16/10, 21/9, etc for more esoteric displays/computer monitors)
(2014-01-20, 05:42)lmyllari Wrote:(2014-01-19, 01:42)fritsch Wrote: If difference between ceil and direct value < 0.01 use the ceil. E.g. 0.998f will be 1.0fI'm not sure if I understood the code 100%, but wouldn't it fail if the direct value is too high, say 1.001f, or the desired ratio is not an integer?
(2014-01-19, 06:58)theMule Wrote: Can someone explain to me where the wmm and hmm variables are being populated from and what is their meaning?They are the display width and height in millimeters as reported from xrandr. I assume it gets the values from EDID.
From my xbmc-xrandr output (not on haswell hardware here, but I have the same issue with pixel ratios on my nvidia hardware, which I had so far worked around by editing the values to 1.0000 by hand in guisettings.xml)
<output name="DVI-I-2" connected="true" w="1920" h="1080" x="0" y="0" wmm="598" hmm="336">
The fact that 598/336 != 16/9 is obviously the underlying issue here, and I would like to understand where these numbers come from.
edit: me no splel very good