Comment # 7
on bug 84944
from warpme@o2.pl
(In reply to Christian König from comment #5) > The deinterlacer is hardware independent and so it's rather unlikely that it > is the source of the problem. > > Can you grab a trace of MythTV with VDPAU_TRACE=1 in the environment once > with and once without deinterlacing enabled? This way we can see what MythTV > is actually doing. Adding VDPAU_TRACE=1 causes stop working VDPAU (MythTV switches to ffmpeg). I can try to investigate this - if You believe it is worth.... For me results from tests Michel suggested shows issue is within GLAMOR as Brazos without GLAMOR works OK while Brazos with GLAMOR NOK. As Kabini by default requires GLAMOR - by default I have issue on Kabini. Both Brazos and Kabini are tested from exactly the same PXE booted image so if Myth has working DI on Brazos - it is asking exactly the same way (and I believe correctly) for DI on Kabini. On the other hand - only on AMD I have in MythTV logs something like this: "W OpenGL: Could not determine whether Sync to VBlank is enabled." On Intel OSS and Nvidia proprietary drivers MythTV reports sync-to-blank works OK. But as - despite this warning - Brazos DI work nicely - I think this probably isn't root cause... br
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
