On Mon, Feb 4, 2013 at 10:45 PM, Artur de Sousa Rocha <[email protected]> wrote: > 2013/2/4 Richard Levitte <[email protected]>: >> Ok, in that case I'd like an explanation to what's happening to me. >> This all started with me color characterising my monitor (laptop LCD) >> and creating a profile for it (using dispcalGUI), then loading it >> (using 'dispwin -L'). Display colors became much better (grey is >> actually grey, not something with a blue tint). >> >> Then I started doing some work on some images I had taken just >> recently, and what I got was absolutely h-o-r-r-i-b-l-e. Basically, >> the three channels were kind of shifted in the histogram, and what was >> supposed to be a black background was now redish brown or some such. >> (I wonder if I could possibly produce a test, say by putting together >> a white .png, import it and see how it ends up). >> Changing my display profile from "system display" to "sRGB" gave me a >> better look. > > I'm afraid the "laptop LCD" part might be a clue. Few laptop displays > can deliver the gamut needed.
I agree most laptop displays are unsuitable for serious photo processing. But... > The calibration software tries to > preserve the brightness ratios between different levels. If it cannot > by a large margin it will fail in all kinds of ways. That's why I > moved to an external display for photo processing. It should still be possible to get a half-decent profile. Color managing a small gamut display just means you lose detail in very saturated parts of the image. It should not result in significant color shifts. So this might be fixable to an extent. Regards, Pascal de Bruijn ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
