> And the divisions by zero are triggered by RAW brightnesses that do
> not occur in the picture. It is fixed now. A good image should
> cover all brightness levels, though.
>
>
if you can detect missing brightness, do you print a warning to the user ?
that would be an easy way to enforce some sort of image quality in the
input...
(it would be nice to check in the metadata for fields like ADL too, but
that's another matter)
>
> The list of presets for the base curve module would get too long
> with this approach I suspect.
>
>
maybe we could do something similar to profiled denoised that has much more
presets than you do (one per camera*iso )
>
>
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel
