Hi, presets are just that : presets. It's hard to have them truly universal. If you like other presets better, just save them.
Filmic RGB uses a different spline interpolation method that behaves differently, closer to the densitometric curves of actual film emulsion. But the previous presets don't make sense now. All the current presets put the middle-grey… in the middle of the dynamic range. You will find that it's how the interpolation behaves better, and it only make sense if you think about it. If you find you image is blown-out (is it really though, or did you just lose local contrast in highlights… which is the goal ?), you can use the dynamic range scaling setting, to quickly and symmetrically give a safety margin to the black and white points. Cheers, Aurélien. Le 16/10/2019 à 10:34, KOVÁCS István a écrit : > Hi, > > I'm on darktable 1a11ea71 compiled using build.sh; OS is Kubuntu 19.04. > > I started with a reasonably exposed landscape, and tried applying the > 'outdoors' setting as a starting point (that, and 'bright outdoors', > often worked well for me in 'classic' filmic in darktable 2.6.2). WIth > the version built from master, I get a rather blown-out picture, with > the grey point set to 2.31%. Auto-tuning sets it to around 5%, and > that results in a much more pleasant rendering (my preferred value, > set manually, is 6%). In 2.6.2, the outdoors preset used 9%; the one > most similar to master's 'outdoors' setting from was 'HDR' of v2.6.2 > (2.25%). > I've uploaded the NEF and screenshots with the different settings here: > https://drive.google.com/open?id=1Abif5j70a0aaVTanGBd7O0JyMntOcRlg > > I started my 'master' version with separate config/cache/library, so I > don't think I have any automatically applied settings other than those > shipped out of the box. 'Classic' filmic is no longer available as a > module, although I can open old history stacks and see a '/!\ filmic' > step in them; editing is not possible. > > A slightly confusing entry in the history: there is a step called > 'gamma', but it's not tied to any module. I guess it's internal > processing, something the users can't do anything about. > > Thanks, > Kofa > ___________________________________________________________________________ > 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
