> Am 12.08.2020 um 21:32 schrieb KOVÁCS István <k...@kovacs-telekes.org>:
>
> On Wed, 12 Aug 2020 at 21:09, Richard Hobday <rlhob...@gmx.co.uk> wrote:
>> 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.
>
> I thought that setting changes which modules get auto-applied (base
> curve or filmic+exposure or none). There's a 'module order' setting in
> the darkroom (below the modules, above 'more modules') that allows you
> to switch between 3.0 and legacy order -- however, in that respect,
> 3.2.1 did not bring any changes, did it (that is, the order of modules
> between 3.0 and 3.2 is the same, is it not)?
>
> However, wouldn't raster masks solve the original poster's problem?
> E.g. one could create a 'dummy' module instance early in the pipe
> (like exposure with no actual change of the exposure), create a mask,
> and re-use that mask as a raster mask for any number of modules that
> come later in the pipe. Any modifications (e.g. changes to exposure)
> done after the 'dummy' exposure module would leave the raster mask
> unchanged.
>
> https://www.darktable.org/2019/12/darktable-30/
> 'Raster masks add a new mode that allows you to reuse a mask from one
> module to another module. This is particularly interesting with
> parametric masks: copying the parameters from one module to another
> would not have been enough because the same parameters do not select
> the same pixels depending on where you are in the pipe. The raster
> mask reuses the mask directly, so it does not have this problem.
> Warning: The raster mask can only take a mask from a module preceding
> it in the processing chain. [...]'
Thank you. This sounds very promising and I will try it. But nevertheless I
need to find a way to rescue my already processed images.
Andreas
>
> Kofa
> ___________________________________________________________________________
> 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
