The base curve can be still used with the standard one instead of the camera one, colours are quite fine then. I was doing that before the arrival of filmic. So the base curve can be kept. And indeed it's good to have the choice.
Le mar. 28 mai 2019 à 10:00, Florian W <flo.wern...@gmail.com> a écrit : > Not everyone has the same approach of digital development (eg. Film like > response vs more creative curve editing, with its disadvantages) and one of > the strong advantage of Darktable is allowing all these use cases. Starting > a war about this won't get us anywhere in the issue at hand here. > > > Le mar. 28 mai 2019 09:33, Aurélien Pierre <rese...@aurelienpierre.com> a > écrit : > >> For the last time : >> >> *BASE CURVES ARE EVIL, CRAP, GARBAGE, NO-GO, DON'T TOUCH, BIO HAZARD, >> KEEP AWAY, HUN HUN, SURVIVORS WILL BE SHOT AGAIN.* >> >> I wouldn't have taken 2 months of my life to develop filmic if base >> curves had worked as expected. Base curves are a broken design and will >> always destroy colors. I have repeated that multiple times in the past >> years, it would be great if people started to listen. >> >> In darktable 2.8, there will be a global preference to have the base >> curves disabled by default because they really harm, especially for the >> newest HDR cameras. Until then, the first thing you need to do while >> opening a raw picture is to disable that god-forsaken module manually. >> >> Thanks for confirming it has nothing to do with matrices though. That >> means everything works as expected. >> >> Aurélien. >> Le 28/05/2019 à 09:00, Florian Hühn a écrit : >> >> >>> If RawTherapee is really using the same matrices, it would be >>> interesting to find out what's being done differently (or additionally)... >>> >>> RawTherapee uses dcraw for import. I took the A7RIII testchart raw and >> ran it through 'dcraw -v -w -o 1 -T DSC00157.ARW', then imported the .ARW >> and the TIFF created by dcraw into DarkTable. The TIFF lokes more natural >> to me. Especially the skin color of the guy on the right looks somehow a >> bit yellowish / ill in the .ARW but more natural in the TIFF from dcraw. >> BUT: When importing the TIFF no base curve is applied. When I disable >> base curve on the .ARW and instead use levels and tone curve manually i can >> get a look that is closer to the TIFF (i.e. the dcraw variant). >> Maybe it comes down to different default settings in DarkTable importing >> vs. dcraw. At some point I'd like to double-check that the matrix >> calculations done by DT are indeed carried out as intended, but so far I >> didn't find a way to artificially create a raw-file for this purpose. >> >> >> ___________________________________________________________________________ >> 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 >> > > ___________________________________________________________________________ > 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
