Ok, got a little more here, on the nvnews.net website I found an interesting comment:
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. Unfortunatly I do not know if my card always reported as an NV17 now, but apparently that's an attempt at some kind of backwards hackish attempt at not needing any changes in XV? Anyway the "default" value that totem/gxine/mplayer/vlc seem to call is the middle hue value, which in this case is generally 179 or 180. Obivously the NVidia people seem to think that a default of 0 should be correct, and I've posted there to try and find out where the negitave values went. Unfortunatly this is where my knowledge of the inner workings of X fall apart, are the media players coming up with a middle value in their own code, or is a call to XV doing it?
