Re: [darktable-user] Module that still applies even if removed
Le 13/05/2023 à 18:45, Remco Viëtor a écrit : On samedi 13 mai 2023 18:41:52 CEST Remco Viëtor wrote: On samedi 13 mai 2023 18:00:17 CEST Jean-Luc wrote: Le 13/05/2023 à 14:03, Remco Viëtor a écrit : On samedi 13 mai 2023 12:23:12 CEST Jean-Luc wrote: Hello, Maybe I am doing things really wrong, but I am running into a problem .../... I am getting nuts - what on earth am I doing wrong ? Going nuts not getting. :-( .../... It sounds like you tried to change a built-in preset and store it under the same name. I don't think you can change the built-in presets. No, I did duplicate an existing one. But the solution is simple: select the layout you want to use as a basis, then go to "manage presets" and "duplicate" the preset. You'll be asked to give it a new name, and then you can adjust it to your liking. That is what I did. Oh, and a quick follow-up: module layout set through those presets doesn't influence which modules will be auto-applied. That's determined by your workflow settings in the "settings" dialog and possible presets in individual modules. 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. Rgrds, darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Module that still applies even if removed
On samedi 13 mai 2023 18:41:52 CEST Remco Viëtor wrote: > On samedi 13 mai 2023 18:00:17 CEST Jean-Luc wrote: > > Le 13/05/2023 à 14:03, Remco Viëtor a écrit : > > > On samedi 13 mai 2023 12:23:12 CEST Jean-Luc wrote: > > >> Hello, > > >> > > >> Maybe I am doing things really wrong, but I am running into a problem > > >> that the manual could not help me to solve. > > >> If I add a module to a workflow, it is easy to have it autoapplied. > > >> But, if I then remove it from the workflow, it still gets applied and > > >> activated upon compress history or new import - whatever I do. > > >> I am getting nuts - what on earth am I doing wrong ? > > > > > > Which module? > > > > > > And what exactly do you mean by "adding a module to a workflow"? Afaik > > > (version 4.2.1) it's not possible to add a module to one of the > > > predefined > > > workflows. > > > > > > What you can do is define auto-applied *presets*. But removal of the > > > preset > > > should stop them from being autoapplied... > > > > > > Remco > > > > Hello Remco, > > > > Yes, you are right, wrong terminology from my side. What I was calling > > workflow is actually a preset from the modules menu. > > The machine running dt is three roms away from the one I am writing from. > > I cloned the scene referred preset and rearranged the modules within, > > tweaking some of them - filmic RGB is one. > > Now, I would like to remove the filmic RGB module, but even then it > > still gets applied at new import or history compression. > > I tried with another module - sigmoid, that I just added - it behaves > > the same : no way to have it forgotten once it has been added. > > It sounds like you tried to change a built-in preset and store it under the > same name. I don't think you can change the built-in presets. > > But the solution is simple: select the layout you want to use as a basis, > then go to "manage presets" and "duplicate" the preset. You'll be asked to > give it a new name, and then you can adjust it to your liking. > > (Rapidement: il faut choisir un "preset" comme base, le *dupliquer* et > modifier le copie) Oh, and a quick follow-up: module layout set through those presets doesn't influence which modules will be auto-applied. That's determined by your workflow settings in the "settings" dialog and possible presets in individual modules. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Module that still applies even if removed
On samedi 13 mai 2023 18:00:17 CEST Jean-Luc wrote: > Le 13/05/2023 à 14:03, Remco Viëtor a écrit : > > On samedi 13 mai 2023 12:23:12 CEST Jean-Luc wrote: > >> Hello, > >> > >> Maybe I am doing things really wrong, but I am running into a problem > >> that the manual could not help me to solve. > >> If I add a module to a workflow, it is easy to have it autoapplied. > >> But, if I then remove it from the workflow, it still gets applied and > >> activated upon compress history or new import - whatever I do. > >> I am getting nuts - what on earth am I doing wrong ? > > > > Which module? > > > > And what exactly do you mean by "adding a module to a workflow"? Afaik > > (version 4.2.1) it's not possible to add a module to one of the predefined > > workflows. > > > > What you can do is define auto-applied *presets*. But removal of the > > preset > > should stop them from being autoapplied... > > > > Remco > > Hello Remco, > > Yes, you are right, wrong terminology from my side. What I was calling > workflow is actually a preset from the modules menu. > The machine running dt is three roms away from the one I am writing from. > I cloned the scene referred preset and rearranged the modules within, > tweaking some of them - filmic RGB is one. > Now, I would like to remove the filmic RGB module, but even then it > still gets applied at new import or history compression. > I tried with another module - sigmoid, that I just added - it behaves > the same : no way to have it forgotten once it has been added. It sounds like you tried to change a built-in preset and store it under the same name. I don't think you can change the built-in presets. But the solution is simple: select the layout you want to use as a basis, then go to "manage presets" and "duplicate" the preset. You'll be asked to give it a new name, and then you can adjust it to your liking. (Rapidement: il faut choisir un "preset" comme base, le *dupliquer* et modifier le copie) Remco darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Module that still applies even if removed
Le 13/05/2023 à 14:03, Remco Viëtor a écrit : On samedi 13 mai 2023 12:23:12 CEST Jean-Luc wrote: Hello, Maybe I am doing things really wrong, but I am running into a problem that the manual could not help me to solve. If I add a module to a workflow, it is easy to have it autoapplied. But, if I then remove it from the workflow, it still gets applied and activated upon compress history or new import - whatever I do. I am getting nuts - what on earth am I doing wrong ? Which module? And what exactly do you mean by "adding a module to a workflow"? Afaik (version 4.2.1) it's not possible to add a module to one of the predefined workflows. What you can do is define auto-applied *presets*. But removal of the preset should stop them from being autoapplied... Remco Hello Remco, Yes, you are right, wrong terminology from my side. What I was calling workflow is actually a preset from the modules menu. The machine running dt is three roms away from the one I am writing from. I cloned the scene referred preset and rearranged the modules within, tweaking some of them - filmic RGB is one. Now, I would like to remove the filmic RGB module, but even then it still gets applied at new import or history compression. I tried with another module - sigmoid, that I just added - it behaves the same : no way to have it forgotten once it has been added. Am I that stupid ? What part am I misunderstanding or doing wrong ? Rgrds, J.-Luc darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Module that still applies even if removed
On samedi 13 mai 2023 12:23:12 CEST Jean-Luc wrote: > Hello, > > Maybe I am doing things really wrong, but I am running into a problem > that the manual could not help me to solve. > If I add a module to a workflow, it is easy to have it autoapplied. > But, if I then remove it from the workflow, it still gets applied and > activated upon compress history or new import - whatever I do. > I am getting nuts - what on earth am I doing wrong ? Which module? And what exactly do you mean by "adding a module to a workflow"? Afaik (version 4.2.1) it's not possible to add a module to one of the predefined workflows. What you can do is define auto-applied *presets*. But removal of the preset should stop them from being autoapplied... Remco darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
[darktable-user] Module that still applies even if removed
Hello, Maybe I am doing things really wrong, but I am running into a problem that the manual could not help me to solve. If I add a module to a workflow, it is easy to have it autoapplied. But, if I then remove it from the workflow, it still gets applied and activated upon compress history or new import - whatever I do. I am getting nuts - what on earth am I doing wrong ? Regards, J.-Luc darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
