Hey, One more reason for gamma.c: legacy. In 2009 when the pipeline was the one of ufraw, this was actually used. So in case someone opens 10yo shots now they depend on the iop.
Re: colorpicker. that's a known issue, we don't run multiple pipelines so the colorpicker reads whatever there is at the end. No clue about your logspace issue. Maybe you picked in lab after display profile transform? that'll have gamma and cbrt(). Cheers Jo On Sat, 3 Nov 2018, 10:05 Andreas Schneider, <a...@cryptomilk.org> wrote: > On Saturday, 3 November 2018 09:59:23 CET Andreas Schneider wrote: > > On Friday, 2 November 2018 21:10:33 CET Aurélien Pierre wrote: > > > Hi Jo ! > > > > > > Thanks for your answer. > > > > > > So this doesn't explain why the global colorpicker readings change > > > depending on the display ICC profile, nor why using a log encoding > > > between -2.5 and 2.5 EV, the grey gets remapped to L = 77 instead of > 50. > > > > > > I believe there is a gamma correction where it doesn't belong. Where is > > > the code for the colorpicker ? > > > > Aurélien, > > > > you broke image export with the latest change: > > > > See: > > > > https://xor.cryptomilk.org/darktable/broken.jpg > > Oh, I get the same if I open it in the darkroom! > > -- > Andreas Schneider a...@cryptomilk.org > GPG-ID: 8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D > > > ___________________________________________________________________________ > darktable developer mailing list > to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
