On Mon, Feb 4, 2013 at 1:09 PM, Torsten Bronger <[email protected]> wrote: > Hallöchen! > > Richard Levitte writes: > >> [...] >> >> The more I'm thinking about this, the more I wonder what's the >> purpose of the display profile... [...] Is there any reason I >> should have the display profile set to something other than the >> output profile? > > If I edit images by looking at how they appear on the screen rather > than by looking at the histogram, I need a display profile. > Otherwise, changing the monitor would change the editing result.
I just came back from FOSDEM, and there this huge thread now :) I haven't had time to thoroughly read the full thread, but I tend to agree with the idea that the histogram (ideally) shouldn't depend on the display profile. It should (ideally) probably be calculated against output profile (typically sRGB or AdobeRGB) as this is what it actually saved to disk on a typical export. (I'm not aware what the implementational consequences would be of such a change, so there may be some practical constraints for the time being). Beside the above, it might be useful to know what other applications do. Having some consistency in behavior across applications isn't a bad thing (assuming the other apps aren't doing silly things :). So if someone wants to do a survey that might be interesting. 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
