[mythtv-users] judder problems with nvidia 358.16

Alex Halovanic halovanic at gmail.com
Wed Aug 2 23:51:01 UTC 2017


Actually I think this is something a little different than that issue.  I
believe it boils down to xrandr (X Resize, Rotate and Reflection extension)
only reporting refresh rates as integers.  If memory serves, Nvidia ended
up "overriding" the refresh rate to values like 50, 51 in order to report
them uniquely.  I think it also had something to do with Twinview/Xinerama
and multiple monitor support.  In the past, you could turn this off and get
the "real" refresh rates out, but I think later drivers always ended up
reporting these fake values.  But without the fake values, you can't even
distinguish between 59.94 and 60.00 HZ as they both come out as 60,

I thought maybe a later update to X.Org fixed this, but it seems like it
remains that way.  However, I *have* noticed the xrandr command line
utility does report 59.94 and 60.00 accurately!  It looks like it actually
does a little calculation using some of the raw modeline values to get
around this flaw, but the numbers seem to check out.

I will probably try monkeying around in the code to see if I can get
Mythfrontend to spit out the true refresh rates.  I'm not sure how far down
this integer/double confusion goes and if there are other workarounds in
place.

Thanks,
Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20170802/223d4e56/attachment.html>


More information about the mythtv-users mailing list