[mythtv-users] judder problems with nvidia 358.16

[Mark Goldberg]

On Wed, Aug 2, 2017 you wrote:

> 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
>

It used to work for years before Nvidia changed something. Myth could
automatically choose the appropriate framerate. See this other thread for
more info:

https://lists.gt.net/mythtv/users/596480

and these:

https://code.mythtv.org/trac/ticket/5643
https://code.mythtv.org/trac/ticket/11493

and I am sure a few more.

Basically, this:

https://www.mythtv.org/wiki/User_Manual:JudderFree

does not work any more.


Thanks for looking.

Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20170802/678ab3ca/attachment.html>