I believe darktable also uses Lanczos internally (lanczos3 is selected as pixel interpolator in Preferences)Įxported at fullsize from darktable, then resized to 1920 using ImageMagick I ended up exporting full size, then feed them to ImageMagick instead, even though I use the same sharpening params in dt, but perhaps they're applied before resizing instead of applying to the resized.Ĭonvert "DSCF7390.jpg" -filter Lanczos -resize 1920x -unsharp 1.5x1+0.4+0.02 -quality 90 "resized/DSCF7390.jpg" On a related note, I've been resizing the images to use on my website, and found that the direct export from darktable for small size is not very sharp. Nor does X-Trans only Foveon.Īs I pulled from master branch too often, I don't even notice the change
As I keep saying, over and over again, repeatedly, there is no point in 1x1 with digital cameras because Bayer sensors don't have that much color resolution. I'm sticking to the non-local auto for now, until I have time to read the documentation/discussion on the new NR.īTW, with 8-bit JPEG output, Darktable shifts from 1x1 (no chroma subsampling) to 2x1 (4:2:2) at quality 92, for great space savings. I gave wavelet-auto a try, but couldn't tell what it does as my image is still as grainy as if no NR applied (well, it is different, just a different kind of wormy grains is applied). I believe it's possible with Darktable now. It is difficult to equal the very nice noise reduction that Fujifilm does at high ISO in out-of-camera JPEG. Many new features, including focus peaking and denoise profiled with wavelets Y0U0V0. I pulled from master branch last week as usual, and the thumbnails in lighttable stopped updating from the changes in darkroom, until I pulled and recompiled yesterday. It's relatively easy to compile from the github source, but living on the bleeding edge is quite dangerous, too. It reached the Ubuntu Linux PPA, so I upgraded.
0 kommentar(er)
