Hi,
I performed some basic experiments with the new nagadoctor module. I
observed one possible issue:
When the negadoctor module is used in combination with the haze removal
module then the haze removal must be applied after RGB inversion via
negadoctor. This means the haze removal module must be moved along the
pixel pipe from its default position to just after the negadoctor.
I have no idea if moving haze removal after "input color profiles" may
cause some issues. Assuming, however, that one would not use negadoctor
in combination with
* tone mapping,
* tone equalizer,
* graduated density or
* unbreak input profile,
moving haze removal module to a position just after the negadoctor
module should be unproblematic.
Users should be aware of this circumstance, when trying to remove
atmospheric haze from scanned negatives.
I do not think that this inconvenience can be fixed by changing the
default positions of the haze removal module or of the negadoctor
without raising new issues for other use cases that do not employ both
modules in combination.
Heiko
--
-- Number Crunch Blog @ https://www.numbercrunch.de
-- Cluster Computing @ https://www.clustercomputing.de
-- Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
