Prior to version 3.0 darktable’s workflow was display-referred (auto-apply pixel workflow defaults = “display-referred”) and this option is still provided as a legacy mode. The remaining modules operate in the non-linear display-referred section of the pixelpipe to produce the final output image. The dynamic range of an image in the scene-referred section of the pixelpipe is often larger than that of the display medium.Īt some point in the pixelpipe, these pixel values are compressed by a non-linear tone mapping operation into a smaller dynamic range more suitable for display on a monitor or a print. Scene-referred modules process linear data that is proportional to the amount of light collected by the camera at the scene. The following diagram should help you to understand the difference between these workflows: Honoring the physical realism (rather than the perceptual realism) makes it much easier to produce predictable processing algorithms with a minimum of artifacts. This has the advantage of being a more physically-realistic space to do transformations than the traditional display-referred workflow, which attempts to perform operations in a non-linear perceptual color space. The scene-referred workflow attempts to perform as many operations as possible in a linear RGB color space, only compressing the tones to fit the output medium (with a non-linear tone mapping) at the end of the pixelpipe. Starting with version 3.6, scene-referred workflow is now the official recommended (and default) way to use darktable. Version 3.2 formalised this by introducing the display-referred and scene-referred workflows, which are controlled by the preferences > processing > auto-apply pixel workflow defaults setting. One of the main reasons to change the module order came about with darktable version 3.0, which introduced the new scene-referred way of working. However, there are a number of very specific use cases where the movement of some modules within the pixelpipe is advised. In previous versions of darktable it was not possible to change the module order. The order in which modules are executed within the pixelpipe has been carefully chosen to give the best output quality. Changing the order of the modules in the user interface changes how your image is processed. Note: The order in which processing modules are executed exactly matches the order in which the modules appear in darktable’s user interface. The order of the pixelpipe is represented graphically by the order in which modules are presented in the user interface – the pixelpipe starts with a RAW image at the bottom of the module list, and applies the processing modules one by one, piling up layer upon layer of processing from the bottom up, until it reaches the top of the list, where it outputs the fully processed image. The ordered sequence of processing modules operating on an input file to generate an output image is known as the “pixelpipe”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |