On Wed, Dec 23, 2015 at 12:01:44PM +0000, Chris Wilson wrote: > The clipped extents of the va-api Window is used to determine which CRTC > to use as the vblank source. Hmm, the Primary Output is used as the > preference (i.e. if any part of that Window is on the Primary, it is > used as the CRTC - the idea being that Primary is important and this > should share the vblank source for more Windows and prevent arbitrary > jumps between vblank sources as the Window moves). just tested, with xv output, vsync seems to be quite ok. however, with va-api it not ok on both LVDS and HDMI. HDMI seems to be far worse with va-api (i.e. out of sync). Maybe a bug in va-api sync code? -- Lukáš Hejtmánek _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
