On samedi 25 juillet 2020 09:15:21 CEST tony Hamilton wrote: > Correct, previously I was trying to get monochrome applied > automatically. But, aside from knowing that I was not trying to do that > in this case, please note that I have not said the whole image is in > monochrome; only a selection of pixels have turned a sort of 'polluted' > grey - with, apparently, some red in them.
When you have defined a preset to be auto-applied, it will be applied whenever you open an image for the first time in the darkroom (provided the image matches, of course) > I don't see how this can be > the result of some preset as, as part of this learning exercise, I have > performed a clean install of DT and all my test images, newly copied > from LightRoom. A clean install means that you also removed the old database and configuration files? Note that some of these can be hidden (~/.config/darktable/* under linux, no idea where to find such files for MS-Windows). > None of this answers the question of how did the > monochrome module get into the history stack in the first place. Well, that part *was* answered by Patrick Shanahan... As you seemed to have set up a preset to be auto-applied to "matching images", that preset will still exist, *and be applied*, when you just re-install the program. Btw, did you follow the suggestion from Patrick, starting darktable with " darktable --library :memory: "? Among other things, you won't get any preset applied on importing an image/ folder. > Of > course one valid explanation is that I am so intellectually stunted that > I do things without realising it or perform actions with no idea of > their consequences. If this were the case, would I be able to use DT at > all? I'd rather not comment on this. Remco ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
