GNOME Bugzilla – Bug 513542
incorrect use of XV_HUE attribute with nvidia 169.09 drivers
Last modified: 2008-01-31 23:07:02 UTC
Please describe the problem: With new 169.09 nvidia video drivers has been added a feature for XV extension and HUE in playback executing xvinfo | grep -A2 XV_HUE after have been loaded Xorg you get: "XV_HUE" (range 0 to 360) client settable attribute client gettable attribute (current value is 0) note that "current value" is 0 if i play a video with any player (i tried VLC, mplayer/gmplayer, gxine) at this time i have no problem at all if i use totem the HUE became wrong and i see any video with wrong colors.. executing the same command after totem playback result in: "XV_HUE" (range 0 to 360) client settable attribute client gettable attribute (current value is 179) and any other video playback software i have the wrong HUE this can be fixed by opening preferences of gnome and set the HUE slide all to the left but it sholdn't work this way for more info and to see the opinion of nvidia linux drivers developers see this post in their forum: http://www.nvnews.net/vbulletin/showthread.php?t=107009 Steps to reproduce: 1. Install 169.09 nvidia driver 2. play a video with Totem 3. Actual results: you have a video with completely wrong HUE (missed up color) Expected results: i expect totem to read the XV_HUE setting and to use them as default instead of setting a wrong value Does this happen every time? yes on my system Other information: all additional information, with nvidia developers opinion, can be readed here: http://www.nvnews.net/vbulletin/showthread.php?t=107009
Which backend are you using?
gstreamer, sorry i didn't mentioned because i though it wasn't pertinent with the bug
gstreamer 0.10 to be more precise
Looks like a duplicate of #306621 to me. *** This bug has been marked as a duplicate of 306621 ***
that's a very old bug i first had this problem when i upgraded to the 169.09 nvidia drivers developers say that: "XV_HUE support was added for the 8-series GPUs in a relatively recent driver release, which is probably why you started seeing this problem recently. The range of 0 to 360 matches the way this attribute worked on the old NV17 Video Overlay adaptor, so the default of 0 should be pretty standard. This definitely sounds like a bug in Totem." i don't know exactly what totem should do with HUE but i never pressed the "reset to default" button the slider was in that position BEFORE i upgraded the drivers and i haven't had any problem before you know better then me what could cause this and if you say that it's the same bug may be it is... but if that's the case i can't understand why i haven't suffered it before and why it hasn't been fixed since 2005
Don't change the components please. The problem is actually with each Xv driver having a different idea of what the "defaults" are. And it's the same bug that's already been reported.