Re: [darktable-user] Module that still applies even if removed
Le 14/05/2023 à 21:14, Jean-Luc a écrit : Le 14/05/2023 à 19:07, Jack Bowling a écrit : Change the workflow preference in the settings to "None" and see if your problem goes away. Jack On 2023-05-14 09:07, Jean-Luc wrote: Le 14/05/2023 à 16:04, thouks a écrit : Which workflow preset did you choose in the global setting? Am 14. Mai 2023 15:04:33 MESZ schrieb Jean-Luc : 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: (..) .../... 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. .../... 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. Hello thouks, I am not sure whether I understand your question... If you mean the preset I started from, the one I duplicated, then the answear is Relatif à la scène (Scene referred if I translate correctly). This seemed logical and obvious to me to use a workflow built for the kind I would use. Hello Jack, I was sure I had checked this before. Hopefully, I did it now. Surprizingly, switching to None or Display (and restart dt) makes things work as expected. I tested both. So I will keep this setting to None until a solution is found. And update the report to take this into account. Rgrds, J.-Luc So, it seems it is a wanted behaviour, as Filmic is a mandatory module when the wokflow is set to scene-referred. Unexpected, but there was surely a good reason for this. And, I realize I did not read correctly the manual - I must have skipped the section where this is explained. Sorry for this. 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
Le 14/05/2023 à 19:07, Jack Bowling a écrit : Change the workflow preference in the settings to "None" and see if your problem goes away. Jack On 2023-05-14 09:07, Jean-Luc wrote: Le 14/05/2023 à 16:04, thouks a écrit : Which workflow preset did you choose in the global setting? Am 14. Mai 2023 15:04:33 MESZ schrieb Jean-Luc : 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: (..) .../... 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. .../... 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. Hello thouks, I am not sure whether I understand your question... If you mean the preset I started from, the one I duplicated, then the answear is Relatif à la scène (Scene referred if I translate correctly). This seemed logical and obvious to me to use a workflow built for the kind I would use. Hello Jack, I was sure I had checked this before. Hopefully, I did it now. Surprizingly, switching to None or Display (and restart dt) makes things work as expected. I tested both. So I will keep this setting to None until a solution is found. And update the report to take this into account. 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
Change the workflow preference in the settings to "None" and see if your problem goes away. Jack On 2023-05-14 09:07, Jean-Luc wrote: Le 14/05/2023 à 16:04, thouks a écrit : Which workflow preset did you choose in the global setting? Am 14. Mai 2023 15:04:33 MESZ schrieb Jean-Luc : 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: (..) .../... 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. .../... 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. Hello thouks, I am not sure whether I understand your question... If you mean the preset I started from, the one I duplicated, then the answear is Relatif à la scène (Scene referred if I translate correctly). This seemed logical and obvious to me to use a workflow built for the kind I would use. 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
Re: [darktable-user] Module that still applies even if removed
Le 14/05/2023 à 16:04, thouks a écrit : Which workflow preset did you choose in the global setting? Am 14. Mai 2023 15:04:33 MESZ schrieb Jean-Luc : 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: (..) .../... 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. .../... 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. Hello thouks, I am not sure whether I understand your question... If you mean the preset I started from, the one I duplicated, then the answear is Relatif à la scène (Scene referred if I translate correctly). This seemed logical and obvious to me to use a workflow built for the kind I would use. 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
Which workflow preset did you choose in the global setting? Am 14. Mai 2023 15:04:33 MESZ schrieb Jean-Luc : >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
Re: [darktable-user] Module that still applies even if removed
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
Re: [darktable-user] Module that still applies even if removed
On dimanche 14 mai 2023 00:36:10 CEST Jean-Luc wrote: > 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: (..) > 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. 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 à 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
