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 124072 - gamma correction wrong
gamma correction wrong
Status: RESOLVED OBSOLETE
Product: gnome-color-manager
Classification: Core
Component: general
git master
Other All
: Normal minor
: ---
Assigned To: gnome-color-manager-maint
gnome-color-manager-maint
Depends on: 124170
Blocks:
 
 
Reported: 2003-10-07 22:47 UTC by Chad Miller
Modified: 2010-09-29 17:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Chad Miller 2003-10-07 22:47:58 UTC
This will be a painful bug to fix; so painful that most people won't even
want to think about it.  If you're the type to stick your head in the sand,
then discontinue reading now.

The display of most of our computers is wrong.  Light emitted isn't
proportional to signal strength.  We set our highs and lows on the monitor,
but the values in between are not linear, but a ugly U-shaped curve; on our
PC-ish hardware, images are much darker than the data in the file is.  

When we build our images and icons atop the foundation of this dark curve,
we shim up the brightness so that it looks correct to us on our monitor. 
When we see an image from outside our computer, like a digital camera,
which (correctly) doesn't fill in our bad gamma-curve, the images look dark
to us.  Black is still black, and white is still white, but the medium grey
that should be right in the middle, is much darker than it should be.

To make sure you understand the problem, consider this image:
  http://images.chad.org/paris/chad-place-de-vosges.jpeg
The image is too dark, but it is not under-exposed.  The problem is your
and my displays.  While viewing that image, open a new xterm and type
"xgamma -gamma 1.7" .  Pow!  

That image now looks like it should (or close to it).  But, unfortunately,
note that many of your other icons are washed out.  Thus, we arrive at the
crux of the matter.

There are two problems to be solved (which I suggest making as blocking
bugs to this ueber-bug):

*  GNOME should offer as a preference (defaulting to a sane value) setting
of the X server's gamma correction value.

*  Many GNOME applications' icons are too light -- they are designed to
look correct after looking through the broken lens of our displays.  (Some
use PNG which is (thankfully) designed to handle gamma correction
internally, but (terribly, horribly) is not implemented in some/most/all?
versions of libPNG so even though a number exists in the file, it's
(excruciatingly) the wrong value.  Not supporting gamma is bad, but seeming
to and getting it wrong is much worse.)

The first item/bug, I'm not sure where to file it.  control-panel?

The second item might mean filing minor bugs on projects that don't use PNG
or once used it incorrectly when creating their images.  An enterprising
individual (perhaps me) might create a script that converts images from the
default bad gamma values to good values and munge images in batch so
project managers can fix it themselves in one swoop.

We can't affect what the outside world will create for us, but we can fix
our own images and adapt to the correct gamma curve.

I sincerely think gamma correction is a problem is worth solving, and that
once understood (which is nontrivial) will seem worthy of solving by those
affected.


More URLs that describe the problem:
  http://www.cgsd.com/papers/gamma.web.html
  http://graphics.stanford.edu/gamma.html
Comment 1 Chad Miller 2003-10-07 22:56:00 UTC
Adding keyword to get eyeballs.
Comment 2 Andrew Sobala 2003-10-09 12:49:04 UTC
Bzzzzzzzzzzz <fry>

Moving to control center as "most relevant module" imho.
Comment 3 Chad Miller 2003-10-10 02:39:05 UTC
I'll let the control-center maintainer reassign this, as I don't have
a better suggestion if "general" is verboten.  (Though, "general"
seems like a good category for endemic, pan-program bugs.  I didn't
create the taxonomy, I just have to fit within it.  Why is "general"
wrong?)

Incorrect gamma values are inherent in almost _every_ GNOME app; this
is not localized to control center.  

I hope to file enh bugs on every app that has bogus gamma values in
its icons and UI images and have each bug block this one.  CC already
has a bug for setting gamma values; this bug doesn't belong to it too.
Comment 4 Elijah Newren 2004-07-17 20:55:17 UTC
/me elbows Andrew for forgetting "Reassign bug to owner of selected component"

Chad: The main problem with "general" is that it has no assignee, which really
means that no one looks at the bug.  However, I think from your plans to file a
whole bunch of bugs from different products and have them all to block this one
would actually make general be okay as the product.  But as a standalone bug,
that wouldn't work too well.  I do agree that the way the "general" product
works is somewhat confusing.
Comment 5 Thomas Wood 2007-01-19 14:39:13 UTC
It's probably worth noting that nvidia now supply the nvidia-settings tool with their graphics drivers that allows users to adjust the gamma amongst many other settings.
Comment 6 Bastien Nocera 2007-02-14 13:58:19 UTC
CC:'ing Ross on gamma stuff
Comment 7 Richard Hughes 2010-09-29 14:50:19 UTC
gnome-color-manager allows you to adjust the session gamma using a combination of your color icc profile and some maths, before squirting it to the per-screen gamma ramps in x. Does gnome-color-manager do what you want?
Comment 8 Chad Miller 2010-09-29 17:07:42 UTC
Wow, I can't believe I wrote all that.

I think g-c-m will get very close to what I want.  If it doesn't, I'll file bugs.