It looks like the most recent branch (21 November) pertaining to your work is:
RawTherapee_dev_5.7-245-gff3e31466_W64_Skylake_191121.zip
Just out of curiosity, I don’t know wheter I am supposed to download the sse4 builds or the other ones most recent SkyLake builds?
At home, I run an old Intel I7: 6500U CPU.
In all truth, I suppose I should opt for the Skylake builds
This is a call for help documenting the Capture Sharpening tool in RT from a user perspective.
I tried to document it, but always ended with very technical documentation, which does not help the users to understand how it works and why it’s better than the (old) RL-deconvolution in RT.
@Silvio_Grosso
As automatic nightly builds are provided on official site, I now build mainly for skylake architecture. If requested I can build for generic+ SSE4 feature architecture.
The micro architecture of this processor being skylake, you can use the skylake build and perhaps benefit of improved speed.
If you found a way to automatically limit the iteration count when halos develop, does that mean have have a reliable halo detection method?
If so, wouldn’t that lead to a relatively simple method to automatically estimate the point spread function?
I implemented an automatic iterations limitation which works quite well to stop iterating when halos appear. But that does not mean it is perfect.
The current implementation processes the image in tiles of size 32x32 pixels. Each of the tiles can be processed with a different gaussian sigma (currrently only gaussian kernels up to sigma 2.0 (13x13) are supported.
If in an iteration of a tile processing one of 32x32 pixels is 50% darker than the original pixel, the algorithm stops iterating.
Corner Softness. Wide-open at full wide angle, the lens showed a little decentering, with the upper corners showing more softness than the lower ones. The center is quite sharp, but softening from the upper corners extends a fair bit into the frame. At full telephoto, corner sharpness is better all around, but the pattern changed, with upper and lower left corners quite sharp and the lower right somewhat soft. The center is again quite sharp, as is most of the frame.
I once had the Idea that one could manually mark borders between objects and enforce a “no ringing” criterion there, using this to guide an algorithm to find the optimal kernel. But I guess that’s a bit off-topic for this thread and quite a project in its own. The idea was to use e.g. the boundary between an out-of-focus background and an object in focus for this because that’s a area in the image where we can make quite solid assumptions about how the transition is supposed to look like with a correct kernel.
Hi, new RawTherapee user here. I know this is old thread. Not sure if my simple question warrants new thread, so I will just post here.
I have a question why Capture Sharpening is available on some RAW files, but not others.
On my Samsung S23 Ultra DNG file, this option is not available. Under RAW tab, only 2 available sections are available: RAW White Points and Dark-Frame.
I checked my Sony a6400 and Canon 6D RAW files. I do see the Capture Sharpening plus many other sections under RAW tab.
How come DNG file does not have this option? Is this due to limitation of camera or RAW file type (DNG)? Or some other reason?
There are many uses and abuses of DNG… I think some smartphones handle demosiacing differently and so this might bypass the usual ability to use capture sharpening… I am sure someone more qualified about the aligo of that function will be able to cofirm this…
It may be because the DNG is not a raw file or contains unexpected data, such as weird data location within the DNG file container. Capture Sharpening happens after demosaicing, so how it was done should not affect the module’s operations, unless there is something that bypasses it (due to what I suggested above or other reasons).
The best way for you to find help is to upload a sample file for us to investigate. Welcome to the forum!
Samsung use modified sensor layout and ML demosaicing which they likely or maybe not code into the DNG. I suspect that since capture sharpening comes right after this that the data is just not recognized and so the options are not available… thats my guess…
