Which workflow preset did you choose in the global setting?
Am 14. Mai 2023 15:04:33 MESZ schrieb Jean-Luc <jean-luc.cecc...@wanadoo.fr>:
>Le 14/05/2023 à 08:10, Remco Viëtor a écrit :
>> On dimanche 14 mai 2023 00:36:10 CEST Jean-Luc wrote:
>>> On samedi 13 mai 2023 12:23:12 CEST Jean-Luc wrote:
>> (..)
>>> In my case, there is no preset defined in the module.
>>> By the way, I would expect that removing a module from a preset would
>>> prevent it from being applied and activated.
>>> There is definitely something I have trouble in understanding.
>>> I think Aurélien P. or Luc V. might have done videos where this could be
>>> explained, I just have to get ahold of the one.
>> In version 4.2.1, the *only* place where you can remove an individual module
>> from a preset is in the module layout. And that layout has no influence on
>> whether a module is auto-applied, auto-activated or not.
>>
>> We are dealing with at least three different "presets" here:
>> - presets in individual modules, can be autoapplied or not.
>> - workflow presets, selected in the global settings dialog. These will
>> determine which modules are initially activated, and cannot be changed by the
>> user
>> - module layout presets. These *only* determine which modules will be visible
>> in the module section of the right sidebar. This has *no* influence on the
>> modules that will be activated for a new edit or after fully clearing the
>> history.
>>
>OK, that is clear. What is not, still, is the way it behaves here.
>Filmic did not appear in the moduel section before I added it into the group I
>had created from the main one.
>And it was not activated nor applied until I created a preset in the module
>itself telling it to autoapply to all photos matching some conditions.
>Then, I wanted to get rid of it, so I first removed the preset upon which it
>was autoapplied. But, on my great surprise, it still gets applied upon history
>compression or new import.
>...
>OK, I went to the machine running dt, ensured there was no preset left into
>Filmic, then created one matching this :
>
>I am sure none of the photos I took matches any of those conditions, so
>compressing the history I ought not see Filmic anymore but, guess what ? It is
>there again displayed in the history.
>So, what makes it behave this way ? Why does it still bother me, instead of
>staying still ?
>...
>Back to dt again, to test whether it might also happen with other modules. I
>recently added Sigmoid to my workflow, and created the preset so it could be
>autoapplied.
>Deleting the preset, Sigmoid is not applied anymore upon compression or new
>import. Re-creating the preset, Sigmoid auto-applies again.
>At this point, unless someone proves that I am doing something wrong, I think
>it is time I open a bug report.
>
>Rgrds,
>
>J.-Luc
>
>____________________________________________________________________________
>darktable user mailing list
>to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
