On Tue, Jan 8, 2013 at 8:08 PM, Pascal de Bruijn <pmjdebru...@pcode.nl> wrote: > On Tue, Jan 8, 2013 at 7:19 PM, Pascal Obry <pas...@obry.net> wrote: >> Le 08/01/2013 19:06, Pascal de Bruijn a écrit : >>> I do however wonder if this might be more suitable as a seperate >>> migration tool (possibly included in the darktable source tree), >>> instead of cluttering the Darktable UI itself with something that is >>> basically meant as a use-once kinda thing. >> >> Well why not have an option to activate or not this but to me it is not >> a use-once. I do not expect to do a mass conversion but to be able to >> import one-by-one from the darkroom. This is important as the result >> must be checked and adjusted. > > Hmm, fair enough. > >> So I'm mostly designing this as an help >> only for the develop process. > > BTW, the Lr HSL tool can probably be reproduced to some degree with > our colorzones tool :)
And another thing comes to mind... You might want to force colorin to the standard color matrix (if available) on Lr import, as most of these matrices are sourced from adobe via dcraw. It won't be a perfect match as there as still enough differences, but the standard matrix make more sense than any other in this case. Regards, Pascal de Bruijn ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
