From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 21869] New: Chroma mismatch using XV
Date: Fri, 22 May 2009 04:54:20 -0700 (PDT) [thread overview]
Message-ID: <bug-21869-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=21869
Summary: Chroma mismatch using XV
Product: xorg
Version: 7.4
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: ancoron-gfoo8dC7XAXddJNmlsFzeA@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
I recently found out that the nouveau driver (and especially its XV
implementation) causes the following chroma-issue with my NV34M. At every
second frame I can see that the chroma is reused from the last frame and not
updated for the current frame. The luminance is always correct.
I checked on another machine with a radeon card to verify that it is not a
problem caused by some other things. XV rendering itself is very fast and I
don't have other problems here.
I have extracted an interesting portion of an encoded video to show what I
mean. I would really like to be able to provide a screenshot of a frame but I
don't know how to get those rendered frames out of the video memory.
If anyone comes by this issue with another hardware than mine please check if
you get the same issue there.
The command I used to verify the problem in mplayer was:
mplayer xv-chroma-mismatch.avi -fps 1 -vo x11
In addition mplayer output is just fine.
Machine infos:
Dell Inspiron 8600
- nVidia GeForce FX Go5200 64M (rev a1, NV34M)
- Kubuntu Jaunty (9.04)
$ dpkg -l | grep nouveau
ii libdrm-nouveau1 2.4.7-0~8.10~ppa3
ii nouveau-kernel-source 0.0.11+git20090404-0ubuntu1
ii xserver-xorg-video-nouveau 1:0.0.10~git+20090404+11be9a9-0ubuntu1
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2009-05-22 11:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 11:54 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-21869-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-05-22 11:58 ` [Bug 21869] Chroma mismatch using XV bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-22 12:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-22 12:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-22 12:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-22 12:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-22 12:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-22 12:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-22 12:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-22 12:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-22 13:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-22 17:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-23 9:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-23 12:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-23 12:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-23 12:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-30 12:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-06-25 20:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-10-25 14:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-10-25 14:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-10-25 18:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-10-25 19:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:09 ` 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-21869-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.