Hi, You can still use the old, ordered processing pipeline with base curve and all that. You just need to select it from the modules menu.
Your workflow sounds very nonstandard though, I'd think most start with global adjustments and work toward local adjustments at the end of the edit. - m On August 12, 2020 11:15:32 AM PDT, Andreas Herold <andreas.her...@web.de> wrote: >Hi, > >some feedback from a User who made currently the upgrade from 3.0.2 to >3.2.1. > >In my workflow I’m using very often modules, which are using parametric >masks. I’m applying moduIes with parametric masks very early in >processing. I do this, to have stable masks, that are not depend on >other modules. E.g. if I want to change brightness and contrast of the >sky, I’m doing this before changing overall brightness. This way the >mask of the sky does not depend on overall brightness. >After upgrade from 3.0.2 to 3.2.1 I now see, that the order of modules >has changed. For example, now the overall brightness is applied before >the module, that was changing the sky. Since I had used a parametric >mask, this mask became invalid. It is not the same selection I >originally chosed. In the result, the processing is destroyed for >hundreds of images. > >Best regards >Andreas >Herold___________________________________________________________________________ >darktable developer mailing list >to unsubscribe send a mail to >darktable-dev+unsubscr...@lists.darktable.org ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
