Hello,
I don't know the digiKam source code, but according to my experience, I would
agree: First crop, then adjust white balance or do other color operations. Since
the "pixels to calculate" is less after cropping.
You can see it clearing with "cpu intensive" operations like "local contrasts"
or "sharpen: refocus": The operations take measurably less time when operating
on a picture *after a crop* (from 4752x3168 to 1800x1350 pixels).
My workflow is:
1. rotate
2. crop
3. adjust white-balance and/or exposure
Exception: There are some operation, I think (I don't really know), which need
so work with the "original pixels" out of camera to give best results: "Enhance:
Sharpen: Refocus" or "Enhance: Lens: Distortion [correction]"
If digiKam Handbook tells the other way, maybe you could file a bug at
https://bugs.kde.org/ for "product: digikam" and "component: Documentation"
Regards,
Peter
On 17.06.19 06:16, Northern Colorado Event Photograph wrote:
> I have digiKam 6.0.0 installed on a Dell Latitude E6520 with 64 bit Win 7
> SP 1, i5 processor, 8 GB RAM.
>
> Does digiKam apply adjustments such as exposure, white balance, curves,
> levels only to a cropped/resized image, once an image is cropped/resized
> (and not to the complete image)?
>
> If so, isn't it better to apply those adjustments after the crop/resize
> than before, as the digiKam Handbook Standard Workflow Proposal describes?
>
> For example, if adjustments are only applied to the cropped image, then
> logically speaking the calculations required for those adjustments are made
> only on the "wanted" pixels of the image and therefore the results should
> be "better" since the "unwanted" pixels are not included in the
> calculations.
>
> So if it is better not make those adjustments after a crop, why not?
>
Locked
