that's a very good summary, let me add a couple of details
there are multiple ways to represent an image, RGB is the most well known
one, but Lab is also well known
some modules can only work on certain representations and changing format
is very costy in quality
The order also minimizes the number of image representation switches to
maximize quality
Your explanation was really good, it would be awesome if you could add it
as a wiki page (and/or a section in the usermanual)
there are a couple of FAQ we really need to document somewhere
* why does DT apply some iop by default
* why can't the order of modules can't be changed
* why DT produces more noisy images than most raw processing software out
of the box
* why can't parametric masks be reused between modules
all theses are legitimate questions, not obvious, but that are very
frequently asked... we need to do something about that
On Thu, Oct 2, 2014 at 10:00 AM, Stéphane Gourichon <
[email protected]> wrote:
>
>
> In some areas (all over and especially after "input color profile"), the
> order may be more debatable, I don't know the details. Inside the source
> code there is a script that generates a dependency graph with (no
> kidding) probably over one or two hundred of inter-modules constraints
> hinting why this order is necessary.
>
> Cheers,
>
>
> --
> Stéphane Gourichon
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Darktable-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/darktable-users
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
