> this whole thing needs a cleanup, i'm slightly scared by the rgb > modules coming after the output profile, which will behave > differently depending on the profile (the only one i might > occasionally use is vignetting i think). i guess we should move > output/display profile to the very end and make the current colorout > a Lab->rgb + s-curve module.
Hi Hanatos, It seems we are duplicating some efforts here :-D Your work on darktable/film-emulation and my darktable/tool_basecurve_improvements are heading in the same direction. As you seem to be more productive than i can be lately, i will put on standby my branch, but still share the results i got so far. Disabling basecurve and adding a proper tonecurve (which is well placed just before the color output module) i tried to simulate a late curve module. This works very well for the tonal curve (L curve). However the automatic a*b* scaling seems to hurt colors somehow, not sure what's at stake here as everything is intermixed by the La*b* formula. So I'm able to get nice results in many cases, but for some, colors are less punchy. I'd describe the colors as a bit dark and washed out. My next move would have been to not only profile the L curve, but also the a* and b*. I see you already started using a different color representation, LCh instead of La*b*, is that avoiding the color problems I have ? Cheers. PS: Do not hesitate to share results with me, i got quite interested in the matter lately. -- Edouard Gomez ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
