![darktable auto correction darktable auto correction](https://pixls-discuss.s3.dualstack.us-east-1.amazonaws.com/original/3X/3/6/36a702a89a58bd2b85e947f65c0d8a3a0b8de787.png)
Lens correction (automatically applied with a preset) Crop and Rotate. I think there's something else going on here that I'm not seeing, and I'll watch the history stack closely from now on. However, HDR is not really usable on darktable (no auto de-ghosting) and there. That would seem to explain it, but I'm certain I was experiencing no lens correction being applied even though the history stack showed it had been. So I'm now wondering if my problem was caused by me saving a preset that was created while the module on/off icon was OFF. December is the snowiest month in Fawn Creek with 4.2 inches of snow, and 4 months of the year.
![darktable auto correction darktable auto correction](https://iili.io/pvBln.jpg)
August is the hottest month for Fawn Creek with an average high temperature of 91.2°, which ranks it as about average compared to other places in Kansas. Makes sense, since I had saved the preset without turning on the effect.ĭeleted that preset, then recreated it with:īrought in another of the new images and the lens correction was applied. In Fawn Creek, there are 3 comfortable months with high temperatures in the range of 70-85°.
![darktable auto correction darktable auto correction](https://pixls-discuss.s3.dualstack.us-east-1.amazonaws.com/optimized/3X/9/8/98ab62cbb9b7ffae592587e3373962d0bb16d58f_2_1380x752.png)
History stack showed 'lens correction (off)'. So far, so good.ĭeleted that preset, then recreated it exactly the same way EXCEPT the lens correction on/off icon was OFF.īrought in another of the new images and the lens correction was not applied. All selection fields with their default valuesīrought in one of the new images and the lens correction was applied, and the history stack showed 'lens correction'.