Hi Richard, thank you. I tried It, but applied afterwards the order has not changed back.
I have enabled writing of xmp files and I’m seeing that the timestamps of xmp files of images I had not opened yet, are still before the upgrade to 3.2.1. Most xmp files should still contain the right information. Do I have a chance to load this information from xmp files? The „load sidecar file …“ button is not an option. It’s too much work to do it for so many pictures. I also have a backup of the old library and could switch back to version 3.0.2. I would then disable auto apply of pixel workflow before doing the upgrade. Do you have any idea, what’s the preferred/better way? Andreas > Am 12.08.2020 um 21:03 schrieb Richard Hobday <rlhob...@gmx.co.uk>: > > You might benefit from changing the settings in: > Preferences/processing/auto apply pixel workflow defaults > this should allow you to the revert to the legacy pipe order. > > R. > > On 12/08/2020 19:15, Andreas Herold 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 > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
