Windows 10 22H2, DT 4.4.2
Should there be a preference setting for “Processing” that reads something like “Apply chromatic aberration adaptation”? Apparently in the Mac version there is, whereby the drop down menu allows for the “legacy” setting.
You’re probably thinking of “Auto apply pixel default workflow” see darktable 4.4 user manual - processing
No, not really. I saw where @Andy_Astbury1 applied the legacy function under the heading I mentioned above. It does not seem to be available in the Windows version.
It depends on the version of darktable, not on the operating system. There used to be two separate settings: one for scene/display referred workflow, the other for legacy/modern chromatic adaptation. With the latest version, a scene-referred workflow implies modern chromatic adaptation, while the display-referred workflow implies legacy chromatic adaptation.
1 Like
I see, then what does “none” refer to?
1 Like
You’ll often get answers faster, and save time for others, if you read the manual.
4 Likes
I’m not sure about the time saving in the long run: after a few times, I just stop reading the questions…
I read the section of the manual “Processing” and I see no mention of the option I have been talking about.
Because it has been removed. The chromatic adaptation method is now implied by the selected workflow defaults.
- none sets the module order to v3.0 RAW and uses the white balance module for chromatic adaptation. No other exposure or tone mapping modules are enabled by default.
1 Like
This is not chromatic aberration, but adaptation.
There has never been a setting for chromatic aberration correction.
You can do that in the lens correction module, and additionally in the dedicated chromatic aberrations and raw chromatic aberrations modules.
https://darktable-org.github.io/dtdocs/en/module-reference/processing-modules/lens-correction/
https://darktable-org.github.io/dtdocs/en/module-reference/processing-modules/chromatic-aberrations/
3 Likes
If you’re using a silicon mac then you should enable opencl to get a performance improvement…
There is a small caveat to selecting none… the default blend mode for the modules is set to display
So if you use none you have to remember to change this or at least I find it gives nicer results and I don’t think display will give you the fulcrum slider…that I would have to check… So you are actually better off in my estimation to use one of the two scene modes but then set both CC and filmic for example to be auto applied as disabled. WB can be set to as shot and the side benefit is that CC and filmic are sitting there ready to activate if you are going to use them… In this way you can get to the point where you have classic wb and view the image pre tone mapping and have the masking set to scene… I suspect many users are not even aware of this nuance…
@Andy_Astbury1 uses “none” due to having had a problem getting the WB module to default to “as shot”. I’m having the same problem on my Win 10 computer.
See approx 3:45 into the video. .
Yeah, but the ‘legacy’ bit is missing as you can see Mike!
Hi Todd,
If I opt for filmic scene referred, I get this strange behaviour in the exposure module, adding 2/3rd EV when the camera was set to 0EV.
It all gets a bit much when you’ve seemingly got to have eyes in the back of your head to check that what you think is happening, is actually happening!
Your original tip (none/legacy) sorted me out nicely, but now the legacy part seems to have vanished from the prefs panel.
But either way, scene referred default for the exposure module is doing something neither I, or the file exif, has asked it to.
If I drop back to ‘none’ in prefs, then this problem goes away.
Its explained in the manual: darktable 4.6 user manual - processing
If you want filmic you cam use a preset to turn it on when using the “none” preference, or use a preset to reset exposure to zero when using one of the scene ref’d defaults.
1 Like
Because base curves increase the brightness of midtones, while the tone mappers (filmic, sigmoid) leave midtones alone.
Left: preview of the camera’s embedded JPG; right: darktable without adding the 0.7 EV, all tone mappers disabled - midtones are darker:
Same, with darktable adding the default 0.7 EV - midtones are about the same brightness:
The image was intentionally underexposed to keep the highlights on my old compact camera, but that’s not the point – the same -1 EV underexposure is applied to the JPG preview and to the darktable image.
The same image, exposure disabled, but with darktable’s ‘average’ (‘neutral’) base curve, also brighter midtones:
2 Likes
Almost every raw needs at least that much to set middle gray to a good spot. I actually auto most pictures to 50 %. For me that ends up anywhere from 0.4 to 1 Ev as a starting point. This sets middle grey nicely for filmic and the other modules… Again you can just set exposure to a fixed value as an auto preset or set it to apply disabled