All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 16490] New: Xv overlay tearing
Date: Mon, 23 Jun 2008 14:57:17 -0700 (PDT)	[thread overview]
Message-ID: <bug-16490-8800@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=16490

           Summary: Xv overlay tearing
           Product: xorg
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: pq-X3B1VOXEql0@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


While investigating the Xv overlay & blitter issue with the X-server backing
store, I found the real overlay jerky and tearing.

I have to disable the Composite extension of the X-server to get the real
overlay adapter. Otherwise, due to the backing store issue, it falls back to
blitter (which I hear is then still drawing the colorkey when it should not,
but that's another issue). If Composite extension is enabled, blitter and
overlay adapters are identical with mplayer, producing a static horizontal tear
line (bug #16231).

Having Composite disabled, the blitter seems to work fine. Overlay looks jerky
and occasionally tears at random places, it looks mostly horizontal tear lines,
but they blink too fast to see clearly. It might also be blocky instead of just
a line.

Practically my whole graphics stack is from git, around 20th-22nd June.
The card is nv20, a Geforce 3.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2008-06-23 21:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 21:57 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-16490-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-07-04  4:12   ` [Bug 16490] Xv overlay tearing bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-07-04  7:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-08-08 10:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=bug-16490-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.