[mythtv-users] judder problems with nvidia 358.16

[Will Dormann]

On 3/4/16 5:10 AM, Marius Schrecker wrote:
> incorrect rtc permissions, although I don't see this fixing the
> incorrect refresh rates being consistently chosen.


I'm no expert on this stuff, but these look suspicious:

Mar  3 20:13:32 mythbox mythfrontend.real: mythfrontend[22207]: E
CoreContext vsync.cpp:275 (TryInit) VSYNC: DRMVideoSync: VBlank ioctl
did not work, unimplemented in this driver?
Mar  3 20:13:32 mythbox mythfrontend.real: mythfrontend[22207]: E
CoreContext vsync.cpp:356 (TryInit) VSYNC: RTCVideoSync: Could not open
/dev/rtc: #012#011#011#011eno: Permission denied (13)
Mar  3 20:13:32 mythbox mythfrontend.real: mythfrontend[22207]: E
CoreContext mythplayer.cpp:2395 (VideoStart) Player(0): Video sync
method can't support double framerate (refresh rate too low for 2x deint)
Mar  3 20:13:32 mythbox mythfrontend.real: mythfrontend[22207]: I
CoreContext mythplayer.cpp:1789 (InitAVSync) Player(0): Display Refresh
Rate: 23.971 Video Frame Rate: 25.000



The equivalent on my system:

Nov 18 21:52:35 <HOSTNAME> mythfrontend.real: mythfrontend[2375]: I
CoreContext mythrender_opengl.cpp:76 (Create) OpenGL: Sync to VBlank is
enabled (good!)




I think the former could cause tearing.  But I'd think that the nvidia
driver stuff could handle that stuff.    I'm using the nvidia 304.131
driver, FWIW.   However according to
<https://www.mythtv.org/wiki/Frame_display_timing>, "Contrary to what
Mythfrontend may say, VDPAU does not use vsync/vblank timing. RTC should
be used instead. "   So that may be not relevant.   My system config has
persisted through many years of MythTV, though, so that could even be an
artifact of a prior pre-VDPAU configuration.

As for the 23.97fps vs 25fps stuff, that surely seems like trouble.  It
almost would seem that you're trying to play PAL video on an NTSC TV?


-WD