Ulrich, thank you for the detailed explanation about DT workflow.
It leads me to another question. Would it be difficult to have a modules'
function be applied twice to an image. With the new selective blending
features that work in Lab space, there has been more than one occasion
where I thought it would be amazing if I could use the same module on the
same picture multiple times, and having the selective blending apply the
effect on specific and varied parameters of the image. Is that something
that would disrupt the current workflow?
Regards,
John
Am 03.02.2013 08:44, schrieb Torsten Bronger:
> Hallöchen!
>
> John P Santos writes:
>
>> It's not a bug. The image profile does actually change the data
>> that you're working with, so you will get another histogram. If
>> you've just calibrated your monitor, did you restart your shell?
>> Darktable will use the system settings for output profile. I set
>> everything to Adobe, because I record all my images in an Adobe
>> colour profile because it has more colour depth.
>
> As I said, I'm not sure about *output* profile -- it may be okay if
> this affects the histogram. But if the *display* profile affects
> it, this does not make sense to me. The result of my image editing
> should not depend on the monitor I use. After all, this is what
> monitor calibration is all about.
>
darktable currently does not have the concept of a "working profile".
Most of our processing is done in Lab color space until in module
colorout data is converted into final output RGB color space. For image
display this color space is defined by your monitor profile; for file
output it is defined by the selected output profile - typically a device
independent profile like sRGB or AdobeRGB.
Assuming that you have installed a proper monitor profile in essence
this means that the look of you image on display is as close as it can
get to the data in your exported file.
Different than other software darktable does not need a "working
profile", because we do all processing in floating point data. A working
profile is needed if your image data is in a limited integer format of 8
or 16bit. It will then define a compromise between resolution in color
range and gamut.
darktables histogram is derived from our preview/navigation window,
which contains RGB data in monitor color space. That also explains why
changing monitor profile has an effect on the histogram.
That said: changing this behavior would mean a significant change in
darktables workflow. In fact we would need to do all processing after
leaving Lab in some abstract color space (e.g. AdobeRGB) and only
convert to monitor color space as a very last step - which would be one
conversion step in addition.
I understand that our current way of processing might be surprising at
first sight if you come from another software. However, besides of that
surprise I do not get the point why it would be crucial to have this
changed.
Ulrich
------------------------------------------------------------------------------
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
Darktable-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-users
------------------------------------------------------------------------------
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
Darktable-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-users
