On Wed, May 13, 2020, at 18:13, Ritchie, Andrew C wrote:
> Is there a list of features that **DO** work that way? Or is there some
> way I can tell by looking in the code?
Generally, any time you click a button in a module to "auto-set" some of the
parameters, the module state is the same as if you had manually moved the
sliders to those values, and the parameters are all that's recorded in history.
For a module to work the way you want, it needs to have a special selectable
"automatic" mode, which is itself a parameter changing the way the module
works. Offhand, other than the exposure module, I can only think of the older
"levels" (not the newer "RGB levels") module as having something like this, and
I don't think I've ever tried to use it for anything myself. I have a vague
impression of the auto-mode parameters being tricky to get predictable results
from, but you could look into it. That module may not be visible by default, in
which case you would need to enable it under "more modules". Description here:
https://darktable.gitlab.io/doc/en/tone_group.html#levels
> the main reason I’m working with DNG instead of ARW btw is because the
> manufacturer sensor crop isn’t honored with ARW and I need the
> principal point (and total area) to stay constant between softwares for
> good comparison of results.
Possibly the raw cropping settings in the "raw black/white point" module could
be useful here? By default darktable tries to include as much valid pixel area
as possible.
--
jys
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
