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. |