After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 343378 - Default settings of the color balance must have hue value to 0, not to 50%
Default settings of the color balance must have hue value to 0, not to 50%
Status: RESOLVED DUPLICATE of bug 306621
Product: totem
Classification: Core
Component: Movie player
1.4.x
Other Linux
: Normal minor
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-05-30 10:12 UTC by Lionel Dricot
Modified: 2007-04-03 14:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Lionel Dricot 2006-05-30 10:12:09 UTC 
Open a movie in totem then go to Preferences > Display tab.

See that, by default, the three first sliders of the color balance are set to 50% (Luminosité, Contraste and Saturation in french translation).

The last one, tint (teinte, in french), is set to 0. 


Play a bit with sliders. Then you want reset the defaults so press the "reset" button (Réinitialiser par défaut in french).


The last slider, tint, is set to 50%. It's not the real default and it must be set, instead, to 0. (else, you will have a green-blueish movie).
Comment 1 Bastien Nocera 2006-06-05 22:49:29 UTC 
Actually, I get the opposite. If I set it to 50%, I have the right picture, and get a blue tint if I set to to 0. What video card do you have, and which drivers do you use for it?
Comment 2 Lionel Dricot 2006-06-06 07:17:21 UTC 
Thanks for your reply. Strange...

I use a GeForce 4 MX with the proprietary nvidia driver (nvidia-glx in Ubuntu).
Comment 3 Bastien Nocera 2007-01-05 13:04:22 UTC 
Is this with the GStreamer, or the xine-lib backend?
Comment 4 Philip Withnall 2007-04-03 14:37:04 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 306621 ***