From: Chris Wilson <chris@chris-wilson.co.uk>
To: Oliver Seitz <info@vtnd.de>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: Video tearing on Sandybridge
Date: Mon, 02 Apr 2012 11:03:50 +0100 [thread overview]
Message-ID: <1333361053_198990@CP5-2952> (raw)
In-Reply-To: <4F774449.5080906@vtnd.de>
On Sat, 31 Mar 2012 19:52:09 +0200, Oliver Seitz <info@vtnd.de> wrote:
[snip]
> If, however, two screens are next to or on top of each other, playing
> video on one of the screens can show some tearing. It is not always seen
> with normal video, a special test pattern is helpful. Also, it does only
> tear in one out of ten tries, you can hit pause again and again, sooner
> or later the tearing will appear, and disappear again after the next
> pause/unpause cycle. While the tearing is there, it stays at about the
> same height of the video until the next pause/unpause cycle. Most times
> it is seen in the top third of the video. It does not matter if the
> video is fullscreen or not.
>
> Is it likely that this is a bug, or am I doing something wrong?
Video tearing in windows is a known issue on SandyBridge as they removed
the commands to perform vsync'ed updates and hid the logic behind a
baffling sequence of registers that we have not yet got working.
The only workaround is to force pageflipping (ie exchange the whole
scanout for each frame) either by using a compositing WM (and hoping
for the best) or to only use fullscreen DRI video applications
(OpenGL or libva decoders) that use SwapBuffers.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-04-02 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 17:52 Video tearing on Sandybridge Oliver Seitz
2012-04-02 10:03 ` Chris Wilson [this message]
2012-04-02 10:40 ` Oliver Seitz
2012-04-02 11:06 ` Daniel Vetter
2012-04-02 11:30 ` Oliver Seitz
2012-04-02 13:22 ` Eugeni Dodonov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1333361053_198990@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=info@vtnd.de \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.